Which IDEs are supported?

VS Code and JetBrains IDEs (IntelliJ, WebStorm, PyCharm, GoLand, PhpStorm, and others). You keep using your existing editor, extensions, keybindings, and settings — Bunnyshell handles the cloud connection.

How fast is file synchronization?

File sync is sub-second for most changes. Bunnyshell uses an optimized sync mechanism that watches for file changes and propagates them instantly to the remote container. It works reliably even on slower connections.

Can I debug remote applications?

Yes. Bunnyshell supports step-through debugging for Node.js, PHP (via Xdebug), and Java (via JDWP). Attach your IDE debugger to the remote process — set breakpoints, inspect variables, and step through code as if it were running locally.

Do I need Docker or Kubernetes installed locally?

No. That is the point. Your application runs on Kubernetes in the cloud. Your laptop only needs your IDE and the Bunnyshell CLI. No Docker Desktop, no local Kubernetes, no language runtimes, no conflicting dependencies.

How long does it take to set up?

Most teams have their first remote dev environment running in under 30 minutes. If you already have a bunnyshell.yaml or Docker Compose file, it is even faster. We also offer free white-glove onboarding to help you get started.

What happens if my internet connection drops?

Your code is saved locally in your IDE, so you never lose work. When your connection resumes, file sync catches up automatically. The cloud environment continues running independently — your services do not stop because your laptop disconnected.

Is there a free trial?

14-day full-feature trial, no credit card required. Includes a Bunnyshell-managed Kubernetes cluster so you can start immediately without connecting your own infrastructure.

$ bns remote-dev up

Code Locally.
Run in the Cloud.

Cloud dev environments that mirror production. Connect your IDE, start coding in minutes.

Start Free ↗Book a Demo

No credit card required

Remote Dev / my-app / Terminal

$ bns remote-dev up

▸ Connecting to cloud env… done

▸ Starting file sync… 42 files synced

▸ Attaching debugger… ready

Port forwarding:

3000 → localhost:3000 (frontend)

8080 → localhost:8080 (api)

5432 → localhost:5432 (postgres)

✓ Remote dev session active

Open http://localhost:3000

Used by engineering teams at

$ cat how-it-works.md

How Bunnyshell works

Connect your repo

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

GitHub

GitLab

Bitbucket

Docker

Helm

K8s

Open a pull request

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

PR #142→env-142.preview.bunnyshell.dev• Running

PR #143→env-143.preview.bunnyshell.dev• Running

PR #144→env-144.preview.bunnyshell.dev• Running

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.

Launch your first cloud dev environment in under 30 minutes. Free trial \u2014 no credit card required.

Start Free ↗Book a Demo

Local IDE.
Cloud Runtime.

VS Code or JetBrains — the tools you already know. Your code runs in a cloud environment that mirrors production. Edit locally, execute remotely. No Docker Desktop, no local dependencies, no conflicting versions.

✓VS Code & JetBrains — connect your preferred IDE to a cloud workspace with one command
✓Full-stack environment — your app, database, and services running together, just like production
✓Zero local dependencies — no Docker, no language runtimes, no conflicting versions on your laptop
✓Consistent across the team — every developer gets the same environment, every time

See remote dev docs →

Remote Dev / my-app / Terminal

$ bns remote-dev up

▸ Connecting to cloud env… done

▸ Starting file sync… 42 files synced

▸ Attaching debugger… ready

Port forwarding:

3000 → localhost:3000 (frontend)

8080 → localhost:8080 (api)

5432 → localhost:5432 (postgres)

✓ Remote dev session active

Open http://localhost:3000

Real-Time
File Sync.

Save a file. See the change in your cloud environment instantly. Bunnyshell syncs your local edits to the remote container in real time — no build step, no deploy wait. Hot-reload works exactly as you expect.

✓Sub-second sync — file changes propagate to your cloud environment as fast as saving locally
✓Hot-reload compatible — works with Webpack, Vite, Next.js, Nodemon, and any file-watch tool
✓Selective sync — configure which paths to sync and which to ignore (node_modules, .git)
✓Works over any connection — optimized for bandwidth. Reliable on hotel Wi-Fi, not just office fiber

See file sync docs →

Remote Dev / my-app / File Sync

Watching for changes…

↑ src/App.js → synced (12ms)

↑ src/components/Header.tsx → synced (8ms)

↑ src/api/routes.js → synced (15ms)

↻ Hot-reload triggered

Ignored:

node_modules/ · .git/ · dist/

↑ src/styles/main.css → synced (6ms)

↻ Hot-reload triggered

42 files synced 0 errors

Remote Debugging.
From Your IDE.

