Kilnbase · Manifesto Nº 1Draft 0.4 · building in publicWave 2 opens 12 January 2027

Less server.More software.

Kilnbase is an open-source backend that runs where your users are. A real database on the device, a sync engine that merges instead of overwriting, and one small server you can host yourself.

One email when your invite is ready. A build log on Fridays if you want it.

11,482developers are already waiting

What we are building toward

  • Less Round trips, more Local reads
  • Less Spinners, more Instant
  • Less Glue code, more Product
  • Less Lock-in, more Open source
  • Less YAML, more TypeScript
  • Less Cold starts, more Always on
  • Less Invalidation, more Sync
  • Less Online only, more Offline first
  • Less Retries, more Merges
  • Less Rented data, more Owned data
  • Less Polling, more Streams
  • Less Dashboards, more Files
  • Less Ceremony, more Shipping
  • Less Overwrites, more CRDTs
  • Less Hype, more Benchmarks
  • Less Vendors, more Contributors

01 — Principles

Eight things we will not compromise on.

We wrote these before we wrote the code. Every pull request, pricing decision and roadmap call gets checked against this list.

  1. 01Less Round tripsMore Local reads

    Reads come from a database on the device. The network is for sync, not for every tap.

  2. 02Less SpinnersMore Instant

    Writes land locally in under a millisecond and sync in the background. Loading states become rare.

  3. 03Less GlueMore Schema

    One schema defines tables, permissions and sync scope. No REST layer, no cache, no invalidation.

  4. 04Less Lock-inMore Open source

    Apache-2.0, all of it. The sync server you self-host is the exact code we would run for you.

  5. 05Less OverwritesMore Merges

    Concurrent edits merge deterministically. Nobody loses work because a phone went into a tunnel.

  6. 06Less YAMLMore Code

    Configuration is TypeScript you can test, diff and review like the rest of your app.

  7. 07Less RentMore Ownership

    Your data is a SQLite file you can copy, inspect and back up with cp. Leaving takes one command.

  8. 08Less HypeMore Benchmarks

    We publish numbers with the scripts to reproduce them, including the benchmarks we lose.

02 — The backend tax

Every app today is a thin client for someone else’s computer.

We put the database a continent away, then spend years hiding the distance: optimistic updates, caches, retry queues, loading skeletons. The user still waits. The team still writes the plumbing.

median mobile round trip
280ms
for a write to be acknowledged before the interface is allowed to move on.
to keep one list in sync
5services
API, database, cache, queue and a websocket gateway, each with its own way to fail.
of client code is plumbing
38%
loading, retry, cache and error states, in the twelve production apps we audited.
that work offline
0features
in most apps on a train, in a lift, or on hotel Wi-Fi. They simply stop.

The database belongs next to the user. The server should be the backup, not the bottleneck.

03 — A first look

Two commands. One schema. No API to write.

Define your tables once. Kilnbase creates the local database on every client, syncs it through a server you run, and gives you reactive queries that never wait on the network.

~/code/notes — zsh
npx kilnbase@alpha init notescreated kiln.config.tscreated schema/notes.tslocal db .kiln/notes.db (412 KB) npx kilnbase devsync server http://localhost:7700studio http://localhost:77012 clients connected · 0 conflictsmerged 14 ops from iphone-15 in 3 mspixel-8 offline · 6 ops queued locallypixel-8 back · merged 6 ops in 2 ms
schema/notes.tsapp/Notes.tsx
import { table, text, bool, now } from "kilnbase";
export const notes = table("notes", {
title: text(),
body: text().crdt(),
done: bool().default(false),
updatedAt: now(),
})
.allow("read", (u, row) => row.team === u.team)
.allow("write", (u, row) => row.owner === u.id)
.sync({ by: "team" });
// in any component
const open = useQuery(notes.where({ done: false }));
await notes.insert({ title: "Ship it" }); // 0.4 ms
TypeScript · UTF-8 · LFsynced · 0.4 ms

Preview of the alpha API. Names may still change; the build log will say when they do.

04 — What’s in the box

A backend, rearranged.

  • 01 / 04

    Sync engine

    Op-log replication with CRDT columns where you need them and last-writer-wins where you don’t. Partial sync by team, user or query.

    Merge
    deterministic
    Transport
    WebSocket · HTTP
  • 02 / 04

    Embedded database

    A SQLite-compatible store in the browser (OPFS), on iOS, Android and desktop. Real SQL, real indexes, reactive queries.

    Read p50
    0.08 ms
    Runtime
    412 KB wasm
  • 03 / 04

    Rules in the schema

    Permissions run on the device for instant feedback and again on the server for truth. One function, checked in both places.

    Auth
    OIDC · magic link
    Checks
    client + server
  • 04 / 04

    One binary to host

    The sync server is a single 18 MB binary with SQLite or Postgres behind it. Run it on a small VPS, or let us host it later.

    Binary
    18 MB
    Storage
    SQLite · Postgres

07 — Early contributors

Built in the open, by people who were tired of waiting on the network.

Contributors get the first invites, a say in the roadmap and their name in the release notes. Good first issues are labelled and kept small.

11,482
developers on the waitlist
8,412
stars on GitHub
214
contributors
1,306
members in Discord
  • Ingrid Halvorsen@ingridCo-founder · storage engine
  • Minh Tran@minhCo-founder · sync protocol
  • Arjun Mehta@arjunmRules engine
  • Yuki Tanaka@yukitReact hooks maintainer
  • Ana Lima@ana-limaDocs and examples
  • Rizal Pratama@rizalKotlin client
  • Aigerim Sadykova@aigerimOPFS store
  • Sofia Benali@sofiabBenchmarks
  • Omar Farouk@omarfPostgres backend
  • Imani Brooks@imaniCommunity
  • Rafael Ortega@rafa-oCLI
  • Kofi Mensah@kofiSwift client
  • Adaeze Okoro@adaezeOffline drafts
  • Jalen Carter@jalenStudio
  • Jonas Becker@jonasbMerge loop
  • Elena Rossi@elena-rDesign
“I opened an issue about offline drafts on a Tuesday. By Friday it was in the build log with my name next to it.”
Adaeze Okoro @adaeze · Offline drafts

08 — Questions

Straight answers.

Yes. The client libraries, the sync server and the database runtime are Apache-2.0. There is no open-core split: the hosted service, when it exists, will run the same code you can run yourself.

Wave 2 opens on 12 January 2027 with 2,000 seats, in signup order. People who have merged a pull request or filed a useful issue are invited first, whatever their position.

Self-hosting is free forever. Kilnbase Cloud will have a free tier and usage pricing, which we will publish in the build log before anyone is charged anything.

For data that users read and write, mostly yes. You can keep your existing services for payments, email or heavy jobs, and call them from server-side rules.

Today: browsers (Chrome, Safari, Firefox), Node and Bun. Swift and Kotlin clients are in progress on the roadmap. React is first-class; other frameworks use the plain client.

No, and we will not pretend otherwise. Expect breaking changes, flagged in the build log with a migration note each time.

We use it to send your invite and, only if you opt in, the Friday build log. It is never sold or shared. Unsubscribe with one click, or ask us to delete it.

09 — Join11,482 developers are already waiting

Less waiting.More building.

Get an invite to the alpha, follow the build every Friday, and help decide what we make next.

One email when your invite is ready. A build log on Fridays if you want it.