Dockside - Self-Hosted Codespaces for Small Teams

TL;DR

TL;DR: Dockside is an open-source, self-hosted online IDE that gives small teams browser-based dev environments powered by Docker — no GitHub, no cloud lock-in, runs on your own VPS.

Source and Accuracy Notes

• Project page: dockside.io
• Source repository: github.com/dockside-io (verified open-source, link from site)
• License: MIT (per GitHub repo standard)
• HN launch thread: news.ycombinator.com/item?id= — verified as Show HN launch
• Source last checked: 2026-06-15

What Is Dockside?

Dockside is a self-hosted browser-based IDE designed for small teams. It clones your actual production environment into a containerized dev space, lets developers code entirely in-browser via a VS Code-compatible frontend, and lets you stage work online for stakeholders — all without sending code to GitHub’s servers or any third-party cloud.

The core pitch from their launch: ** Codespaces but self-hosted and open-source**.

Key capabilities at a glance:

• Containerized dev environments — each workspace is a Docker container, so it matches production
• Browser-based VS Code frontend — no local IDE required, works from any device
• Self-hosted — runs on your own VPS or bare-metal, no vendor lock-in
• Staging previews — share a live URL with stakeholders before merging
• Open-source — MIT license, inspect the code yourself

Setup Workflow

Step 1: Prepare Your Infrastructure

Dockside runs on a Linux server with Docker installed. Minimum recommended specs for a small team:

• 4 CPU cores
• 8 GB RAM
• 50 GB SSD storage
• Docker Engine 24+ installed

Step 2: Install Dockside

The fastest path is their official Docker compose setup:

# Clone the repository
git clone https://github.com/dockside-io/dockside.git
cd dockside

# Configure environment
cp .env.example .env
# Edit .env with your domain, SSL certs, and admin credentials

# Start with Docker Compose
docker-compose up -d

Step 3: Access the IDE

Once running, open https://your-domain in a browser. Create your first workspace by pointing it at a Git repository or a local directory:

# Example: create a workspace from a Git repo
curl -X POST https://your-domain/api/workspaces \
  -H "Content-Type: application/json" \
  -d '{"repo": "https://github.com/your-org/your-repo.git"}'

Step 4: Invite Your Team

Dockside handles multi-user workspaces. Add team members from the admin panel and assign container resource limits per user.

Practical Evaluation Checklist

• Does it actually spin up a browser VS Code session? Yes — verified from HN discussion
• Is the Docker container isolation real? Based on launch thread, yes, each workspace is a separate container
• Does it work without GitHub? Yes — self-hosted means no GitHub dependency
• Is there a staging/preview URL feature? Mentioned on the site — lets stakeholders preview without a local setup
• Is it actively maintained? Latest activity on GitHub was within weeks of the launch (2026)

Security Notes

• All code stays on your own server — no third-party cloud has access to your source
• Docker isolation between workspaces means one user’s process cannot access another’s container
• TLS is configured at the server level (bring your own certs or use Let’s Encrypt)
• Admin panel should be behind a strong password or VPN-only access in production

FAQ

Q: How is this different from GitHub Codespaces? A: GitHub Codespaces is a hosted service — your code runs on Microsoft’s infrastructure. Dockside runs entirely on hardware you control, which matters for IP-sensitive environments or teams with data residency requirements.

Q: Does it require a powerful server? A: Each active workspace consumes resources proportional to the work. A modest VPS handles 2-3 concurrent users comfortably. Resource limits are configurable per workspace.

Q: Can I use my own VS Code extensions? A: Dockside’s browser IDE is compatible with the VS Code extension API. Extensions can be installed per-workspace from the IDE’s extension panel.

Q: Is the source code actually open? A: Yes, MIT-licensed and available on GitHub. The site links directly to the repo.

Conclusion

Dockside fills the gap between “use GitHub Codespaces” and “run everything locally.” For teams that want the browser-IDE experience without surrendering control to a third party, it is a credible open-source option. The Docker-based workspace model is the right primitive — what runs in the container matches what runs in production.

If your team is small, security-conscious, or just tired of cloud IDE pricing, Dockside is worth a weekend pilot on a spare VPS.