La IA de tu empresadeja de vivir encuentas sueltas.
One console per organisation where your team builds its own agents, gives them the company's documents and hands out permissions by department — under one account and one invoice.
- You sign in with your Theus account
- Contracted separately
- Only AI usage is metered
$ curl -s https://theus.pe/api/atlas/plans | jq '.plans[].name'"Atlas Team""Atlas Business""Atlas Scale"# And the API demands a real session:$ curl -o /dev/null -w '%{http_code}' https://atlas.theus.pe/…/info401
El problema, en una frase
«Every department has its own account, its documents off to one side and its keys pasted into a chat.»
One identity, one catalogue and permissions by department — under a single invoice
What does Atlas do?
It governs what a loose chat does not.
One identity for the whole company
You sign in with the same Theus account and each organisation gets its own model catalogue and its own credential.
Agents you configure yourself
A generic builder with a private knowledge base and office-document reading.
Bought separately
Three plans of its own — Team, Business and Scale — with recurring billing, monthly or annual.
What is inside the console
It is not a chat with a companylogo on it.
Agents and flows
They are created, configured with instructions and scope, tested and published.
Private knowledge
Document bases per organisation, with segmentation and keywords.
Models and credentials
Your organisation's enabled catalogue, plus its credentials.
Tools and templates
MCP servers, publishable skills and templates.
Permissions by role
Each section is switched on by permission; the role decides which surface each person sees.
API keys and statistics
Managed programmatic access and visible usage.
The part almost no enterprise page writes down
What is metered, what is not, and what happens when it runs out.
- Metered and cut off
The included AI usage, in credits. Each Atlas tier is backed by a concrete allowance.
- Not metered
The catalogue's capacity figures: users, agents, knowledge and operations have no counter.
- The real cut-off is in credits
The allowance is announced as an amount, but the cut-off happens in credits. If you ask for a model above your tier, the answer tells you what happened in Atlas's own vocabulary.
The Atlas plans
Three tiers.One single meter.
The amounts and the small print are published by the same server that bills: this page queries them live when it opens and types none of them. What you see here is what /api/atlas/plans serves, and the purchase closes in the Atlas console itself.
Published before tax · monthly or annual
- Atlas Team
- · Sized for 5 users
- · Included AI usage: metered and cut off, in credits
- · You sign in with your Theus account
- Atlas Business
- · Sized for 20 users
- · Included AI usage: metered and cut off, in credits
- · You sign in with your Theus account
- Atlas Scale
- · Sized for 75 users
- · Included AI usage: metered and cut off, in credits
- · You sign in with your Theus account
Users, agents, knowledge, operations and the activity log are the intended sizing of each plan, not an automatic cut-off. What is metered and cut off is the included AI usage, in credits.
A pilot
A pilot starts with a process,not with a demo.
The top tier is a conversation. If you want to start there, tell us which repetitive task is costing you time: with that we can decide the scope, who validates the result and how we measure whether it worked. If you would rather go in on your own, the ladder and the buy button are on the Atlas plans page.
One account. One invoice.Your whole company.
Atlas Team · Atlas Business · Atlas Scale — monthly or annual