Set a breakpoint. Step through code running in the cloud. Inspect variables, evaluate expressions, trace execution — all from your local IDE. Same workflow as local debugging, but on production-like infrastructure.

✓Node.js debugging — attach your debugger to remote Node processes. Breakpoints, watches, call stacks
✓PHP debugging — Xdebug integration. Step through Laravel, Symfony, or vanilla PHP running in the cloud
✓Java debugging — JDWP remote attach. Debug Spring Boot, Quarkus, or any JVM app in cloud containers
✓Multi-service debugging — trace requests across frontend and backend running in the same environment

See debugging docs →

Remote Dev / my-app / Debug (Node.js)

● Breakpoint hit — server.js:42

41  async function getUser(req, res) {
42    const user = await db.findUser(req.params.id);
43    if (!user) return res.status(404).json({ error: 'Not found' });

Variables

req.params.id = "usr_93x"

req.method = "GET"

req.path = "/api/users/usr_93x"

Call Stack

getUser server.js:42

router router.js:18

handleReq http.js:7

Port Forwarding
& SSH Access.

Access any remote service on localhost. Forward database ports, API endpoints, or admin panels — as if running on your machine. SSH into any container for logs, migrations, or live troubleshooting.

✓Port forwarding — map remote ports to localhost. Access databases, queues, and APIs locally
✓SSH into containers — drop into any running container. Inspect logs, run migrations, troubleshoot live
✓Multiple services — forward ports from multiple containers simultaneously
✓CLI-driven — one command to forward, one command to connect. No UI clicks required

See port forwarding docs →

Remote Dev / my-app / Connections

$ bns port-forward --all

✓ localhost:3000 → frontend:3000 Active

✓ localhost:8080 → backend:8080 Active

✓ localhost:5432 → postgres:5432 Active

✓ localhost:6379 → redis:6379 Active

$ bns ssh backend

Connected to backend-api-7f8d4c (node:20-slim)

root@backend-api:~# npm run migrate

✓ Migrations applied (3 pending)

Built for every team member,
not just DevOps.

Developers

Open IDE, start coding

No conflicting dependencies. No setup guides. Connect your IDE to a cloud environment and start writing code. Every time.

New Hires

Day-one productivity

No 2-day onboarding to run the app locally. Spin up a complete environment in minutes and start contributing immediately.

Platform Teams

Standardize dev environments

Define environments in code, enforce across the org. Every developer gets the same stack, same versions, same config.

Remote Teams

Same experience, anywhere

Consistent regardless of location, OS, or hardware. Berlin or São Paulo — same environment, same performance.

QA Engineers

Test on real infrastructure

Access the same cloud environment developers use. Reproduce bugs on the exact same stack, every time.

Engineering Leaders

Cut onboarding time by 10x

New developer? One command to a working environment. Track time-to-first-commit across your org.

✦✦

Stop setting up. Start shipping.

Launch your first cloud dev environment in minutes. Free trial, no credit card required. Free white-glove onboarding.

Start Free ↗See It Live (15 min)

Teams that moved development
to the cloud.

“Manual tests on Argo CD PRs now take me seconds. When you review dozens of PRs a day, that's a game-changer.”

Michael CrenshawCore Team Member

“Automatically created BunnyShell environment based on PRs, speeding up the entire task implementation process.”

Jacob TobiaszCore Team Member

“The automation and scalability that Bunnyshell provides complements the DigitalOcean platform, empowering developers to build amazing products.”

Aaron GellerGP & Channel

“Websites don't die anymore, sales keep growing sustained by state-of-the-art tech scalability. Customers send thank you cards.”

Elif BolatCEO

Laura MichadCTO

“From a release once in 2-4 weeks to multiple times per week, and nobody's stressed about it.”

Catalin SporisCEO

“I can count on an integrated platform for managing our infrastructure — capabilities we don't have in-house, at a fraction of the cost.”

Gustavo HaramuraTeam Lead & Solution Architect

“I can do with Bunnyshell and a DevOps person what my clients are doing with 4 DevOps people.”

Radu DalbeaCTO

“Developers want convenience. They expect someone to translate their Docker Compose to the cloud. They're not going to rush to learn Kubernetes.”

Dianne RussellPlatform Engineer

“Bunnyshell was the only tool that handled our Helm + EKS setup without asking us to change everything.”

Arlene McCoyDevOps Engineer

“60+ microservices. Bunnyshell deploys them in parallel and lets us control which ones come first.”

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.

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.

A remote development environment runs your application stack in the cloud instead of on your laptop. You connect your local IDE (VS Code or JetBrains) to the cloud workspace, edit files locally, and your code executes remotely. You get production-like infrastructure without installing anything locally.