Card
Five ways to arrange the same container — a feature grid, a pricing table, a magazine index, a services list and a team page.
Everything the deploy step should have done already
Six things you would otherwise wire together yourself, working the moment you connect a repository.
Edge routing
Requests resolve at the nearest of 38 regions, so a user in Jakarta waits the same 40ms as one in Frankfurt.
Instant rollback
Every deploy keeps its own immutable URL. Reverting a bad release is one click and takes effect globally in seconds.
Preview branches
Each pull request gets a live environment with seeded data, ready to share before anything touches production.
Zero-config caching
Static assets, API responses and images are cached with sensible defaults you can override per route.
Secrets that stay secret
Environment values are encrypted per project and never printed in build logs, even on failure.
Usage you can predict
Hard spending caps, per-project budgets and an alert before you cross any threshold you set.
Pricing that stops surprising you
Every plan includes unlimited projects and unlimited collaborators. You pay for build capacity, nothing else.
For side projects and everything you build on a Sunday.
- 1 concurrent build
- 100GB bandwidth
- Community support
- Preview deployments
For teams shipping to customers every week.
- 12 concurrent builds
- 1TB bandwidth included
- Password-protected previews
- Email support in 4 hours
- Analytics and Web Vitals
For organisations with procurement and a security team.
- Unlimited concurrency
- SAML SSO and SCIM
- 99.95% uptime SLA
- Named solutions engineer
- Invoiced annually
Prices in USD. VAT added where applicable.
The Journal, issue eleven
What we learned rewriting our scheduler for the third time
Two rewrites failed because we optimised for throughput before we understood the shape of the work. The third started with a week of measuring nothing but queue depth.
Density is a feature, not a default
Why we shipped three row heights instead of picking the one we liked best.
The written-first meeting, two years on
We replaced status meetings with documents. Here is what actually stuck.
Four ways to work with us
Every engagement is run by the same two partners from the first call to the final handover. We take on four clients at a time so nothing waits in a queue.
Brand identity
Naming, wordmark, type system and the rules that keep it coherent once fifty people start using it.
Product design
Interface design from first flow to shipped release, working inside your repository rather than beside it.
Design systems
A component library your engineers actually adopt, with the documentation and governance to keep it alive.
Marketing sites
The site that carries the launch — written, designed and built as one piece of work by the same two people.
Eleven of us, and no layer in between
Everyone here talks to customers. The four below happen to answer the most email.
Amara Lindqvist
Co-founder, CEO
Previously built payments infrastructure at Klarna.
Daniel Okafor
Co-founder, CTO
Wrote the first version of our scheduler on a train.
Yuki Tanaka
Head of Design
Cares more about empty states than anyone should.
Sofia Marchetti
Head of Support
Answers more tickets than the rest of us combined.