Early accessWe set it up with you

Application platform.
Any cloud, any server.

Run web apps, APIs, workers and databases on AWS, Google Cloud, Hetzner or your own hardware. Beep builds, releases, scales and monitors them, for one flat price per server.

  • Any provider
  • Servers managed for you
  • No per-app, seat or bandwidth fees
  1. queuedPush to main · 3f9c2e1 “Add checkout flow”
  2. buildingCloning acme/storefront on a managed builder
  3. buildingDetected Node.js 22 · Next.js 15 · pnpm
  4. buildingRailpack build, cached layers reused
  5. builtImage recorded · 3f9c2e1
  6. releasingRolling release · 2 replicas
  7. releasingHealth check GET /api/health → 200
  8. healthyTraffic moved · storefront.acme.com
$ git push origin main Releasing… Healthy in 41s

Any framework. Zero config.

  • Next.js
  • Django
  • Rails
  • Laravel
  • Go
  • Rust
  • Phoenix
  • Spring Boot
  • .NET
  • Bun
  • Deno
  • Dockerfile

Beep detects your framework and builds it for you, with caching between deploys. Monorepos, Dockerfiles and prebuilt images work too.

What you can run

One platform for the whole stack

Front ends, APIs, background jobs, cron and databases, deployed and managed side by side in one place.

  • Web services

    Next.js, Rails, Django, Go or anything that serves HTTP, live on a URL with HTTPS.

  • Static sites

    Served from Beep’s edge at no extra cost. Visitors never see a half-deployed site.

  • Workers

    Background jobs and queue consumers that run around the clock, private by default.

  • Cron jobs

    Run tasks on any schedule, in the time zone you choose.

  • Databases

    Postgres with pgvector and PostGIS, Redis and Valkey, connected to your services privately.

  • MCP servers

    Host MCP servers right next to the APIs your agents call.

One-click templates

  • n8n
  • Plausible
  • Umami
  • Uptime Kuma
  • MinIO
  • Ghost

Platform

Everything you expect from a platform.

Builds, deploys, scaling, domains and observability, handled for every service you run, on whichever cloud you run it.

Scale

Scale out across clouds

Start on one machine and grow to a fleet across providers. Beep adds replicas when traffic rises, and nothing is ever billed per service.

Zero-downtime deploys

A bad deploy never reaches your users

Every new version is checked before it takes traffic, and the old one keeps serving until it passes. Roll back instantly, with no rebuild.

Domains

Custom domains with automatic HTTPS

Every service is live on a URL the moment it deploys. Add your own domain and certificates are issued and renewed for you. Password-protect staging with one switch.

Observability

Logs, metrics and alerts built in

Search logs, watch requests, errors and latency for every service, and get alerted when something breaks. 30 days of history on every plan.

Drive it from your terminal or your agent. The Beep CLI and MCP server give you and your coding agents everything the dashboard can do: deploy, roll back, read logs and change settings.

Any compute

Your bill follows your servers, not your app count.

Platforms like Vercel, Railway and Render charge per app, per seat or per gigabyte of bandwidth, on compute they rent to you. Beep charges one flat plan per server and nothing for bandwidth, requests or extra services. Your provider bills the servers on its own terms.

  • Any providerAWS, Google Cloud, Hetzner, Scaleway, any VPS or your own hardware. Mix them in one workspace, or let Beep create servers in your Hetzner account.
  • Use all of itRun many services on one machine, or spread them across a fleet. Spare capacity runs your next service instead of adding to the bill.
  • Infrastructure handled for youBeep sets up, secures and updates every machine, so you never manage a server yourself.
Monthly cost, same stacklower is better
  • Beep + Hetzner$16.09
  • Railway≈ $40
  • Vercel≈ $56
  • Render≈ $68
  • Fly.io≈ $94

Seven small apps, two Postgres databases and an open pull request preview, under 100 GB of egress. Published list prices, checked October 2026; the Beep figure includes the server you pay your provider for. Bandwidth is left out on every side, so on platforms that meter it, heavy traffic widens the gap. See every comparison

Reliability

Built for the days something goes wrong.

Production-grade reliability on every service from its first deploy. Nothing to configure, no runbooks to write.

  • Self-healingIf an app crashes, it’s back up before anyone notices. Whatever you deployed is exactly what keeps running.
  • Instant rollbacksGo back to any previous deploy in one click. Nothing is rebuilt.
  • AutoscalingReplicas are added when traffic climbs, spread across machines so one failure doesn’t take you down.
  • AlertsYour team hears about crashes, failed deploys and error spikes before your users do.
  • Private networkingServices talk over an encrypted private network. Databases and workers stay private unless you choose to make them public.
  • Secure by defaultEvery machine is locked down from the first minute and kept up to date automatically.

Coming soon: managed database backups. The full list of controls shows what is available, in beta and not yet built.

Where it runs

Your servers, your provider, your choice.

Mix clouds in one workspace and move services between them without changing how you deploy. Every option gets the same platform and the same dashboard.

  • Beep Cloud
  • Hetzner
  • awsAWS
  • Google Cloud
  • DigitalOcean
  • Vultr
  • OVHcloud
  • Scaleway
  • Any VPS

