Værft is built on a small number of well-considered pieces — edge compute, managed data, git-native deploys, observability, security, and honest billing — each designed to fit the next. You assemble software, not infrastructure.
Your functions run as V8 isolates in the nearest of eighteen regions, with millisecond cold starts and a single predictable model: one module, one handler, zero containers.
Logs, traces, metrics, and exceptions share the same semantics, the same SQL-ish syntax, and the same alert router. Dashboards are Git-versioned.
Data and compute pin to the jurisdiction you choose. SSO on every paid plan, SCIM on Business, hardware keys on Fleet. Every config change is in an audit log you can export.
Start a project on the Hobby tier. Upgrade only when you need support, compliance, or scale — never features you should have had on day one.
Share your stack. A Værft solutions engineer sketches what a migration would look like — services, data, timeline, cost.