Bunnyshell

Preview environments for every pull request

Bunnyshell is an environment automation platform. For each pull request it creates a full-stack, isolated copy of an application in seconds, and it removes that copy once the change is merged. The company says this lets developers test a change in a production-like setting without queuing for a shared staging server. It also says more than 30,000 engineers use the platform. Environments can be created from the user interface, from the command line or through Git workflows, so that the code and its environment stay in step.

Development, production and AI sandboxes

Beyond preview environments, the platform offers cloud development environments that give developers every service and dependency without a local setup, with hot reload connected to the cloud. Staging and production environments can be created and cloned from a user interface without a DevOps ticket. The company says production workloads come with 24/7 support, monitoring, alerting and autoscaling. It also offers AI sandboxes for agents, scripts and jobs, which it describes as isolated environments with fast start-up and no exposure of the host system.

Cost and lifecycle control

Environments pause when they are idle and are destroyed when the pull request closes, and the company says customers do not pay for uptime nobody uses. Frontend and backend services build independently, and an image is reused where the runtime has not changed. Services start in dependency order so that the environment is ready as quickly as possible. Project-level rules can set availability windows and a budget for each environment. QA, performance testing and sales demonstration environments are offered as on-demand copies of production.

Security and deployment model

The platform connects to the customer's own Kubernetes cluster, so the company says code and data stay within the customer's infrastructure. Each environment gets its own namespace. Access is set by role, so privileges can differ for each user, team, project and environment. Single sign-on can be connected to an existing identity provider. Secrets are encrypted and kept out of the code, and every environment action is recorded in an audit trail showing who deployed what and when. The company says it is SOC 2, ISO 27001 and ISO 9001 compliant. Environments are defined as code in a single configuration file, so each one can be reproduced and governed.