Your own server, not a row in someone else's table

Most AI builders run every app on shared infrastructure, in a shared database, within reach of the same agent that wrote it. A cloud project here gets a dedicated server by default (or joins one you already run) with PostgreSQL installed on that server, a domain, TLS, and a way to leave.

What runs where

Browser talks to the Builder; the Builder provisions and deploys to your own server, one per project by defaultYour browserchat · editor · terminalbuilder.seamai.proprovisions · deploys over SSHbills · registers domainsYour project's serverCloud VPS · EU ARM or US x86Caddy · TLS (Let's Encrypt)systemd proj-{slug} · NodePostgreSQL 16 (local)your-app.cloud.seamai.proor your own domain
  • One server per project by default. The Builder provisions a cloud VPS for the project and installs PostgreSQL 16 on it. You can also place more than one of your projects on a server you already have; each keeps its own database, hostname and process, and the cap is shown when you provision. Nothing is shared with another tenant.
  • A normal Linux service. The app runs under systemd as proj-{slug}; Caddy sits in front and gets a certificate from Let's Encrypt automatically.
  • Deploys over SSH. When you redeploy, the Builder sends the project to the server, installs dependencies, builds it and restarts the service.
  • Server backups. Automatic server backups are enabled for provisioned servers.

Regions and sizes

Read live from the same settings the product bills from. Servers are a flat monthly price on top of a paid plan.

RegionSizevCPUMemoryDiskPer month
Europe (nbg1)small48 GB80 GB$20
Europe (nbg1)medium816 GB160 GB$40
Europe (nbg1)large1632 GB320 GB$75
United States (ash)small48 GB160 GB$45
United States (ash)medium816 GB240 GB$80
United States (ash)large1632 GB360 GB$150

Domains and TLS

Every cloud project gets a *.cloud.seamai.pro hostname. Register a domain from inside the Builder or point one you already own at the server; Caddy provisions the certificate from Let's Encrypt and renews it.

Leaving: export and self-host

The project is a standard layout with no proprietary runtime. Download it as a ZIP or push it to a GitHub repository, then run it anywhere:

  1. Export: Download as ZIP from the workspace, or push to GitHub with your own token.
  2. On your machine or server: npm install.
  3. Set the environment your app expects (for cloud projects, DATABASE_URL pointing at a PostgreSQL you control).
  4. Build with the project's own script: npm run build.
  5. Run the built server under systemd, PM2 or a container, with a reverse proxy for TLS.

The docs walk through it in more detail.

What this costs, plainly

Cloud servers are available on paid plans and billed flat per server size; the sizes and prices above are the real ones. AI usage beyond your plan bills per 1K tokens. See pricing.

Start freeSee pricing