Company
We build the boring pipe between your database and everything that copies it.
Every application eventually keeps a second copy of its data: a search index, a cache, a read model for analytics. And every team eventually finds out that the second copy is wrong. A deploy skipped a write, a job retried twice, a delete never made it across.
Maya and Tomás met in 2021 on an incident bridge about exactly that, and started Driftbase in March 2023 with a simple rule: the database is the source of truth, and the only honest record of what changed is its write-ahead log. Everything downstream should be derived from that log, in order, and be rebuildable at any time.
Today Driftbase moves a little over 40 billion change events a month for about 300 teams, from two-person startups to a top-ten US grocery delivery service. We’re nine people, based in Portland with two engineers in Lisbon and Osaka, and backed by Boldline Ventures and a group of database people we admire.
What we believe
- Correctness first. A fast pipeline that loses a delete is a slow outage.
- Open by default. The CLI is Apache-2.0, and the hosted service runs the same binary.
- Boring is a feature. We would rather you forget we exist.
Team
- Maya OkaforCo-founder & CEO
Ran the Heroku Postgres follower fleet for five years.
- Tomás LindqvistCo-founder & CTO
Built the indexing pipeline at Algolia’s Paris office.
- Jun WatanabeFounding engineer
Wrote the keyset backfiller and most of the sink adapters.
- Rosa DelgadoHead of customer engineering
Has migrated more Elasticsearch clusters than she will admit.
Work with us
We hire slowly and remotely within UTC−8 to UTC+9. If replication slots and idempotent writes sound like fun, get in touch even if nothing is posted.