Skip to content

Architecture

One engine, three zones.

akterd is a single Rust engine. On your laptop it runs akter dev. In the cloud it writes every commit to two of three NVMe replicas before it answers.

The stack, layer by layer

What we’ve measured

FIG. 2 3-AZ quorum commit, 10,000 samplesc8id.large ×3, us-west-2a/b/c, io_uring O_DIRECT

commit latency, ms

0.76 ms
Commit across three zones at p99
Standalone write-ahead log commit. Not yet wired to akterd SQLite inserts.
0.63 ms
To fork a 50 GiB volume at p99
dm-thin copy-on-write on c8id.xlarge, 200 runs, activation included.
47.5k/s
Commands on a single hot actor
64 clients at 2.36 ms p99. Durable Objects soft limit is about 1,000 req/s.

akterd figures use local NVMe and a Rust echo worker. Full three-zone end-to-end numbers are still targets.

How the commit path works

What’s live and what’s next

We keep this list honest. Nothing moves to Live until it passes on real hardware.

Live

  • Akter.make, tables, files, channels

    @akterjs/effect

  • Plain TS SDK and UI hooks

    @akterjs/sdk · react · solid · svelte

  • akterd local engine

    akter dev · 23/23 host guarantees

  • 3-AZ quorum WAL core

    Two-of-three NVMe commit, object storage cold tier

Landing now

  • Copy-on-write files

    A 50 GiB fork in 0.63 ms at p99

  • Embedded hybrid search

    Vector, BM25, and hybrid ranking

  • Reactive SQL views

    Live queries that update incrementally

  • Backups and polyglot clients

    akter backup · @akterjs/codegen

Later

  • Firecracker computers

    under 10 ms resume target

  • Cross-actor transactions

    Akter.transaction

  • akter studio

    state and SQL inspector

  • Preview environments

    akter checkout · akter preview

Start with one actor.

Run akterd on your laptop with one command. Ship the same code to three zones when you’re ready.