Enterprise · Plans & Getting Started
Pick a plan, bring your knowledge and standards, and go live in weeks, not quarters.
Business
- Resource Hub for your own Skills
- Credits Plans per period and day
- Library, Base and Connectors
Finance operations
- Library seeded from Git
- 2 Connectors bound and tested
- First Work: month-end close
Company release
- Released to 3 roles in Explore
- Pilot team through Academy
- Usage overview for leaders
Plans
Every plan is the same AOS.work: the same Basil Harness runtime, the same Shieldon gateway, the same apps. The difference is how far you take it and how much we do with you.
Team
One team, one workspace, real work from the first week.
- Seats
- Up to 25 seats
- Workspaces
- Up to 5 workspaces
- Skills & Works
- Published Skills and Works from Explore
- Apps
- Library and Base
- Models
- Curated model catalogue
- Governance
- Roles, allowed models, run records
- Support
- Email support and the Academy foundations path
Business
Most teams start hereAuthor your own standards and release them across departments.
- Seats
- 25 to 500 seats
- Workspaces
- Unlimited workspaces
- Skills & Works
- Resource Hub: author, version and release your own
- Apps
- Library, Base, Connectors and custom apps
- Models
- Your own model keys, credits per role
- Governance
- Credits Plans, usage overview, audit export
- Support
- Named contact and Academy role paths
Enterprise
Your environment, your identity provider, our delivery team.
- Seats
- Unlimited seats across accounts
- Workspaces
- Unlimited, with Git-synced resources
- Skills & Works
- Everything in Business, plus a private catalogue
- Apps
- Everything in Business, plus Open Origin System apps
- Models
- Self-hosted and private models
- Governance
- Custom roles, registration domains, policy locks
- Support
- Delivery team, partner network, capacity planning
Enterprise adds
- Dedicated deployment, cloud or on-prem
- SSO and custom roles
- Security review pack
- Partner-led delivery
Limits are per account. Moving up a plan keeps your workspaces, Library, Memory and run history; nothing is migrated, only unlocked.
In every plan
Whichever plan you pick, the workplace underneath is complete. These are in every plan, from the first seat.
Basil Harness runtime
Every task runs as a traceable, sandboxed, cancellable unit of work, with a run record you can read back.
Included
Shieldon gateway
Policy, security and audit for every model call, whichever model the run uses.
Included
Library
The file system and source of truth for every workspace: My Space, Team Space, sharing and trash.
Included
Base
Structured data with tables, fields, views, filters and grouping; tasks can return query views.
Included
Memory
Long-term context per user, kept as revisions you can review and restore at any time.
Included
Scheduled Tasks
A fixed message on a one-time or recurring plan; every trigger is its own task and run record.
Included
Explore
Where people discover, add, configure and update Skills, Works, Connectors and Apps.
Included
AOS Academy
Learning paths from foundations to role-based Works, for users, administrators and delivery teams.
Included
Credits & models
Models are configured once, centrally. Credits Plans put a ceiling on spend per period and per day. Roles decide who may use which model. Nothing is substituted silently.
- 01
Central model configuration
Administrators add models with a base URL, key, context window and a credits conversion per thousand tokens. A model must pass Test connection before anyone can be granted it.
- 02
Allowed models per role
Each role carries its own allowed models. Multiple roles union, then intersect with what is configured. If a model is not allowed, the run does not quietly pick another one.
- 03
Credits Plans per period and per day
One active plan per account: a billing period, a period limit, a daily limit and members. The usage overview shows where credits go, by team and by model.
Configuring models
Illustrative · Admin Console, Models and Credits & Plan Management
Getting started
A guided path with our delivery team and your administrator. Every week ends with something your people already use.
- 01
Week 1
Workspace and knowledge
We set up the account, roles and the first Workspace, then bring your documents and standards into Library from Git, upload or an existing drive.
- Account, roles and first Workspace
- Library seeded with your documents
- Models connected and tested
- 02
Week 2
First Skills, Works and Connectors
Together we author the first Skills and one Work for a real role in Resource Hub, bind the Connectors they need and publish immutable versions.
- Three to five Skills published
- One Work for one role
- Connectors bound and tested
- 03
Week 3
Pilot team and Academy
A pilot team works on AOS.work every day. They follow the Academy path for their role, and their run records tell us what to refine.
- Pilot team live on real tasks
- Academy path completed
- Skills refined from run records
- 04
Week 4+
Company roll-out
Explore Management releases the published versions to every role. Scheduled Tasks take over the recurring work and the usage overview shows adoption.
- Explore releases to all roles
- Scheduled Tasks on recurring work
- Usage overview for leaders
- Done
- In progress
- Up next
Our delivery team, your administrator, and partners when you want them.
The delivery team runs the path together with your administrator. Implementation partners can take over scenario design, Skill authoring and Academy training when you roll out across regions or business units.
Questions
The questions we hear in most first calls.
A team is usually working on real tasks within the first two weeks, and a company roll-out follows from week four. The pace depends on how much knowledge you bring into Library and how many Connectors the work needs.
Book a demo and we will set up a workspace with your knowledge, your standards and your guardrails.
Built on Basil Harness · Protected by Shieldon