Preview environments

A preview for every pull request.

Every GitHub pull request gets its own environment and URL, running on your own servers and removed when the pull request closes. Developer and above include active previews.

Get early access →Talk to us

Preview environments

Source: GitHub pull requests
URL: On edge.usebeep.sh, with HTTPS
Lifetime: Removed when the pull request closes
Active previews: 3 on Developer, 10 on Team, and 25 on Business

How it works.

One per pull request

Open a pull request and its preview builds and deploys on its own, with a URL to share.

Cleaned up for you

When the pull request closes, its environment is removed.

On servers you pay for

Previews run on your servers, so each one adds nothing to the plan price.

Protected if you want

Password-protect staging before anyone outside the team sees it.

See it run

git push. Everything else is handled.

Every push to your tracked branch builds and releases on its own. Traffic moves only when health checks pass, and every GitHub pull request gets its own preview environment, removed when it closes.

deploy · apilive

→ build detected · railpack · layer cache warm

✓ image built

✓ health checks passed new version first

✓ traffic moved to api.acme.com zero downtime

✓ https certificate issued · auto-renews

›_Zero-config deploys

acme / checkout-flowPreviewsLogs

Add Apple Pay at checkout

Preview livePR #214de4a91c

https://↗

Build railpackHTTPS autoRemoved when PR closesPlan Developer+

Migrate cart state to server actions

PR #209checkout-pr-209.edge.usebeep.sh

⎇Preview environmentsDeveloper+

Preview environments, answered.

Straight answers. Anything missing, ask us directly.

Which plans include previews?

Developer and above, with 3 on Developer, 10 on Team, and 25 on Business active at once; Hobby has none. They run on your servers rather than on billed instances.

Do previews work with GitLab?

Pushes from GitHub and GitLab both build and release. Pull request previews are available for GitHub pull requests.

Guides that use it.

Deploy Next.jsRun your Next.js app as a long-lived Node server on a machine you choose, with previews for every pull request and no per-function billing.→Deploy RailsDeploy Rails with Puma on a server you own: db:migrate before each release, zero-downtime rollouts and one flat plan for the whole app.→

More features.

Zero-downtime releasesBeep starts the new version first and moves traffic only once it passes its health checks. If something is wrong, roll back to an earlier image in one click, with no rebuild.→Managed databasesRun Postgres 16 to 18 with pgvector and PostGIS, plus Redis and Valkey, on the servers your apps already use. Back up to Beep’s storage or your own S3-compatible bucket.→Custom domains and HTTPSEvery service starts with a URL on edge.usebeep.sh. Point a CNAME at Beep and certificates are issued and renewed for you; you never touch a certificate file.→Logs and metricsLive-tail build and runtime logs. Track CPU, memory, requests, error rate and p95 latency for every service, and get an alert when errors or latency climb.→Server securityBeep sets up every server the same way: inbound traffic denied, app ports reachable only from its edge, security updates applied automatically, and containers restarted if they crash.→Static sitesHost static sites on Beep’s edge at no extra cost within your plan’s storage, with skew protection so visitors never mix old and new assets during a deploy.→

Own your infrastructure again.

Plans from $1 a month, billed per server, never per service.

Early access · We’ll set up your workspace

Or talk to us →