Science & optimisation
Multi-year research project
Pause a project for months and resume it intact.
- Store
- Memory
- Graph
- NoSQL
The scenario
A research agent’s whole state is frozen between funding rounds and thawed when work restarts.
How it works
- 1State accumulates over the active phase.
- 2The partition is frozen to archive.
- 3It is rehydrated from its manifest later.
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
01State accumulates over the active phase.
queued- Ahura Storestore.putqueued
status: queued · 0 / 48 objects stored
- Ahura Memorymemory.getqueued
status: queued · 0 / 240 keys written
02The partition is frozen to archive.
queued- Ahura Graphgraph.edge.putqueued
status: queued · 0 / 380 edges recorded
03It is rehydrated from its manifest later.
queued- Ahura NoSQLnosql.queryqueued
status: queued · 0 / 600 records written
Services in this partition
Store
0 calls · 0.00 ACU
Memory
0 calls · 0.00 ACU
Graph
0 calls · 0.00 ACU
NoSQL
0 calls · 0.00 ACU
Spend by service
Event log
- Waiting to start.
Why Ahura OS
Why this is better on Ahura OS
Projects with funding gaps pay twice in the usual setup: once to keep servers alive through the pause and again to rebuild confidence in archived data. On Ahura OS a pause is a freeze. The partition moves to encrypted archive, compute is released, and a manifest records exactly what was stored. Thawing restores the whole project, not file by file, and when the project is truly over, destroying it removes the data and returns what is owed.
What each capability replaces
- Ahura StoreInstead of managing buckets, permissions and lifecycle rules, objects follow the partition: they freeze, thaw and expire with it.
- Ahura MemoryInstead of provisioning and securing a cache or database, agents get fast key/value state with expiry already scoped to their partition.
- Ahura GraphInstead of standing up and operating a graph database, relationships live beside your other state at the same price and isolation.
- Ahura NoSQLInstead of designing tables and maintaining indexes, you write documents and query them. Indexes are looked after for you.
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
Servers and databases kept running, and paid for, through every pause in funding, or data archived by hand and hard to restore.
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