PREPARE BEFORE THE SANDBOX

Start with your work.
Not the setup.

Basecamp prepares the runtimes, dependencies and tools your project needs. Your code stays yours. Your environment arrives ready.

One project. One sandbox. That’s enough.
01 / YOUR PROJECT

You have something to build.

Start with the project and tools you already use. No new build system. No platform-selection step.

your-project / Project files Docker example target
SOURCE your-project ENVIRONMENT To be preparedSame project. Same destination.
Your next change PROJECT, NOT SETUP
THE WORK YOU CAME HERE TO DO

A feature. An analysis.
Your next idea.

Keep your code, your project structure and your native tools. Leave the environment preparation to Basecamp.

Node.js Python Rust JavaAnd beyond
Examples of the environment model, not a claim that every adapter is released.
Preparation host CONNECTED · BEFORE THE TASK
$basecamp sync
01readNative manifests, locks and target
02resolveMatch the environment to this project
03prepareReuse, fetch and materialize resources
04verifyCheck completeness and compatibility

Preparation happens here. Not in your task sandbox.

YOUR SOURCE

Your code.
Your files.

your-project/├─ source & tests├─ native manifests & locks└─ declared project inputs
SOURCE · project-01Unchanged
BASECAMP

Ready
environment.

ENV · prepared-01
Runtimes · Dependencies
Tools · Declared resourcesMATERIALIZED FOR THE TARGET
Verified resourcesReady to activate

Ready to use. Not a pile of installers.

PREPARATION COMPLETE
Your sourceCheckout or deliver independently
Prepared environmentMaterialized and target-compatible

Two independent assets.
One place to do your work.

YOUR CHOSEN SANDBOX

Docker

Source Received

Environment Attached

Receive the files.
Activate the prepared environment.

No package-manager installation in this illustrated task path.
SETUP IS OUT OF YOUR WAY

You’re ready.
Get to work.

Run your usual build, test or analysis. The sandbox provides execution. Your application or agent produces the result.

Activating environment
your-project WORKSPACE

○ Your source is here

○ Your environment is here

○ Activated in the workload process

NOW, YOUR NORMAL TOOLSBuild. Test. Analyze.

No installation checklist between you and the task.

Source remains independent from the environment.Workflow illustration · not live execution

ONE PROJECT. ONE SANDBOX. THAT’S ENOUGH.

The install checklist
ends before the task begins.

01 / BEFORE THE TASK

Basecamp prepares.

Resolve the project. Fetch what is missing. Materialize and verify the environment.

Resolve → Prepare → Verify
02 / INSIDE YOUR SANDBOX

You get to work.

Receive the source and environment. Activate in the task process. Use your normal commands.

Receive → Activate → Work

For declared, fully prepared resources on a compatible target. Business network access is a separate policy. Understand the preparation boundary

YOUR PROJECT. YOUR EXISTING TOOLS.

More than a language.
The things your work needs.

Single project, multiple projects or monorepo. The preparation model covers runtimes, native dependencies, system tools and declared AI resources.

Languages & runtimes

32
JavaScriptTypeScriptNode.jsDenoBun runtimePythonRustGoJavaKotlinScalaCC++C#F#RubyPHPSwiftObjective-CDartRJuliaElixirErlangHaskellOCamlLuaPerlZigFortranBashPowerShell

Native package managers

32
npmpnpmYarnBunpipuvPoetryPipenvCondaMambaCargoGo modulesMavenGradlesbtNuGetComposerBundlerRubyGemsConanvcpkgSwiftPMCocoaPodspubrenvJulia PkgHexCabalStackopamLuaRocksCPAN

System tools & SDKs

21
aptdnfyumapkpacmanzypperHomebrewNixGuixSpackScoopwingetChocolateyGCCClangCMakeNinjaCUDA librariesROCm librariesAndroid SDKWASI SDK

Agent tools & resources

15
Playwright browsersChromiumFirefoxMCP serversGitffmpegripgrepjqModel weightsTokenizersModel adaptersDatasetsEvaluation fixturesSearch indexesVector indexes

Environment scope, not a checklist of released adapters. Rust / Cargo is the recorded implementation; availability must be checked for each combination. See what is verified

ONE SANDBOX IS ENOUGH. CHOICE STAYS OPEN.

Your chosen workspace.
Not another platform to learn.

Keep the sandbox you already use. Explore the delivery surfaces below without changing the project in the story. Each route has its own capabilities and limits.

Docker

Project and prepared store are mounted from the Docker daemon host. The workload entrypoint activates the environment.

Separate Rust + Docker fixture exists.

Provider documentation
HOW THE TWO PARTS ARRIVE
Your sourceReady environment
Docker

Same-host mount

Names identify ecosystem references, not partnerships or certified integrations. A setup hook that installs inside the target does not, by itself, satisfy the prepare-first workflow.

RECORDED EXECUTION, NOT A MOCKUP

A real project.
An offline sandbox.

Watch the recorded Rust + Docker example. A separate preparation container prepares the environment; the task container runs with networking disabled.

Watch the real session Linux arm64 · supplied preparation prerequisites · cached official distribution. The recording proves this configuration, not every illustrated combination.
Actual terminal recording 28.93s
Docker container started. Network: none.

Hello from the offline sandbox. Answer: 42

test result: ok. 2 passed; 0 failed
Play the recorded session
NEXT · OPTIONAL

Your runs, in one view.

Later, coordinate execution across destinations without losing the project’s history or results. Not required for preparation.

Explore the next chapter
LESS SETUP. MORE OF YOUR WORK.

Bring your project.
We’ll prepare the environment.

Get started with Basecamp