One-click provisioning on Hetzner today. Any other cloud or VPS connects with one command.

  • Bring your own serverAvailableConnect a Linux machine from any cloud or VPS provider with one command.Your provider bills you for the server. It counts toward your plan’s BYOS servers.
  • Your cloud account, provisioned by BeepHetzner todayConnect your Hetzner account and Beep creates machines in it for you.The servers stay in your account, on your provider’s invoice, and count as BYOS servers.
  • Beep CloudEarly accessCompute supplied by Beep, so you don’t need a cloud account at all. Opening to early-access workspaces in Europe first.Billed hourly as a separate line on your Beep invoice. Never counts toward your plan’s server limit.

Setting up a specific provider? See provider guides.

How it works

From zero to production

The same three steps for your first service and your fiftieth. No config files to write.

// 01 · Connect

Connect any cloud or server

  • Any providerAWS, Google Cloud, Hetzner or any VPS. Beep can also create machines in your Hetzner account.
  • Ready in minutesBeep sets everything up and locks it down. Nothing to install by hand.

// 02 · Deploy

Deploy from Git, with a preview for every pull request

  • Deploy on pushEvery push to your GitHub branch deploys automatically. GitLab repositories deploy in one click.
  • Pull request previewsEach GitHub pull request gets its own environment, removed when it closes.

// 03 · Operate

Roll back, promote, and stay in control

  • Instant rollbacksGo back to any healthy deploy in one click.
  • Environments and rolesPromote staging to production, with roles and per-project access for your team.

Migration

Move one service first. Then the rest.

Moving production is a project, not a button. We plan it with you, start where the risk is lowest and keep your current platform running until each service has proved itself on Beep.

  1. 01Review what you runWe go through your services, databases, traffic, deploy process and current bill with you.
  2. 02Choose what movesStateless web services, workers and cron jobs move most easily. Anything that should stay where it is, stays.
  3. 03Design the targetServers, providers, environments and networking, written down before anything changes.
  4. 04Start with a non-critical serviceA staging copy, an internal tool or a worker runs on Beep next to your current platform.
  5. 05Validate itCompare builds, release behaviour, latency, resource use and cost against what you run today.
  6. 06Expand graduallyMove the next services and databases one at a time, with DNS cut over only when each is ready.

Pricing

Start small. Grow without replatforming.

One platform plan per workspace, priced by servers rather than services or seats. Compute is separate and always visible: your provider bills your servers, or Beep Cloud, in early access, bills by the hour.

  • Hobby

    For side projects on one server.

    $3/month

    Same price billed yearly

    • 1 BYOS server
    • 1 member
    • 300 build minutes / mo
    • One environment
    Get early access
  • Developer

    For developers shipping production apps.

    $9/month

    $7.20/mo billed yearly

    • 3 BYOS servers
    • 3 members
    • 1,000 build minutes / mo
    • Environments and PR previews
    Get early access
  • Team

    For teams

    For teams running several services in production.

    $49/month

    $39.20/mo billed yearly

    • 10 BYOS servers
    • Unlimited members
    • 5,000 build minutes / mo
    • Environments and PR previews
    Get early access
  • Business

    For companies running a larger fleet.

    $149/month

    $119.20/mo billed yearly

    • 30 BYOS servers
    • Unlimited members
    • 15,000 build minutes / mo
    • Environments and PR previews
    Get early access

Enterprise · from $499/month

For production migrations and larger estates.

Hands-on migration with Beep engineers · Custom server and build limits · Annual agreement and invoicing · A shared Slack channel · Support terms agreed in writing

Discuss your infrastructure

BYOS (bring your own server) servers are ones you connect or Beep creates in your cloud account; extra ones are $2/month each from Developer up. Beep Cloud servers never count toward the limit. No per-service or bandwidth fees, and no per-seat fees on Team and Business. Compare every plan

FAQ

Questions, answered

Anything else? Email hello@usebeep.dev.

Who is Beep for?

Teams who like the experience of platforms such as Vercel, Railway or Render but want it on compute they choose, and growing software companies running several services in production that want a platform without building a platform team. Both use the same product; larger teams add more servers, people and support.

Is Beep available now?

Beep is in early access. Join the list and we’ll set up your workspace with you. If you run production for a business, talk to us and we’ll plan the move together.

Do I need to know Docker or DevOps?

No. Beep detects your stack, builds it with Railpack and runs it for you. If you already have a Dockerfile or a prebuilt image, Beep uses that instead.

Does Beep back up our databases?

Not yet. Postgres, Redis and Valkey run on your servers today, but managed backups and restore are still being built. Until then, keep your own backups, for example with a scheduled pg_dump job.

Can I SSH into my servers?

No. Once Beep sets a server up, SSH is closed to the internet and only Beep’s encrypted private network can reach the server. To look inside a running service, open a shell in its container from the dashboard, next to its logs and metrics. Beep Cloud servers don’t run SSH at all.

Does Beep charge for bandwidth?

No. Beep doesn’t meter bandwidth, requests or function calls. Traffic on your servers is billed by your provider on its own terms: many VPS providers include several terabytes a month, while AWS and Google Cloud charge for egress.

Can we move one service at a time?

Yes, and we recommend it. Run a non-critical service on Beep next to your current platform, compare it, then move the rest and switch DNS one service at a time.

What happens when we use all our build minutes?

Running apps keep running. Wait for the monthly reset, build on your own connected server without using Beep build minutes, or, on monthly paid plans, opt in to $5 per extra 1,000 minutes.

Early access

Your cloud, run like a platform.

Join early access and we’ll set up your workspace. Bring servers from any provider, or let Beep create them.

No spam. We’ll only email you about your workspace.

Running production for a company? Discuss your infrastructure →