We build the layer
under your runtime
Midwess is a small team working on durable infrastructure for
stateful workloads. We started with pglite-rs — an embedded
Postgres for Rust — and grew out from there: worldant puts a
durable world runtime on top, and PgPaw turns the same engine
into a read-replica cache with realtime updates.
Everything
we ship is MIT licensed. We make money from sponsors and
partners, not from a hosted control plane.
What we hold to
The principles that shape what we build and — more often — what we deliberately don't.
State outlives the process
A runtime is only durable if its state survives the things that kill it — restart, crash, deploy, scale-to-zero. The work is making that property compose across layers instead of leaking into every application.
Postgres, not a lookalike
We don't ship a custom query language, a bespoke type system, or a new wire protocol where Postgres already has one. The faster the world agrees on a SQL, the more leverage every team gets from it.
Operator-grade defaults
Sane retries, audit logs, per-step observability — boring infrastructure that ships inside the platform, not as tribal knowledge bolted on by each team that picks us up.
One stack, three layers
Each layer stands alone. Together they keep stateful work alive through anything short of disk failure.
Real Postgres, embedded
pglite-rs compiles a single-process Postgres fork straight into your binary. Full types, transactions, MVCC, extensions — no server, no Docker, no install step.
Durable runtimes
worldant hosts JS workflows on a V8 isolate owned by Rust. Every step transition is an atomic SQL write, so the isolate can sleep on idle and replay from the log when work arrives. Exactly-once across a restart.
Realtime at the edge
PgPaw serves the same query as both a CDN-cacheable snapshot and a live SSE feed, with watermark-derived invalidation. Plain Postgres SQL, native RLS, no bespoke query language to learn.