$ bns environments deploy --type production

Production-Grade.
From Day One.

Run production workloads on Bunnyshell. Monitoring, alerting, autoscaling, and 24/7 support — built in.

NewNo credit card required

B
Production / Environments / Overview
EnvironmentRegionPodsUptimeStatus
prod-us-eastus-east-124/2499.98%Healthy
prod-eu-westeu-west-118/1899.99%Healthy
prod-ap-southap-south-112/1299.97%Healthy
Total pods: 54/54Avg uptime: 99.98%Last deploy: 14m ago
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.

Deploy your first production environment in under 30 minutes. Free tier — no credit card required.

01

Same Definition.
Dev to Prod.

The bunnyshell.yaml that runs your dev environment runs your production environment. Same definition, production-grade infrastructure. No config drift, no environment-specific hacks.

  • One YAML, all stagesthe same bunnyshell.yaml powers dev, staging, and production environments
  • No config driftenvironment variables, secrets, and infrastructure defined once, promoted across stages
  • Git-versioned infrastructureevery production change tracked in your repository. Full audit trail by default
  • Promote with confidencewhat you tested in dev is exactly what runs in production. No surprises
See environment definitions
B
Production / prod-us-east / bunnyshell.yaml
# Same definition — dev to prod
kind: Environment
name: prod-us-east
type: production
components:
  - kind: Helm
    name: frontend
    replicas: 3
    autoscale: true
  - kind: Helm
    name: backend-api
    replicas: 4
    autoscale: true
  - kind: Terraform
    name: infra
    module: rds + elasticache
02

Monitoring
& Alerting.

Built-in health checks, resource monitoring, and alerting. Know when something is wrong before your users do. CPU, memory, disk, network, and custom metrics — all visible from one dashboard.

  • Health checksHTTP, TCP, and exec probes for every component. Automatic restart on failure
  • Resource monitoringCPU, memory, disk, and network metrics per pod, per component, per environment
  • Custom alert rulesset thresholds for CPU, memory, latency, and error rates. Get notified via Slack, PagerDuty, or webhook
  • Incident timelinecorrelate deployments with metric changes. See exactly which deploy caused the spike
See monitoring docs
B
Production / prod-us-east / Monitoring
CPU 34%Memory 58%Disk 22%Network OK
Health checks (last 5m)
frontend /healthz 200 OK 12ms
backend-api /health 200 OK 8ms
worker /ready 200 OK 5ms
postgres pg_isready accepting 3ms
Alerts (24h)
✓ No alerts triggered
Active rules: CPU > 80%, Memory > 85%, p99 > 500ms, error rate > 1%
03

Autoscaling
& High Availability.

Horizontal pod autoscaling, multi-region deployments, automated failover. Scale with your traffic, not your ops team. Handle traffic spikes without manual intervention.

  • Horizontal pod autoscalingscale pods based on CPU, memory, or custom metrics. Min and max replicas per component
  • Multi-region deploymentsdeploy to multiple regions from the same definition. Latency-based routing built in
  • Automated failoverunhealthy pods replaced automatically. Traffic rerouted in seconds, not minutes
  • Zero-downtime deploysrolling updates with configurable surge and unavailability. No maintenance windows
See autoscaling docs
B
Production / prod-us-east / Autoscaling
TimeEventReplicasCPU
08:00Traffic baseline328%
09:15Traffic spike detected3 → 672%
09:16HPA scaling up645%
12:30Peak traffic868%
18:00Traffic normalizing8 → 432%
22:00Off-peak baseline315%
04

Termination
Protection.

Lock critical environments. Prevent accidental deletions, enforce approval workflows for production changes. Sleep well knowing your production environments are safe.

  • Environment lockslock production environments against accidental deletion. Explicit unlock required
  • Approval workflowsrequire team lead or platform team approval before deploying to production
  • Rollback on failureautomatic rollback to the last healthy deployment if health checks fail post-deploy
  • Change audit trailevery production change logged with who, what, when, and the approval chain
See protection docs
B
Production / Settings / Protection Rules
Environment locks
🔒 prod-us-east Locked — deletion blocked
🔒 prod-eu-west Locked — deletion blocked
🔒 prod-ap-south Locked — deletion blocked
Approval workflows
Deploy to production — requires 2 approvals
Scale down below 3 replicas — requires lead approval
Modify infra components — requires platform team
$ bns env delete prod-us-east
Error: Environment is protected. Remove lock or get approval to proceed.

Production infrastructure
for every role.

DevOps Engineers

Production on autopilot

Autoscaling, monitoring, and alerting configured once. Focus on architecture, not firefighting. Infrastructure as code, promoted across stages.

Developers

Deploy with confidence

Same YAML from dev to prod. No environment-specific config to manage. Push, merge, and know your code runs the same way everywhere.

Platform Teams

Standardize production

Define production templates with security, scaling, and monitoring built in. Teams self-serve within guardrails you control.

SREs

Observability built in

Health checks, resource metrics, and alerting from day one. Correlate deploys with incidents. Mean time to resolution drops.

Engineering Leaders

Reduce ops overhead

Fewer DevOps tickets, fewer late-night pages. Production runs itself. Track deployment frequency and reliability with built-in metrics.

CTOs

Enterprise-grade infrastructure

SOC 2 compliant, multi-region, auto-scaling. Production infrastructure that meets enterprise requirements without the enterprise price tag.

Same YAML. Dev to prod.

Deploy your first production environment in minutes. Free tier, no credit card required. Free white-glove onboarding.

Teams running production
on Bunnyshell.

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

Yes. Bunnyshell manages environments on your Kubernetes clusters, including production. The same bunnyshell.yaml that defines your dev environment defines your production environment — with production-grade features like autoscaling, monitoring, alerting, and termination protection enabled.

Production infrastructure that scales with you.

Start free — deploy your first production environment in minutes. Free tier, no credit card required. Free white-glove onboarding.