Helm7

Run your entire app stack, end to end, from $12 a month.

Supabase, Neon, Vercel and Fly.io, replaced by one platform that is easy to run and is far cheaper to run. Your app, Postgres, auth, storage, jobs and domains, driven from a dashboard, a terminal or an AI agent.

Free for 72 hours. No card, and no email if you are an agent.

Powering apps for

  1. Acme
  2. production
Plan ready

New Product

Repository
github.com/acme/acme-app
Region
Falkenstein

What it needs

  • Postgres

    Version 18, pgvector available

  • Auth

    Sign-in for your users

  • Storage

    Files, with no egress charge

  • Custom domain

    Certificate included

Plan

Nothing applied yet

  1. create productAcme eu-central
  2. create environmentproduction
  3. create serviceweb shared-0.25, sleeps when idle
  4. create databaseprimary Postgres 18
  5. change secretDATABASE_URL set on production
  6. create authproduction email
  7. create bucketuploads private
  8. create domainacme.com certificate issued once DNS resolves
Estimated usage$2.11–4.38/month

Inside the $12 Builder minimum, so that is the bill. Largest cost: service (shared-0.25).

Nothing here is irreversible.

Switch a part off and the plan, the requests and the cost change with it. The prices are the estimator's real output for Falkenstein; the Product is an example.

Most applications are billed twice.

One company runs the front end. Another runs the database, the auth and the files. They bill separately and fail separately, and neither can tell you what the whole thing costs.

Read the full comparison
People on the team
3

Vercel

Monthly invoice

  • Pro, 3 seats$60
Total$60

Supabase

Monthly invoice

  • Pro$25
  • Point-in-time recovery, 7 days$100
  • Custom domain$10
Total$135

Two invoices, before usage$195

Helm7

Monthly invoice

  • Pro minimum$29
  • 3 peopleSeats are not charged$0.00
  • Point-in-time recoveryIncluded on Pro$0.00
  • Custom domainIncluded$0.00
Total$29

One invoice, before usage$29

Vercel and Supabase figures are their published list prices, read on 22 September 2026. Usage is extra on every side of this; on Helm7 it draws down against the minimum instead of being added to it.

Everything the application needs, in one place.

A Product holds your services, Postgres, auth, storage, jobs, domains and variables. Delete it and all of it goes. Make a preview and all of it comes along.

How the platform fits together

Built from git. One call to roll back.

  1. Acme
  2. production
  3. web

Deployments of web, newest first

  • a1f3c2eAdd the pricing pageLive
  • 9bd01aaFix the login redirect
  • 77e4b19First deploy

Build log for a1f3c2e

  1. Cloned main
  2. Detected Next.js, npm, Node 22
  3. No Dockerfile in the repository, so one was generated
  4. npm ci
  5. next build
  6. Started the new container and waited for it to answer
  7. Moved traffic to the new container

Know the price before you build it.

Every change comes back as a plan first: what gets created, what it costs a month, and what can't be undone. Plans are free and change nothing. This is the estimator they use.

How pricing works
  1. Acme
  2. Estimate
Nothing is created

Web service

Sleeps when idle, wakes on the next request

Background worker

Never sleeps, has no time limit. Workers start on Pro.

1 GB
5 GB
1

Estimated usage

$0.64–1.34/month

  • service (shared-0.25, sleeps when idle)$0.58
  • Postgres (1 GB)$0.34
  • object storage (5 GB, no egress charge)$0.08
  • custom domain$0.00

On Builder, you pay

$12/month

Usage sits inside the $12 minimum, so the minimum is the whole bill.

› The same question from an agent

cost_estimate

{
  "resources": [
    {
      "type": "service",
      "instance": "shared-0.25"
    },
    {
      "type": "database",
      "storage_gb": 1
    },
    {
      "type": "storage",
      "storage_gb": 5
    },
    {
      "type": "domain",
      "count": 1
    }
  ]
}

Let an agent drive. Keep the limits.

Agents get the same 66 operations people do, over MCP. Every key has scopes, a spend cap and an expiry, and a call past the cap is refused before anything is spent.

How agent access works
  1. release-bot
  2. MCP session
