Billed per server
One server or twenty, arranged your way
Keep everything on one machine or spread services across a fleet from different providers. Plans include servers, and nothing is billed per service.
Early accessThe waitlist is open
Your own server.
None of the ops.
Push code and Beep builds, releases, and runs it on servers you control, with HTTPS, rollbacks, logs, and metrics built in.
- queuedPush to main · 3f9c2e1 “Add checkout flow”
- buildingCloning acme/storefront on a managed builder0.8s
- buildingDetected Node.js 22 · Next.js 15 · pnpm
- buildingRailpack build, cached layers reused31.4s
- builtImage recorded · 3f9c2e1
- releasingRolling release · 2 replicas
- releasingHealth check GET /api/health → 2001.2s
- healthyTraffic moved · storefront.acme.com
$ git push origin main
Releasing…
Healthy in 41s
- queuedPush to main · 91be0d4 “Export invoices as CSV”
- buildingCloning acme/billing on build-01, your build server1.1s
- buildingDetected Python 3.12 · Django 5.1 · uv
- buildingRailpack build · collectstatic, gunicorn44.9s
- builtImage recorded · 91be0d4
- releasingBlue-green release · 1 replica
- releasingHealth check GET /healthz → 2002.3s
- healthyTraffic switched · billing.acme.com
$ git push origin main
Releasing…
Healthy in 56s
- queuedPush to main · c04a7e2 “Retry failed webhooks”
- buildingCloning acme/events on a managed builder0.6s
- buildingDetected Go 1.24 module · ./cmd/api
- buildingRailpack build · go build18.7s
- builtImage recorded · c04a7e2
- releasingRolling release · 3 replicas across 2 servers
- releasingTCP health check :8080 → open0.4s
- healthyTraffic moved · events.acme.com
$ git push origin main
Releasing…
Healthy in 29s
- queuedDeploy ghcr.io/acme/worker:2.3.1
- buildingPrebuilt image, nothing to build
- builtPrivate registry credentials verified
- releasingPulling image on hel1-jobs-016.2s
- releasingRecreate release · worker, no public address
- releasingRestart policy: always
- releasingContainer started · process running1.9s
- healthyworker is healthy on hel1-jobs-01
Deployed from the dashboard
Releasing…
Healthy in 12s
Bring any stack. Beep works out the build.
- Next.js
- Django
- Rails
- Laravel
- Go
- Rust
- Phoenix
- Spring Boot
- .NET
- Bun
- Deno
- Dockerfile
Railpack detects the runtime and framework and caches layers between pushes. Monorepos, Dockerfiles, and prebuilt images work too.
Platform
Everything a platform does. On servers you control.
Beep installs a small agent on each server, then takes care of builds, releases, routing, certificates, and telemetry, so running a server stops being your job.
Zero-downtime releases
Traffic moves only when health checks pass
Rolling and blue-green releases start the new version first and shift traffic once it is healthy. Rolling back re-releases an earlier image, with no rebuild.
Automatic HTTPS
Domains and certificates, handled
Every service gets a URL on edge.usebeep.sh. Point a CNAME at Beep and certificates are issued and renewed for you. Password-protect staging, or open a TCP port for a database.
Logs and metrics
See what’s happening while it happens
Live-tail build and runtime logs. Track CPU, memory, requests, error rate, and p95 latency per service, and set alerts for when errors or latency climb.
How it works
From bare server to production
Three steps, no YAML to write and no Dockerfile required.
// 01 · Add a server
Bring a server, or get one from Beep
- From any providerBeep Cloud, your own cloud account, or any Ubuntu or Debian VPS.
- Ready in minutesBeep installs its runtime and agent, then locks the server down.
// 02 · Push to deploy
Push to deploy, with a preview for every pull request
- GitHub and GitLabEvery push to your tracked branch builds and releases on its own.
- Pull request previewsEach GitHub pull request gets its own environment, removed when it closes.
// 03 · Operate
Roll back, promote, and stay in control
- Rollbacks without rebuildsRe-release any healthy deployment in one click.
- Environments and rolesPromote staging to production, with per-project access for your team.
Your servers
Any cloud or VPS, locked down by default
Bring a server from any provider, or get one from Beep Cloud. Every server gets the same hardened setup.
- Beep Cloud
- Hetzner
- awsAWS
- Google Cloud
- DigitalOcean
- Vultr
- OVHcloud
- Scaleway
- Any VPS
One-click provisioning today. Any other Ubuntu or Debian server is added over SSH.
- Firewall on from the startInbound traffic is denied by default. App ports are reachable only from Beep’s edge, over an encrypted private network.
- Managed end to endBeep owns the host setup, so nothing drifts and Beep stays responsible for its security. Debug from a container shell in the dashboard.
- Patched automaticallyUnattended security updates and fail2ban are configured on every server Beep sets up.
- Self-healingCrashed containers restart. If a server drifts from what you deployed, Beep releases it back into shape.
What you can run
One platform for the whole stack
Front end, back end, background work, and data, on whichever servers you choose, all from one dashboard.
Web services
Next.js, Rails, Django, Go, and anything else that listens on a port gets a URL and HTTPS.
Static sites
Hosted on Beep’s edge at no extra cost within your plan’s storage, with skew protection so visitors never mix old and new assets.
Workers
Queue consumers and long-running processes that stay private, with no public address.
Scheduled jobs
Cron schedules in the time zone you choose. Each job runs, then exits.
Databases
Postgres 16 to 18 with pgvector and PostGIS, plus Redis and Valkey. Back up to Beep’s storage or your own S3-compatible bucket.
MCP servers
Deploy HTTP-based MCP servers as web services, next to the APIs your agents call.
One-click templates
- n8n
- Plausible
- Umami
- Uptime Kuma
- MinIO
- Ghost
Pricing
Room for your next stage.
From your first project to a business running on Beep. Choose the capacity your work needs.
Save 20% yearly on Developer, Team & Business.
Server costs are separate. No per-app fees.
Hobby
For side projects.
Get early access$1$1/month
Billed monthly$12 billed yearlyNo annual discount
- 1 server you can connect
- 1 person in your workspace
- 300 build minutes / monthFor builds on Beep’s shared build platform.
- 1 build at a time
- 24 hours of log history
One server for your side projects. Upgrade when you need more.
Developer
For developers shipping production apps.
Get early access$9≈$7/month
Billed monthly$86.40 billed yearly
- 5 servers you can connect
- 3 people in your workspace
- 1,000 build minutes / monthFor builds on Beep’s shared build platform.
- 1 build at a time
- 7 days of log history
Additional servers: $2/server/month
Team
RecommendedFor small teams shipping together.
Get early access$29≈$23/month
Billed monthly$278.40 billed yearly
- 15 servers you can connect
- 10 people in your workspace
- 3,000 build minutes / monthFor builds on Beep’s shared build platform.
- 3 builds at a time
- 30 days of log history
Additional servers: $2/server/month
Business
For businesses running many services.
Get early access$99≈$79/month
Billed monthly$950.40 billed yearly
- 50 servers you can connect
- 25 people in your workspace
- 10,000 build minutes / monthFor builds on Beep’s shared build platform.
- 5 builds at a time
- 90 days of log history
Additional servers: $2/server/month
What are build minutes?
Your plan includes a monthly allowance for building your apps on Beep’s shared build platform. These builds run on Beep’s infrastructure, keeping build work off the servers running your apps.
You can also build and deploy on your own connected servers without using this allowance. If you build on the same server as your live apps, builds compete for CPU and memory and may slow those apps down.
On a standard Beep build machine, a five-minute build uses five minutes of your monthly allowance. A machine with twice the CPU power uses ten minutes for the same five-minute build. Waiting in the queue does not count, and these minutes do not limit how long your app stays online.
The essentials, on every plan
- Deploy when you push code
- Release updates and roll back
- Automatic HTTPS and custom domains
- One-click Postgres, Redis, and Valkey
- Backups to your own storage account
- Logs and metrics
- Build and deploy on your own server
- An app terminal in your dashboard
Compare everything included
| What’s included | Hobby | Developer | Team | Business |
|---|---|---|---|---|
| Servers you can connect | 1 | 5 | 15 | 50 |
| People in your workspace | 1 | 3 | 10 | 25 |
| Build minutes on Beep / month | 300 | 1,000 | 3,000 | 10,000 |
| Builds running at the same time | 1 | 1 | 3 | 5 |
| App preview versions at a time | 0 | 3 | 10 | 25 |
| Separate test and production setups | Not included | Included | Included | Included |
| App logs saved / month | 100 MB | 1 GB | 10 GB | 50 GB |
| How long app logs are kept | 24 hours | 7 days | 30 days | 90 days |
| Storage for app versions & build files | 1 GB | 10 GB | 50 GB | 200 GB |
| Additional servers | Upgrade required | $2/server/mo | $2/server/mo | $2/server/mo |
What else will I pay for?
Servers that run your apps
Beep Cloud servers are a separate charge on your Beep invoice. With your own cloud account or existing server, you pay your provider directly. Your app’s data and databases use storage on that server.
Extra build minutes
Developer, Team, and Business monthly subscriptions can opt into paid builds at $5 for each additional 1,000 build minutes, measured as explained above. This option is unavailable on Hobby and annual subscriptions. When your allowance runs out, wait for it to reset or build on your own server without using Beep build minutes. Apps already running stay online.
Backup storage
Save backups with your own storage provider, using an S3-compatible service, or store them with Beep for $0.05 per GB stored for a month. You pay for backup storage separately on every plan, from the first GB.
Additional servers
Developer, Team, and Business can connect more servers for an additional Beep fee of $2 per server per month. You also pay for the server itself. A server used only to prepare app releases still counts toward this limit. Hobby must upgrade to connect a second server.
Early-access packages. Limits for preview versions, stored files, and app logs are proposed for launch. Your Beep build-minute allowance and the amount of app logs you can save reset monthly, even if you pay yearly. Storage limits describe how much you can keep at once. Faster build machines use more of your Beep build-minute allowance; the standard machine has 2 vCPUs. Builds may wait when machines are busy. Storage for app versions and build files includes container images, cached build files, and static website files. Log history covers the logs saved within your monthly limit. Building on your own server uses no Beep build minutes, but files stored with Beep still count toward your storage limit. Hobby has no annual discount.
Need help choosing? Talk to us.
FAQ
Questions, answered
Anything else? Email hello@usebeep.sh.
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.
Can I SSH into my servers?
No, and that’s deliberate. Beep manages each host end to end, so manual changes can’t conflict with its setup and Beep can stay responsible for security. To debug, open a shell inside any container from the dashboard, right next to your logs and metrics.
What happens when I use all my Beep build minutes?
You can wait for your monthly allowance to reset, or continue building and deploying on your own connected server without using Beep build minutes. Existing applications keep running. Developer, Team, and Business monthly subscriptions can also opt into paid builds at $5 per additional 1,000 build minutes with a payment method on file. A minute on the standard build machine uses one minute; a machine with twice the CPU power uses two. Extra paid build minutes is not available on Hobby or annual subscriptions.
Can Beep prepare several app updates at once?
Hobby and Developer can run one build at a time, Team can run three, and Business can run five. These limits apply across your workspace. Builds may wait if Beep’s build machines are busy, but waiting time does not use your monthly Beep build-minute allowance.
Where do my builds run?
Your plan includes build minutes on Beep’s shared build platform, so build work runs on Beep’s infrastructure. You can also build and deploy on your own connected server without using those minutes. Building on the same server as your live apps competes for CPU and memory and may slow those apps down. A separate build server counts toward your plan’s server limit, so Hobby must upgrade to connect a second server. App versions and build files stored with Beep still count toward your storage limit.
Plans from $1 a month
Ship on servers you own.
Join early access and we’ll set up your workspace. Bring a server from any provider, or start on Beep Cloud.