jed
Embeddable. Capable. Safe for untrusted SQL.
One file, no server — types and behavior modeled on PostgreSQL.
0.x preview — not ready for production use. Heavily tested, but not yet proven by real-world use, and the on-disk format may still change. Read the preview status →
A live database, in your browser
no server — the engine is running on this pageNo results yet. Run a query to see output.
Embeddable
A library you link into your program — no server, no daemon. Just your app and a file.
Single file
One database is one file on disk. Copy it, back it up, ship it. Commits are atomic and crash-safe.
Rich type system
Exact decimals, timestamps, UUID, JSON/JSONB, arrays, ranges, and composite types — and a value is never silently reinterpreted at runtime.
PostgreSQL-modeled behavior
Modeled on PostgreSQL — not just the syntax it accepts, but the semantics a query actually observes. The everyday SQL you already write behaves the same.
Safe for untrusted SQL
Safe by design — memory-safe cores, a pure built-in surface with no host access, and a deterministic cost ceiling on every query.
Many native cores
Built from scratch in Rust, Go, and TypeScript in lockstep — byte-identical, no reference implementation.
Built for
Running untrusted SQL
Let your users write and run their own queries. An adversarial query still cannot corrupt memory, reach the host, or exhaust resources.
Local dev & test
When production is PostgreSQL, run your test suite and local development against an embedded database — no server to provision, behavior you can rely on.
An embedded PostgreSQL companion
Embed jed at small scale, and scale up to PostgreSQL with the same SQL. One codebase, two footprints.
How it works here
This whole site is static — no backend. The jed engine is compiled to run in your browser: a native TypeScript core executes in a Web Worker, and the database tool persists real single-file databases to your browser’s origin-private file system (OPFS). The same engine ships as native Rust, Go, and TypeScript cores.