G2

Valentin I.

CTO

Small-Business (50 or fewer emp.)

10/5/2026

"From dev to production: simple deploys for large apps"

5/5

What do you like best about Bunnyshell?

What I like best is how simple it is to run and redeploy a full environment. Our dev environment for a large PHP monolith runs on Bunnyshell, together with its cron worker, and each part is a separate component. I can redeploy only the components that changed, so a deploy for QA is fast and does not disturb the rest of the stack.

The CLI is the second thing I value. One bns command deploys the environment, so we put it directly into our release workflow: merge to the dev branch, deploy, notify the team, and move the ticket to QA. Nobody has to open a dashboard or ask DevOps for help.

The environment definition is a single YAML file, close to Docker Compose, so developers who know our local Docker setup understand it quickly. Review collected by and hosted on G2.com.

What do you dislike about Bunnyshell?

When a pipeline fails, the cause is not always clear from the first output. I have to look through the events and the pipeline logs to find the step that failed. A short, clear error summary at the end of a failed deploy would save time. Review collected by and hosted on G2.com.

What problems is Bunnyshell solving and how is that benefiting you?

The main benefit is a shorter path from a merged change to a change that QA can test. We connected the deploy to our workflow: the team is notified in Slack when the deploy starts and when it finishes, and the ticket moves to QA only after a successful deploy. QA always knows if the environment is safe to test on, and developers do not wait for another person to do the deploy.

The second benefit is that developers stay focused on the product. We do not have to maintain the Kubernetes setup for this environment ourselves. Review collected by and hosted on G2.com.