Syncs web and mobile clients
Every user sees a change the moment it happens, on web and mobile.
Data, sign-in and live updates in one backend that you or your coding agent publish in one step. Verft runs it and scales it, so you only build the app.
Changes go live in one step while your users stay connected, and any earlier version can go live again. See the three steps
read_at. An Option lets Verft add it without a migration.Tables are Rust structs and Actions are functions. Verft finds them by their attributes, so there is no list to keep.
The test context calls Actions as any Identity, moves the clock and fakes outbound HTTP, all in memory.
The generated TypeScript client subscribes to a Query and gets every change in commit order.
Every user sees a change the moment it happens, on web and mobile.
Email, magic links, passkeys, Google and Microsoft, without running an auth service.
Emails, payments and other outside calls retry on their own until they go through.
A release that would expose data is stopped before anything changes.
Data is private by default. When you open a table, one rule says who may see which rows, and Verft enforces it on every request.
Rust. The contract between a module and Verft is a language-neutral WASM interface, so other languages can follow.
No. The managed cloud runs them. A company that keeps data in-house can run a single-App server on its own infrastructure.
Durable tables in Postgres, one database per Environment. Ephemeral tables, such as presence, in Redis.
They stay connected. Their Subscriptions refresh, and calls already running finish on the old module.
Yes. verft dev starts a local server, publishes on every save and regenerates the TypeScript client.
Not yet. Verft is in development. Request early access and we email you when you can publish your first module.