Skip to main content

Introduction

AppHaven hosts the applications you (or your AI agents) build, straight from a Git repository. You configure an app once, pointing it at a repo and describing it in a small manifest, and AppHaven takes it from a commit to a running app on a real domain over HTTPS. It builds your code, runs your containers, provisions your database, and keeps your data safe.

You work the way you already do: push code with Git, look at the result, ship it. AppHaven handles the building, the containers, the routing, and the certificates so you don't have to.

Who it's for​

AppHaven is built for European SMBs, internal-tool builders, and technical founders running custom apps, including the growing number of apps that AI agents help write. You should be comfortable with Git and a terminal. You do not need to know your way around containers, reverse proxies, or infrastructure: that is what the platform takes care of.

It is built durability first: run your applications reliably, keep their data safe, and recover quickly when something goes wrong.

The deploy flow​

A change moves through AppHaven in three steps:

  1. Push your code. Your agent, or you, pushes to Git. No bespoke CLI to learn, no pipeline to wire up.
  2. Look at a preview. Deploy any branch and it comes up as its own preview environment on its own URL, with its own containers and its own storage, so you can see exactly what changed before it goes anywhere near your users.
  3. Ship it. Deploy your production branch: one click in the console, or automatic on every push if you turn auto-deploy on.
push code
preview on its own URL
live in production

Previews are what let an agent iterate quickly: every branch can be running and clickable, while production only ever changes when the production branch does.

What makes AppHaven different​

Builds included. Point AppHaven at a repository with a Dockerfile and it builds your app from source on every deploy. There is no build pipeline to set up and no container registry to publish to, and you follow each build's log live in the console.

A managed database. Declare a database in your manifest and AppHaven provisions and operates it: credentials are generated for you and never appear in your repository, storage is managed, and the database is continuously backed up with point-in-time recovery. See Database.

Durability first. Persistent storage survives every redeploy, managed databases are backed up continuously with point-in-time recovery, and every deployment records exactly which commit it shipped. See Backups & recovery.

Isolated by design. Production, every preview, and every other customer's app each run in their own virtual machine, with their own operating system and their own private network. See How AppHaven runs your app.

European by design. AppHaven is run by a European company, in EU datacenters. You pick the region when you create an app, and your data stays there. This is a structural property of the platform, not a region toggle bolted onto a US service.

Where to go next​