1 of 4 calls
  1. 1Find out what this key can do before planning anything.

    whoami {}
    {
      "key": {
        "scopes": [
          "database:write",
          "deployment:write",
          "domain:write",
          "product:read",
          "product:write"
        ],
        "capabilities": [
          "may_deploy"
        ],
        "product_id": "prd_7k2m9x4qw1nv",
        "budget_usd": 5,
        "spent_usd": 0,
        "budget_remaining_usd": 5
      }
    }

Every response is what the API returns for this call.

  1. Agent keys
  2. release-bot
Spend cap
$5.00/month$0.00 spent

Any call that would cost more is refused.

Expires
In 8 hours, and it cannot extend itself
Scopes
deployment:writedatabase:writeproduct:readproduct:writedomain:writemay_deploy
Reach
One Product, and never more than the person who made the key. Tools it cannot use are left out of its tool list altogether.
One definition, every surface
The REST API, the MCP server, the SDK and llms.txt are generated from one catalogue of 66 operations, so they cannot drift apart. 36 of them can be dry-run.
Sign-up with no account
cloud_init gives an agent a workspace with no email and no card. It expires, so it is for trying things. A person claims it to keep it.
A manual written for models
llms.txt is the whole surface in plain text, leading with the rules that prevent expensive mistakes.

Let an agent test it. Keep the password.

Test accounts are temporary users in your product that an agent or CI can sign in as. The password and 2FA seed are encrypted and never listed. An agent gets a lease on them for the length of one run, and every checkout is logged.

How test accounts work
  • One call or one click

    Created in the product’s own auth and tagged as a test user.

  • Expires on its own

    Give it hours, and it deletes itself.

  • 2FA codes on demand

    Generated on Helm7’s side. The seed stays put.

  • Every checkout logged

    Rotate or delete whenever you like.

Hosted in the EU.

Falkenstein, Germany and Helsinki, Finland. Your data stays in the region you pick. There is no US region yet, and we would rather say so here than in a support ticket.

Falkensteineu-centralHelsinkieu-north

Priced like infrastructure, not like seats.

You might have two people and thirty agents, so nobody is charged per seat. Each price is a minimum monthly spend. Usage draws down against it, and you only pay more if you use more.

Full pricing
  • Trial

    Free

    For trying it, including by an agent with no account.

  • Builder

    $12/month

    For one application in production.

  • Pro

    $29/month

    For several applications that need to stay up.

  • Scale

    $99/month

    For applications where an outage costs money.

Questions people ask first.

Something missing? [email protected] reaches a person.

  • What is Helm7?

    Helm7 is a hosting platform that runs a whole web application in one place: the app itself, its Postgres database, auth, file storage, background jobs and custom domains. You can drive it from a dashboard, a REST API, a CLI or an AI agent over MCP, and every change is planned and priced before it is applied.

  • Is it an alternative to Vercel and Supabase?

    Yes, for teams that use the two together. Vercel runs the front end and Supabase runs the backend; Helm7 runs both on one bill with no per-seat charge. It is newer and smaller than either, and it only runs in the EU today, so the comparison page lists the cases where you should stay where you are.

  • How much does it cost to host a Next.js app?

    For a small app, the $12 Builder minimum is usually the whole bill. A Next.js service that sleeps when idle, with Postgres, auth, a storage bucket and a custom domain, is estimated at $2.11–4.38 a month in usage, which draws down against the minimum. Pro is $29 and adds workers, scheduled jobs and point-in-time recovery.

  • What does planning a change mean?

    Every change can be run as a dry run first. It returns what would be created, changed or destroyed, what the result would cost per month, and anything that cannot be undone, without doing any of it. It works the way terraform plan does for infrastructure code, and it is free.

  • Can an AI agent use it safely?

    Yes. Agents connect over MCP and get the same 66 operations as the REST API. Each agent key has its own scopes, an optional monthly spend cap and an expiry, can never do more than the person who created it, and is refused before spending past its cap.

  • Where is my application hosted?

    In Falkenstein, Germany and Helsinki, Finland. There is no US region yet, so users in North America will see more latency than on a platform with servers there.

Start with a plan. Apply it when you like it.

72 hours on the trial, no card. Point it at a repository and read what comes back.