The backend platform for the new world

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.

Your app’s publish history, module by module

Changes go live in one step while your users stay connected, and any earlier version can go live again. See the three steps

From Rust code to a live app in 3 steps

  1. Declare tables and actions in Rust

    Tables are Rust structs and Actions are functions. Verft finds them by their attributes, so there is no list to keep.

  2. Test the Rust module with cargo test

    The test context calls Actions as any Identity, moves the clock and fakes outbound HTTP, all in memory.

  3. Connect your frontend to the backend

    The generated TypeScript client subscribes to a Query and gets every change in commit order.

Built into the platform. Live data, sign-in, jobs and publish checks.

Syncs web and mobile clients

Every user sees a change the moment it happens, on web and mobile.

Signs people in to your backend

Email, magic links, passkeys, Google and Microsoft, without running an auth service.

Sign-in connections
3 connected
  • GoogleOAuth for every Identity Connected
  • Microsoft Entra IDAny tenant, claims included Connected
  • GitHubOAuth for developers Connected
  • AppleSign in with Apple on iOS Connected

Retries jobs until they succeed

Emails, payments and other outside calls retry on their own until they go through.

  • Job sync_invoices failed5 of 5 tries usedRe-run
  • Job send_receipt finishedAfter 2 retries, 14 s apart
  • Schedule nightly_cleanup ranOnce, as every night

Refuses unsafe backend publishes

A release that would expose data is stopped before anything changes.

Publish checks for module 44
4 of 5
  • Message has a Visibility rule
  • Room has a Visibility rule
  • author says what happens on delete
  • STRIPE_KEY has a value
  • Set SMTP_HOST for staging

Verft shows each caller only their rows

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.

See what a publish checks

Questions

Which language do Verft modules use?

Rust. The contract between a module and Verft is a language-neutral WASM interface, so other languages can follow.

Do I run servers for my backend?

No. The managed cloud runs them. A company that keeps data in-house can run a single-App server on its own infrastructure.

Where does Verft keep my data?

Durable tables in Postgres, one database per Environment. Ephemeral tables, such as presence, in Redis.

What happens to clients when Verft publishes?

They stay connected. Their Subscriptions refresh, and calls already running finish on the old module.

Can I run Verft on my laptop?

Yes. verft dev starts a local server, publishes on every save and regenerates the TypeScript client.

Can I use Verft today?

Not yet. Verft is in development. Request early access and we email you when you can publish your first module.