Resources

We write down what we learn.

Engineering notes, postmortems, the changelog and the operational status of every region — the material an architect reads before putting a vendor in a design doc.

Engineering · 18 min read

Why we put the write-ahead log on a zonal tier — and what it cost us

Sub-millisecond appends bought us a 6× write-latency advantage and a zonal failure domain we then had to engineer away. The gray-failure circuit breaker, the 30 ms abandonment rule, and the two production incidents that taught us to build it.

Read the post →
write path · p50 by tier
zonal append tier24 ms
standard object storage163 ms
same code path, one storage class apart
Writing

From the engineering blog

All posts →
{{ p.tag }} {{ p.date }}

{{ p.title }}

{{ p.excerpt }}

Changelog

Shipped recently

Subscribe →
{{ c.date }} {{ c.tag }} {{ c.title }} {{ c.body }}
System status All systems normal
{{ s.region }} {{ s.code }} {{ s.latency }} {{ s.uptime }}
Full status history →

Community

Design partners get a shared channel with the engineers who wrote the write path. Everyone else gets the same people in public.

Trust

Everything security review will ask for.

Available before you sign anything, not after. Where a certification is in progress we say so rather than implying it is done.

Certified

SOC 2 Type II

Report available under NDA. Continuous control monitoring, annual audit.

Available

HIPAA BAA

Signed at the Scale tier. No enterprise minimum, no usage premium.

In progress

FedRAMP Moderate

Via Assured Workloads. Target Q2 2027 — do not plan a federal launch around it yet.

Available

GDPR & DPA

EU data residency in europe-west4. Subprocessor list published and versioned.

Get the engineering notes, not a newsletter.

One email when we publish something substantial. Roughly twice a month, never about a funding round.

Subscribe