Skip to content

Product / Actors

A database for every
thing you model.

An actor is a typed state machine with its own SQLite, files, jobs, and live channels. It handles one command at a time, so there is nothing to lock.

src/order.contract.ts
export const Pending = Schema.TaggedStruct("Pending", { total: Schema.Number })export const Paid = Schema.TaggedStruct("Paid", { chargeId: Schema.String })export const Order = Akter.make("Order", {  callers: [User],  commands: {    pay: Akter.command({      callers: [User],      errors: [],      from: [Pending],      input: Schema.Struct({ chargeId: Schema.String }),      output: Schema.Void,      to: [Paid],    }),  },  final: [Paid],  initial: { input: Schema.Struct({ total: Schema.Number }), to: Pending },  key: OrderId,  parent: Akter.Root,  queries: {},  states: [Pending, Paid],  tables: [],})

Everything an entity needs,
in one place.

Each primitive lives inside the actor and commits in the same turn, so state, rows, files, and messages never drift apart.

  1. Typed state machines

    States are Effect schemas and commands declare where they can run from and to. akter verify model-checks every path.

    Akter.make · from / to

  2. Private SQLite tables

    Typed tables with STRICT migrations derived from your schema. Queries run against the actor’s own file.

    Akter.db · *.table.ts

  3. Files that fork

    A POSIX folder per actor on copy-on-write storage. Fork an actor and its files come with it.

    Akter.fs

  4. Jobs, timers, schedules

    Durable steps with effect/workflow, one-off timers, UTC schedules, and state timeouts, all inside the turn.

    Akter.timer · Akter.schedule

  5. Live channels

    Push updates and presence to React, Solid, and Svelte clients over one connection.

    Akter.channel

  6. Search in the actor

    Vector, BM25, and hybrid ranking inside the actor’s SQLite, with no separate index to sync.

    sqlite-search · landing now

See inside any actor

Open an actor in the console to read its current state, browse its tables and files, and replay its command history.

ord_4471Order · Awake · production
  • _tagSchema.tag"Shipped"
  • carrierSchema.String"ups"
  • chargeIdSchema.String"ch_9f2a"
  • totalSchema.Number12800
  • itemssku, quantity, unit_price1 row
  • chargescharge_id, amount, captured_at1 row
  • shipmentscarrier, tracking, shipped_at1 row
  • auditcommand, caller, at4 rows
  • designs/mug-01.pngWritten by addItem900 KB
  • receipts/ch_9f2a.jsonWritten by pay2 KB
  • invoice.pdfWritten by pay212 KB
  • labels/ups.pdfWritten by ship88 KB
  • 4ship({ carrier: "ups" })Paid → Shipped0.24 ms
  • 3pay({ chargeId: "ch_9f2a" })Pending → Paid0.22 ms
  • 2addItem({ sku: "mug-01" })Pending, 2 rows written0.19 ms
  • 1create({ total: 12800 })Created as Pending0.21 ms
4 commands · 18.4 KB SQLite · 1.2 MB filesFork into a new key

Call actors from any stack.

Landing

  • Rust
  • Go
  • Python
  • Swift
  • Kotlin

Start with one actor.

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