Business operations
One agent per customer
Give each customer a private agent that sleeps when idle.
- Memory
- Store
- NoSQL
- Identity
The scenario
A product runs a dedicated agent for every customer. Idle ones are frozen so they cost almost nothing.
How it works
- 1Each customer gets their own partition.
- 2Inactive partitions are frozen.
- 3A returning customer’s agent is thawed on demand.
An illustrative scenario, not a customer story.
Interactive simulation
Simulate this case study
Watch the partition come up, each step run, and usage build as it goes. Simulated: volumes, timings and prices are illustrative.
Partition
—
Status
not created
Elapsed
00:00
- Provisioning
- Processing
- Freezing
- Complete
01Each customer gets their own partition.
queued- Ahura Memorymemory.setqueued
status: queued · 0 / 240 keys written
- Ahura Storestore.getqueued
status: queued · 0 / 48 objects stored
02Inactive partitions are frozen.
queued- Ahura NoSQLnosql.getqueued
status: queued · 0 / 600 records written
03A returning customer’s agent is thawed on demand.
queued- Ahura Identityidentity.verifyqueued
status: queued · 0 / 60 signatures
Services in this partition
Memory
0 calls · 0.00 ACU
Store
0 calls · 0.00 ACU
NoSQL
0 calls · 0.00 ACU
Identity
0 calls · 0.00 ACU
Spend by service
Event log
- Waiting to start.
Why Ahura OS
Why this is better on Ahura OS
A dedicated agent per customer is the right design and the wrong cost model if each one needs a running server. On Ahura OS each customer gets a partition, active agents run and idle ones freeze to archive pricing, then thaw on demand when the customer returns. Your cost tracks activity rather than customer count. Isolation is structural, since one customer’s agent has no path to another’s data, which is a much stronger guarantee than a naming convention.
What each capability replaces
- Ahura MemoryInstead of provisioning and securing a cache or database, agents get fast key/value state with expiry already scoped to their partition.
- Ahura StoreInstead of managing buckets, permissions and lifecycle rules, objects follow the partition: they freeze, thaw and expire with it.
- Ahura NoSQLInstead of designing tables and maintaining indexes, you write documents and query them. Indexes are looked after for you.
- Ahura IdentityInstead of building key management and signing services, each agent gets an identity and a signing and verification service whose private keys are never handed to the agent.
And on every use case
One endpoint, not a stack
Memory, storage, compute, inference, identity and messaging share one connection, one identity and one bill. The integration work you would normally own disappears.
Isolation by construction
Every agent’s world is a partition. Separation is how the platform is built, not a convention teams must remember to follow.
Cost follows use
Pay per call and per millisecond. Idle agents freeze to archive pricing. There is no capacity to reserve and nothing running unseen.
Retention and deletion built in
Lifetimes, expiry, freezing and destruction are platform features, so your data policy is enforced rather than aspirational.
Safe autonomy
Spending limits, protected signing keys, approval steps and signed actions let agents work unattended without being unaccountable.
Ready for audit
Designed against SOC 2 and ISO 27001 controls, with every call metered, recorded and attributable.
Compared
The old way of doing things
A running server or container for every customer, mostly idle, each needing patches and monitoring.
Data retention is built in
Everything this scenario stores lives in one isolated partition with a lifetime you set. Expired data deletes itself, a paused project freezes to low-cost archive, and a finished one can be destroyed completely. Security and compliance