Emails
Send and receive mail straight from your service.
Save a file and it is live at its own URL. It sleeps when idle and costs nothing asleep. Your users' data stays in Europe.
The defaults are sensible enough that there is almost nothing to configure: you deploy, and the URL that comes back is already serving traffic.
$ frontback deploy service api production → building ✓ built (1.8s) ✓ artifact 8487be7b 41 files, 812 KiB ✓ v7 released to production ✓ live (0.9s) https://api.run.frontback.dev
$ curl https://api.run.frontback.dev hello from europe
Send and receive mail straight from your service.
Code that runs itself, on a schedule in plain words.
Every deploy is kept. Going back takes one click.
Test in staging, then promote to production when ready.
production
staging
Code branches. The database branches with it.
Staging is a fork of production, data included.
No adapters, no special entry points. If it builds, it runs.
Every runtime and library →Every template deploys into your organisation as a real project, live at its own URL. Then it is yours: open the editor and change anything, or tell the AI what you want instead.
Builds, rehearses on a dry run branch with a fork of your data, and deploys when you say so, even from your phone on the go.
An AI chat in the console, on models hosted in Europe. Or bring your own agent: the MCP server and the skill hand it the same tools.
Your users are in Europe.
Now their data is, too.
Two plans. Read both sentences and take the one that sounds like you.
I am shipping a side project.
I am running a real app.
I am a business or an enterprise.
Free to start. Scales to zero while you sleep.
Go beyond what seems possible.