Send the project
Inspect its runtime, choose a provider and capture a project snapshot. Exclusions keep configured private and generated files out of the upload.
COMPUTE THAT FOLLOWS YOUR WORK
More compute.
Same workflow.
Give your project a box. Run its build, tests or a coding worker on local and cloud compute. Bring the results back to the harness you already use.
CLI · stdio MCP · local execution monitor · hosted platform in progress
YOUR PROJECT. ITS OWN COMPUTE.
BOXFLEETProject snapshotSource + requested command
Results, returnedArtifacts + hashes + execution
LOCAL / CLOUDCHOOSE YOUR PROVIDER
KEEP YOUR EDITORSELECT THE COMPUTEINSPECT THE RESULT
01 / THE ROUND TRIP
Your box is an extension
of your workspace.
Reason and edit on your workstation. Move the work that needs a separate environment, CPU or memory into a box.
Run the work
Execute a command, run project tests, build an artifact, or delegate a task to our guest coding worker with host model relay.
Bring it back
Retrieve requested files and patches. Read exit codes, command output, bounded model exchanges and a hash-linked execution journal.
02 / PICK YOUR ENTRY POINT
One system.
Several ways in.
Authorized operator installations can use the same job contract from a coding client, terminal or local application. These are examples, not a live session or a public installer.
boxfleet run --project /absolute/project \ --provider e2b --action build --install --artifact dist
The returned job ID links status, logs and retrieved output. Match the artifact path to your project.
03 / KNOW WHAT HAPPENED
A result you can
inspect.
Find jobs by box or caller task ID. Inspect the request, requested model and effort, observed provider details, operation timings, outputs and cleanup.
Missing measurements stay unknown. Captures are bounded and redacted. Hashes help detect changed files; they are not signed execution attestation.
Explore the execution record ↗jackai-box.execution/v1 CONTRACT
- Identity
- job ID · box ID · caller context
- Request
- project · command · model · effort
- Execution
- timestamps · durations · exit codes
- Usage
- reported counters · explicit unknowns
- Outputs
- artifacts · patch · source · SHA-256
- Lifecycle
- cleanup result · recorded errors
MCP / CLI / HTTP RETURN THE SAME CONTRACT
04 / CHOOSE THE ENVIRONMENT
Real integrations.
Clear boundaries.
Available source, an implemented adapter and a live-qualified workflow are different things. Check installed capabilities for the current details.
Firecracker · E2BLIVE-TESTED PATHS
Local VM and cloud execution paths have live proofs. Local Firecracker needs Linux KVM or configured WSL2 assets and a suitable guest image.
Runpod · Daytona · Instabox · SSHOFFLINE / CONDITIONAL
Runpod allocation and SSH execution have offline contract tests, but no live GPU proof. Daytona and Instabox need authorized account qualification. Generic SSH connects to an existing trusted Linux host; it does not provision a cloud fleet.
AWS · Azure · other cloudsNATIVE ADAPTERS PLANNED
Native AWS, Azure and Google Cloud provisioning and Cloudflare Sandbox integration are planned. An OpenAI-compatible model endpoint connects only to an already running model service.
For continuous systems
The current controller supports four active jobs per process and bounded local history. It does not provide a distributed scheduler, tenant isolation or automatic agent recovery after a controller restart. Account lifetime budgeting and cross-box continuation remain planned.
05 / ACCESS
One account.
Every box.
BoxFleet's hosted customer platform is in development. Public sign-up, hosted jobs and team billing are not available on this website yet.
The planned customer flow uses one JackAISaaS account for sign-in, organization membership and subscription rights. BoxFleet will use those rights to authorize jobs while keeping execution history and artifacts in its own service.
The local CLI and monitor already serve authorized operators. Provider credentials stay under their control; this public website does not ask for keys or connect to a box.
Explore the workflow ↗BOXFLEET ACCESS CURRENT STATUS
- Website
- Available at boxfleet.io
- Local tools
- CLI, MCP and monitor for authorized operators
- Accounts
- JackAISaaS connection in progress
- Cloud API
- Hosted execution not yet available
NO PUBLIC SIGN-UP OR PAYMENT ON THIS SITE
FIND YOUR WORK AGAIN
Every launch gives you a job ID.
The local monitor links each job to its box, request, live output, retrieved artifacts and cleanup result. A versioned execution record preserves timings, hashes and the outcome after the box ends. Hosted team history will arrive with the customer platform.