DataConnector-Pro

A DataConnector-Pro project

SamDevBox

A whole development environment your teammate opens in a browser tab. Terminal, editor, and an AI agent that can actually see the page it just changed — running on a machine only your network can reach.

Why it exists

Setting up a development environment is still a two-day job

Bringing someone onto a codebase means the right language version, the right package manager, a database, credentials, and a page of setup steps that were accurate six months ago. Half a day if it goes well. Two days if it does not — and it is their machine, so you cannot see what went wrong.

SamDevBox makes that environment a thing you create rather than a thing you explain. One command builds it, and what you hand over is a link.

What is in the box

Everything the work needs, and nothing that leaks

A real terminal, not a web IDE toy

A full shell with your repo cloned, dependencies installed, and your toolchain on PATH. Close the tab and nothing stops — reopen the link and the session is exactly where you left it.

VS Code in the browser

The editor you already know, on the same box, behind the same password. Your theme, your keybindings, your extensions — seeded on first boot.

An agent that can see its own work

Claude Code is preinstalled next to a headless Chromium, so the agent can open the page it just changed, take a screenshot, and check it — instead of describing what it believes it did.

Nothing exposed to the internet

The box publishes no ports. It joins your private network and is reachable only by devices you have invited — with the terminal behind its own password on top.

Onboard someone in minutes

Give a contractor a working environment without handing over your laptop, your keys, or two days of setup instructions. Revoke it by deleting one box.

Disposable on purpose

Broken environment? Delete it and make another. Every box is built from one image and one config file, so the tenth is identical to the first.

How it works

Three steps, and the third one is sending a link

01

Drop it into your repo

One folder and one command. It reads your git remote to work out what to build, so most repos need no configuration at all.

02

Create a box

It builds, joins your private network, clones the repo, installs dependencies, and hands you a URL.

03

Send the link

They open it in any browser, on any machine, and start working. No install, no VPN client to configure, no access to anything else you own.

Licensing

Free for individuals and small teams

Use it on your own projects, and inside a small company, at no cost. Past that size a commercial licence is required — and it buys something concrete.

A working box is a moving target. The image pins a browser, an editor server, a terminal bridge, a language runtime and half a dozen other tools, and every one of them ships breaking changes on its own schedule. A licence pays for the maintained build: the one that still works after the next Chromium bump, on both Intel and ARM.

Not sure which side of the line you are on? Tell us your team size below and we will answer plainly — including if the answer is that you owe us nothing.

Commercial licence

Tell us about your team

Two lines is enough: how many people, and what you would use it for. We will tell you whether you need a licence and what it costs — and if you do not need one, we will tell you that instead.

Free for individuals and small teams — ask before you assume you owe anything.
One annual licence per company. No per-seat counting, no usage metering, no phone-home.

By submitting this form, you agree to our Terms of Service and Privacy Policy.

Built and used daily by DataConnector-Pro.