Beep for business
Scale your software, not your infrastructure team.
For SaaS teams running several apps, APIs, workers and databases. Beep gives you one platform for all of them, on the cloud you already use, and we move production over with you one service at a time.
What Beep solves
The problems that show up after the first few services.
Most teams don’t need Kubernetes or a platform team. They need deploys that don’t depend on one person, servers nobody has to look after and a bill they can explain.
Deploys depend on one person
Scripts, SSH sessions and tribal knowledge. Beep gives every service the same release flow: previews, health-checked releases and a history of every deploy.
Managed hosting bills grow per service
Every worker, database, preview, seat and gigabyte of bandwidth is another line item. On Beep you pay for servers and one plan, and add services without adding fees.
Servers someone has to babysit
Beep sets up, secures and patches every machine. Only your apps face the internet, and nobody on your team has to log into a server again.
No shared view of production
Logs on one box, metrics in another tool, nobody sure what is deployed where. Beep shows every service’s releases, logs and metrics in one place.
Who does what
What Beep runs, and what stays yours.
Here’s how the work splits once your services run on Beep.
Beep runs
- Builds from your Git repository, your Dockerfile or a prebuilt image
- Releases, health checks, restarts and rollbacks
- Certificates, custom domains and routing through Beep’s edge
- Setting up, securing and patching every server
- The private network between your servers and the edge
- Collecting logs and metrics for every service
You keep
- Your provider account, server sizes and how many replicas each service runs
- Your code, its dependencies and their vulnerabilities
- Database backups, until managed backups ship
- Your data, your compliance obligations and who you give access to
- Paging and on-call rotations
Migration
A migration plan before anything moves.
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.
- 01Review what you runWe go through your services, databases, traffic, deploy process and current bill with you.
- 02Choose what movesStateless web services, workers and cron jobs move most easily. Anything that should stay where it is, stays.
- 03Design the targetServers, providers, environments and networking, written down before anything changes.
- 04Start with a non-critical serviceA staging copy, an internal tool or a worker runs on Beep next to your current platform.
- 05Validate itCompare builds, release behaviour, latency, resource use and cost against what you run today.
- 06Expand graduallyMove the next services and databases one at a time, with DNS cut over only when each is ready.
Security and operations
Where every feature stands.
Each item is marked with where it stands today.
- AvailableHealth-checked releases and rollbacksRolling and blue-green releases with HTTP or TCP health checks; any earlier release can be re-released without a rebuild.
- AvailablePrivate networkingAn encrypted private network between your servers and Beep’s edge. Workers and databases have no public address unless you open a port.
- AvailableLocked-down, patched serversEvery server is closed to the internet by default and gets security updates automatically. SSH is closed once a server is set up.
- AvailableRoles and project accessOwner, Admin, Developer and Viewer roles, custom roles and per-project grants.
- AvailableTwo-factor sign-inAuthenticator apps, passkeys and recovery codes, and a workspace setting that requires them.
- AvailableEnvironments and promotionStaging and custom environments, promotion to production and a preview environment per GitHub pull request.
- AvailableActivity historyA workspace activity feed of deploys and changes, kept for 13 months.
- AvailableLogs and metricsRuntime logs and per-service metrics kept for 30 days; build output for 14 days.
- BetaAlerts on error rate and latencyShown in the dashboard and enabled per workspace during early access. Delivery to email or Slack is not built yet.
- BetaBeep Cloud computeServers supplied and billed by Beep, opening to early-access workspaces in Europe.
- Not yetManaged database backups and restorePostgres, Redis and Valkey run today, but Beep does not back them up yet. Keep your own backups until this ships.
- Not yetSAML single sign-on and API tokensSign-in is by email, Google or GitHub, with two-factor.
- Not yetDeployment approvals and audit log exportAnyone with deploy rights can release; the activity feed is viewable in the dashboard only.
- Not yetAutoscaling and multi-region failoverReplica counts are set by you. Beep’s edge runs in Europe.
- Not yetUptime SLA, status page and compliance reportsWe don’t offer a contractual uptime SLA or hold SOC 2 today, and we’ll say so in any agreement.
Pricing and support
Know what you pay for.
The platform fee and the compute are separate lines, so you can see exactly what Beep charges.
- Platform plan
- Growing teams usually start on Team at $49 a month (10 BYOS servers) or Business at $149 (30 BYOS servers), both with unlimited members and 30 days of logs. Both are self-serve, with no call required. Extra BYOS servers are $2 a month each, and Beep Cloud servers never count toward the limit.
- Compute
- Servers in your own cloud account are billed to you by your provider. Beep Cloud servers, in early access, are billed hourly as a separate line on your Beep invoice.
- Enterprise agreements, from $499 a month
- Hands-on migration with Beep engineers. Custom server and build limits. Annual agreement and invoicing. A shared Slack channel. Support terms agreed in writing. Priced to the size of the estate and the migration work involved.
Talk to us
Tell us what you run.
We read every message. We’ll reply with questions or a time to review your setup together, and we’ll tell you plainly if Beep isn’t the right fit.