A platform your institution runs and owns.
AdiHub, the Angelsee Data Intelligence Hub, is delivered as software your institution operates: on your servers, under your security policies, with source code per subscription.
Runs on your servers.
AdiHub and its database run on a Linux server your institution controls, on campus or in your own cloud. It needs no outbound connection to Angelsee to operate.
- A current Linux server (Ubuntu LTS or RHEL-compatible) with Node.js and PostgreSQL installed. The requirements sheet lists the exact supported versions.
- PostgreSQL on the same server or on your institution's own database server.
- Sign-in by emailed link, with a second factor for administrators. Single sign-on through your identity provider (OIDC, then SAML) follows in the first release after v1.0.
- Inbound HTTPS only. Updates can arrive as an offline package if your network allows no downloads.
- Each installation serves one institution, with one data source for that institution.
Installed with a checked, repeatable script.
The installer checks the server before it changes anything, then installs, configures and confirms that AdiHub is healthy.
- A preflight check of operating system, Node.js, PostgreSQL and disk, with a clear pass, warning or fail for each.
- Run over SSH by named Angelsee staff whose access is removed when the work is done, or by your own administrator with our guidance on a screen share.
- An install log your institution keeps, and a health check you can call at any time.
- We can prepare the server for you if your team prefers.
Versioned releases with documented upgrades.
Every release brings the improvements built for all institutions, with the steps to apply it.
- Database migrations run as part of the upgrade, with the previous version kept until the new one passes its health check.
- Automatic rollback when the health check fails after an upgrade.
- Signed release packages; client packages ship without source maps.
- An annual support and updates subscription covers new releases, security patches and support.
Source code per subscription, licensed for your institution.
Nothing about how your numbers are produced is hidden. Your security team can audit the code; your staff can configure and extend it.
- The readable source of the modules you subscribe to, plus the core platform they need to run and to be audited.
- Licensed for your institution's own use. It may not be resold or redistributed.
- Dashboards are defined as configuration, so your team adds and changes them without changing the core.
- Extensions add new dashboards and data connectors, with their own settings and your institution's theme.
- Upgrades stay clean, because your changes live outside the core.
What your team builds stays yours.
Every dashboard records where it came from: shipped with AdiHub, built by Angelsee for your institution, or built by your own team.
- Dashboards your team builds belong to your institution.
- You may choose to share one with us for the core product. Only its design is shared, with generated sample data that matches its structure. Your data never leaves your systems.
- Your administrator sees exactly what will be shared before anything is sent, and every shared dashboard keeps a traceable record of its origin.
AdiHub is in active development. Some capabilities on this page, such as sharing a dashboard with us, are still being built. Ask us which are ready for your institution.
What IT and security teams ask first.
Where does AdiHub run?
On your institution’s own Linux server or cloud, with its database alongside it. It needs no outbound connection to Angelsee to operate.
Who owns the dashboards and the data?
Your data is always yours, and so is every dashboard your own team builds. You receive source code per subscription, with a license to use and modify it for your institution’s own use.
What does our IT team need to provide?
A secure Linux server with Node.js and PostgreSQL installed, and a DNS name and certificate. We can also prepare the server for you.
How is our data protected?
Your data stays on your infrastructure, under your security and FERPA policies. We access your environment only as our statement of work allows, and we never use institutional data to train AI models.
See where AdiHub fits your institution.
Tell us which offices and systems are involved. We reply within three business days.