Get an audit

Head to head · Sandbox code · October 2026 research run

Freestyle vs Together Code Sandbox

Freestyle scores 58.5 (C) on agent readiness against Together Code Sandbox's 53.6 (D), and leads in 3 of 7 scored categories. Together Code Sandbox leads on maintenance & community and transparency & trust. Both do sandbox code.

FreestyleFreestyle Cloud Inc. · HTTP API C58.5/100#520 of 841 Together Code SandboxTogether AI · HTTP API D53.6/100#628 of 841

Which one, for what

Freestyle C

Good for Suited to long-running agent work that needs a full Linux VM, memory-preserving pause, snapshots to branch from and private networking.

Ahead on

  • Reliability, 43 against 25
  • Security & auth, 53 against 47
  • Payments & pricing, 45 against 20

Also in its favour

  • Free to start without a card

Watch for

No terms of service or service agreement found on the site, and the privacy policy covers the website only

Together Code Sandbox D

Good for Teams already buying from Together, and former CodeSandbox SDK users, who want Docker-defined sandboxes with disk and memory snapshots from Python or TypeScript.

Ahead on

  • Maintenance & community, 83 against 71
  • Transparency & trust, 60 against 41

Watch for

The SDK and CLI work only for organisations Together has enabled, and the docs say to contact Together for access

Score by category

CategoryWeight this runFreestyleTogether Code SandboxEdge
Reliability16%204325Freestyle +18
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28686even
Agent ergonomics13%16.26970Together Code Sandbox +1
Security & auth14%17.55347Freestyle +6
Payments & pricing10%12.54520Freestyle +25
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87183Together Code Sandbox +12
Transparency & trust7%8.84160Together Code Sandbox +19
Negative events≤1500
Total58.5 · C53.6 · D

Facts side by side

FactFreestyleTogether Code Sandbox
KindHTTP APIHTTP API
VendorFreestyle Cloud Inc.Together AI
Hosted endpointhttps://api.freestyle.sh/v5https://api.bartender.codesandbox.io
TransportsHTTPHTTP
AuthAPI keyAPI key
PricingFreemiumPay per use
x402nono
LicenceProprietary service with no published terms of service found. The freestyle SDK and CLI package on npm is MITProprietary service under Together's terms of service. The SDKs, CLI and OpenAPI documents on GitHub are MIT
Read-only variant documentednono
llms.txtyesyes
Last release2026-09-272026-10-07
Terms last updatedno document linkedno date given
Privacy policy last updatedno document linkedno date given
Customer content may train modelsnot found in the text
Terms restrict automated accessnot found in the text
Terms restrict benchmarkingyes
Terms or service can change without noticenot found in the text
Arbitration or class-action waivernot found in the text
Popularity72k npm/wk3 stars, 1.3k npm/wk, 3.4k PyPI/wk

Verdicts

Freestyle

A public OpenAPI 3.1 file describes 88 operations with a stable error code on every failure, and per-VM identity tokens keep the team API key away from end users. No terms of service, product privacy policy, request rate limit or incident history was found, and the only SDK is TypeScript.

Together Code Sandbox

Two public OpenAPI documents, MIT clients for Python and TypeScript, cursor pagination and built-in retries make the surface easy for an agent to drive. Access is the limit. Together enables the SDK per organisation on request, publishes no rate limits or SLA, and neither status page names the sandbox service.

Before you call either

Freestyle

  1. Send a firewall object on every POST /v5/vms. It is required, and a VM with no rules has no outbound internet
  2. Ask the owner to run freestyle login in a browser once, then mint a key with freestyle tokens create --output json
  3. Do not retry an exec that answers 409 VM_NON_RESPONSIVE. The command may already have run
  4. Keep exec-await under its 300,000 ms cap and use a PTY session or x-freestyle-background-after-secs for longer work
  5. Call the /v5 paths. The unversioned duplicates in the OpenAPI file are marked deprecated

Together Code Sandbox

  1. Confirm the organisation is on Together's allowlist before installing. A valid TOGETHER_API_KEY alone is not enough
  2. Build a snapshot first with snapshots.create. No default image exists, and every sandbox needs snapshot_id or snapshot_alias
  3. Set ttl at creation or call terminate(). Nothing stops a sandbox otherwise, and closing the Python client leaves it running
  4. Store the snapshot alias, not the sandbox ID. A terminated sandbox can't restart, and its state lives at sandbox:<id>
  5. Exclude snapshots.create from retries with should_retry, and set experimental.network_policy before serving anything private on a port

Questions

Which is better for AI agents, Freestyle or Together Code Sandbox?

Freestyle scores 58.5 (C) on agent readiness against Together Code Sandbox's 53.6 (D), and leads in 3 of 7 scored categories. Together Code Sandbox leads on maintenance & community and transparency & trust.

Do Freestyle and Together Code Sandbox need an API key?

Both need an API key.

Can an agent call Freestyle and Together Code Sandbox without installing anything?

Yes. Freestyle has a hosted endpoint at https://api.freestyle.sh/v5 and Together Code Sandbox at https://api.bartender.codesandbox.io.

Other comparisons with Freestyle or Together Code Sandbox

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report