Ownable by design
Assets, names and records are objects your users hold, not rows in a database you administer.
A base layer where what your app creates belongs to the people using it — and anyone can verify that it does.
Shipped on the platform
The platform is
Verifiable by default
Every state change carries a proof. Trust is something a participant checks, not something they extend.
Composable without asking
Modules share one object model, so anything built here is a part every other builder can use.
Fast without trade-offs
Consensus is reserved for what needs ordering; everything else settles in parallel.
The stack
Six modules, one object model
Each module does one job and shares the same notion of ownership, so composing them is the default rather than an integration project.
Keel
The base ledger: objects, owners, and the rules for moving them.
Hold
Large data with the same ownership guarantees as assets.
Latch
Encryption and access control, enforced by the protocol.
Drift
Heavy computation that returns with a proof it ran honestly.
Well
Shared order books any application can draw on.
Berth
Names people own, portable across everything built here.
Fields
Different industries, same guarantees
Finance
- Sub-second settlement
- Programmable collateral
- Positions anyone can audit
Games
- Items players actually own
- Economies that survive the studio
- Trades without a marketplace tax
Agents
- Balances software can hold
- Spend rules enforced by protocol
- Receipts for every action
Institutions
- Permissioned views on public rails
- Verifiable workflows
- Compliance as a query, not a quarter
Deep enough to build on
The guarantees hold at the scale where platforms usually start rationing them.
- 0.4s
- finality, median
- 24k
- settlements per second, sustained
- 6
- modules, one object model
- 100%
- state verifiable by anyone
Ways in
Your first object is ten minutes away
The tutorial walks from an empty directory to an owned, transferable thing on the test network.
