Make your web app live in seconds

Every new account gets €5 of credit, valid for 30 days. No credit card, no card check, nothing to claim: it is on the balance the moment you sign up.

Charges are drawn from the credit first and from your real balance only after it is gone, and the two are always shown as separate numbers on the billing page. The credit is not a top-up: it never counts toward your lifetime spend, so it does not unlock the tiers or the production email sending that a real payment does.

What it buys: the entry Nano plans are €3/mo each. One Nano web service on its own runs the full 30 days and leaves credit unspent. A web service plus a Nano PostgreSQL costs €6 a month, so the pair runs about 25 days before the credit is gone. Top up any amount from €5 to carry it past that. Static sites are not billed at all and never touch the credit.

Two limits apply while you are running on credit alone. You get one service of each type (one web service, one PostgreSQL, one Redis, one cron job), and static sites are not counted against that. And you can only pick the entry plans: Nano, or Starter for the types that have no Nano. Standard and above need a real payment first, because €5 should not buy 8 vCPU for an afternoon. A single top-up of €5 lifts both.

When the credit runs out, or when the 30 days are up (whichever comes first), running services stop and the remainder is written off. Your real balance is never touched. Full breakdown on the pricing page.

No cold starts while you're using the app. Runsite keeps containers warm as long as they receive traffic.

On Nano, the entry plan, a web service that gets zero requests for 14 consecutive days is suspended to free up shared capacity. The next incoming request wakes it back up (usually within a few seconds). Your code, environment variables, and storage are preserved.

In practice this only affects truly abandoned projects. Any live demo, bot, or side project with even occasional visitors will never sleep. Starter and above (from €5/mo) skip the inactivity sleep entirely and stay always-on with dedicated CPU.

Your services stop. Nothing is deleted on the spot, and nothing is charged to a card you never gave us.

We email you on day 23 and day 29 of the credit, and again when services actually stop, so the wall is never a surprise. Top up any amount from €5 and press Start: a web service redeploys, a PostgreSQL database comes back with its volume exactly as it was.

Storage is held for 7 days after the stop. After that the PostgreSQL volume is reclaimed and the final backup is kept for 12 months, so a project you come back to months later can still be restored by topping up. Redis is in-memory and is not backed up, so export anything you need before the deadline.

Static sites are unaffected. They are never billed and never stop.

You set a monthly budget in the dashboard, say €20. Services consume resources, we track usage against that cap in real time.

Hit 80% and you get an email. Hit 100% and services pause automatically. They stop running but aren't deleted, and nothing more gets charged. Raise the cap or wait for the next cycle to resume.

The cap is a hard stop, not a friendly email after the damage is done.

Yes. Add your domain in the dashboard, point your DNS at Runsite (A record for apex, CNAME for subdomains), and SSL is issued via Let's Encrypt in minutes. Renewals are automatic.

Attach multiple custom domains to a single service. Wildcard domains work on paid plans.

Every service also gets a free *.runsite.app subdomain, handy for staging or a quick demo. Here's how to set up a custom domain step by step.

No. No per-seat, per-user, or per-team charges. Your whole team, 2 people or 200, can deploy, manage services, and read logs at no extra cost.

You pay for the infrastructure your services actually use: CPU, memory, storage. That's a different model from Heroku or Railway, where per-seat fees snowball as teams grow.

Shared dashboards, deploy permissions, and audit logs come with every plan.

EU only. All of them. Your app data, database backups, and object storage never leave EU borders.

Every account is GDPR-compliant by default and ships with a signed Data Processing Agreement. No negotiation, no upcharge, no sales call.

That matters if you handle EU customer data or fall under the Digital Services Act. Unlike US-based platforms that bolt on EU regions as an extra, Runsite is EU by design.

No. Proxies, VPN endpoints, VLESS/Xray/V2Ray and Shadowsocks nodes, and traffic tunnels of any kind are prohibited on every plan, paid ones included. Services identified as running them are blocked without notice and without a refund.

This is not a bandwidth policy we might relax later. Relay traffic is what a shared platform cannot absorb: it saturates egress that other customers paid for, and it puts our IP ranges on blocklists that take months to leave.

Runsite is built for applications: web services, APIs, background jobs, and the databases behind them. If your workload is a legitimate app that happens to open outbound connections (a scraper, a bot, a webhook relay), that is fine. Anything whose purpose is to forward third-party traffic is not. Section 4 of the Terms of Service sets this out in full.

Runsite is a European platform, built for European teams. The infrastructure runs entirely inside the EU, we invoice in euro, and a GDPR-compliant DPA comes with every account, so if you are looking for European hosting for a European product, this is what it was built for.

You don't have to be an EU company to sign up. Customers in the UK, Switzerland, and other countries are welcome, and their data stays in the EU either way.

We do not serve countries and territories under comprehensive EU, UN, UK, or US sanctions (as of August 2026 that means Russia, Belarus, Iran, North Korea, Cuba, Myanmar, and the occupied territories of Ukraine), or any person or company on an applicable sanctions list. Accounts we identify as falling into that category are suspended, and payments from those jurisdictions are declined. Section 5 of the Terms of Service sets this out in full.