What's an Isolated Instance?
Your own private workspace — a separate database and application — built on the same Adora AI OS framework. Same look and feel across your whole company. Completely separate environments per team.
The core idea
Every Adora AI OS instance has its own database, its own application layer, and its own set of tools and integrations. Different departments often have very different needs — what an engineering team uses daily would clutter a marketing team's workspace, and vice versa.
If your company is fine with everyone working the same way, a single instance works perfectly — teams just use the right applications within it. But when departments need different toolsets, different data boundaries, or different AI workflows, isolated instances give each team exactly what they need with nothing they don't.
How instances connect
Each department runs its own instance. All of them can pipe context upward to a leadership instance — giving leadership a unified view without giving them access to every team's day-to-day workspace.
Each instance = its own database · its own application · its own toolset
Not all instances are the same size
The $897/month starting price is for a basic instance — the right fit for a focused team with standard workloads. A 30-person marketing department and a 2,000-person engineering department both get "isolated instances," but they need very different amounts of compute. We right-size every instance during onboarding.
A focused departmental workspace. Enough compute to run your AI workflows, integrations, and context without breaking a sweat.
- ·A marketing team running campaign agents
- ·An HR department managing onboarding flows
- ·A small ops team automating reporting
More compute, more concurrent users, higher context load. Right-sized during onboarding based on your team's actual workflows.
- ·A mid-size engineering department
- ·A regional sales org with heavy CRM integration
- ·A cross-functional ops team
Enterprise-grade compute for departments that run at scale. Think thousands of users, real-time integrations, and high-volume AI workflows running simultaneously.
- ·Enterprise engineering departments (2,000+ engineers)
- ·Global sales operations
- ·Large-scale data or ML teams
We figure out the right size together
You don't need to spec out your compute before signing up. During the Pre-Season Audit phase of onboarding, we look at your team sizes, workflows, integrations, and data volume — and we recommend the right instance tier for each department.
Whether we're running on our current infrastructure or our own compute as we scale, the principle stays the same: the cost reflects the resources your team actually needs. A small marketing team pays for a small instance. An enterprise engineering org pays for the compute that supports thousands of users and high-volume AI workflows running simultaneously.
Ready to figure out what you need?
Instance sizing is part of onboarding. Claim your founding spot and we'll scope everything out together in the first session.