Self-hosted AIOE
Run the AI Enterprise Operating Environment in your own tenancy, and choose how to install it.
Self-hosted AIOE (the Enterprise edition) is the control plane AI Workbench signs in to, running in your own cloud tenancy or data centre. Your people sign in with your organisation's identity provider, and each workbench finds AIOE from a DNS record on your email domain. From the console you then see every workbench and node, publish policy and a catalogue of teams, roles, skills and prompts, govern the tools agents use, keep the secrets they need, and control a workbench remotely from a browser or a phone. No workbench opens an inbound port: each one keeps an outbound connection to AIOE, and a WireGuard overlay can carry private traffic between machines.
These pages describe the current release of self-hosted AIOE: Helm chart aioe 0.1.0, application version 0.1.0. If you would rather not run anything yourself, Mojo Up AI Cloud offers the console as a hosted service.
What you run
| Piece | What it is | Required |
|---|---|---|
| API | One stateless container (aioe-api, port 3001). Workbenches, nodes, the console and the mobile app all talk to it. | Yes |
| Console | A static web app served by nginx (aioe-console, port 8080). | Yes |
| PostgreSQL | Where everything is kept. The API applies its own schema migrations when it starts. | Yes, for anything beyond a throwaway evaluation |
| Redis | Lets more than one API replica share live connections. | When you run more than one API replica |
| Mesh relay and gateway | The WireGuard overlay's packet relay and the platform's own node on it (aioe-mesh-services). | Only if you use the overlay |
You also need two app registrations in your identity provider, a public hostname for the API and one for the console, and a DNS record on each email domain your people use.
Choose an install path
After you install
Once AIOE is running, the day-to-day work of an administrator (people, policy, catalogue, tools, secrets, audit) is in Administration.