$ bns environments create --from staging

Staging On Demand.
For Every Team.

Create, clone, and manage staging environments from the UI. Any team member, no DevOps ticket.

No credit card required

B
Project / my-app / Environments
EnvironmentBranchStatus
staging-mainmainRunning
staging-v2release/v2.0Running
staging-qaqa/regressionStopped
staging-hotfixhotfix/paymentRunning
How Bunnyshell works — architecture diagram

$ cat how-it-works.md

How Bunnyshell works

01

Connect your repo

Link your GitHub, GitLab, or Bitbucket repository. Define your environment using Docker Compose, Helm, or Terraform — tools you already use.

GitHubGitHub
GitLabGitLab
BitbucketBitbucket
DockerDocker
HelmHelm
K8sK8s
02

Open a pull request

Bunnyshell auto-provisions an isolated, full-stack environment for every PR. Share the preview URL with your team.

PR #142env-142.preview.bunnyshell.dev• Running
PR #143env-143.preview.bunnyshell.dev• Running
PR #144env-144.preview.bunnyshell.dev• Running
03

Merge and move on

Tests pass, code is reviewed, PR merges. The environment auto-destroys. No cleanup. No surprise cloud bills.

End-to-end tests passed
Code review approved
Merged — environment destroyed

See it in action.

Spin up your first staging environment in under 30 minutes. Free tier — no credit card required.

01

One-Click Staging.
Zero Tickets.

Clone any environment instantly from the UI or CLI. Every developer, QA, PM can spin up a full staging stack without waiting for DevOps.

  • Clone from UI or CLIone click or one command to duplicate any existing staging environment
  • Full-stack replicationfrontend, backend, database, infrastructure — all cloned together
  • Self-service for all rolesdevelopers, QA, PMs, and designers create their own staging environments
  • Template-based creationdefine approved templates so every staging environment meets your standards
See environment cloning docs
B
Project / my-app / Clone Environment
$ bns environments clone --from staging-main --name staging-feat-checkout
▸ Cloning staging-main…
  ▸ Copying environment config… done
  ▸ Building frontend… done (38s)
  ▸ Building backend-api… done (42s)
  ▸ Starting postgres:15… done (8s)
  ▸ Seeding database… done (12s)
  ▸ Running healthchecks… all passing
✓ staging-feat-checkout ready in 2m 48s
  🌐 https://staging-feat-checkout.bunnyenv.com
02

Clone, Branch, Test.
Merge.

Clone a staging environment, connect it to a feature branch, test in isolation. Merge the PR, the environment cleans itself up.

  • Branch-linked stagingconnect any cloned environment to a feature branch for isolated testing
  • Auto-update on pushpush new commits and the staging environment redeploys automatically
  • Auto-destroy on mergePR merged or closed? The staging environment removes itself. Zero cleanup
  • Parallel testingmultiple teams test different features simultaneously — no staging contention
See lifecycle docs
B
Environments / staging-feat-checkout / Activity
TimeEventStatus
Mon 09:14Clone from staging-mainCreated
Mon 09:18Connected to feat/checkoutDeployed
Mon 14:30New commit pushedRedeployed
Tue 10:00QA testing completeApproved
Tue 11:15PR #312 mergedDestroying...
Tue 11:16Cleanup completeDestroyed
03

Auto-Sleep.
Auto-Wake.

Environments sleep at 8 PM, wake at 8 AM. Or set custom schedules. No forgotten staging servers running through the weekend.

  • Configurable schedulesset sleep and wake times per environment or apply org-wide defaults
  • Weekend shutdownautomatically stop staging environments Friday night, restart Monday morning
  • Instant wake on accesswake any sleeping environment with one click when you need it off-hours
  • Cost reduction by defaultmost teams cut staging cloud spend 40-60% with auto-sleep alone
See auto-sleep docs
B
Environments / staging-main / Schedule
# Auto-sleep schedule
sleep: 20:00 UTC (Mon–Fri)
wake:  08:00 UTC (Mon–Fri)
# Weekend policy
weekend: sleep (Sat 00:00 – Mon 08:00)
Status:
Running next sleep in 4h 22m
Environments on this schedule: 4
  staging-main · staging-v2 · staging-qa · staging-hotfix
04

Per-Environment
Cost Tracking.

Track cloud spend per staging environment via Kubecost integration. Know exactly what each team, branch, or feature costs.

  • Kubecost integrationper-environment CPU, memory, and cost breakdown updated in real time
  • Team-level reportingaggregate costs by team, project, or environment type for chargeback
  • Stopped = $0sleeping and stopped environments cost nothing. No forgotten resources
  • Budget alertsset spending thresholds and get notified before costs exceed expectations
See cost tracking docs
B
Project / my-app / Cost Overview (Kubecost)
EnvironmentCostCPUMemory
staging-main$4.82/day0.8 vCPU2.1 Gi
staging-v2$3.64/day0.6 vCPU1.8 Gi
staging-qa$0.00/day
staging-hotfix$2.18/day0.4 vCPU1.2 Gi
Total$10.64/day1.8 vCPU5.1 Gi

Staging that works
for your entire org.

Developers

Self-serve staging

Spin up a full staging environment from the UI. No tickets, no waiting, no shared environments.

QA Engineers

Dedicated test environments

Every test cycle gets its own staging. Run E2E, performance, and regression tests in isolation.

Product Managers

Preview any feature

Access staging environments for any PR. Review features before they ship — no setup required.

Platform Teams

Guardrails, not gates

Define templates, set resource limits, control who can create what. Self-service with governance.

Engineering Leaders

Track staging costs

Per-environment cost tracking. Know which teams and features drive cloud spend.

Release Managers

Staging that matches production

Same infrastructure definition, same config. What works in staging works in production.

Staging without the bottleneck.

Self-service staging for every team. Free tier includes 5 environments. No credit card required. Free white-glove onboarding.

Teams that made staging
self-service.

Enterprise-grade security.
Your data stays in your cloud.

Bunnyshell connects to YOUR Kubernetes cluster. Your code and data never leave your infrastructure. SOC 2, ISO 27001, and ISO 9001 compliant.

SOC 2
ISO 27001
ISO 9001

RBAC

Three-layer permission model: Policies, Resource Selectors, and Teams. Granular enough for enterprise.

SSO

Enterprise single sign-on. Integrate with your existing identity provider.

Network Isolation

Dedicated Kubernetes namespace per environment. Pods accessible only within their namespace.

Secrets Management

Environment variables and secrets handled securely. Never hard-coded, always encrypted.

IP Whitelisting

Restrict access to specific IP ranges. Control who can reach your environments.

Audit Logs

Full audit trail for every environment action. Who deployed what, when, and where.

Frequently asked
questions

Can’t find what you’re looking for? Talk to our team

Self-service staging means any team member — developer, QA, PM, or designer — can create a full-stack staging environment from the Bunnyshell UI or CLI without filing a DevOps ticket. Environments are cloned from existing templates, so they match your production stack automatically.

One click to a full staging stack.

Self-service staging for every team member. Free tier includes 5 environments. No credit card required. Free white-glove onboarding.