Frequently Asked Questions

How isolated are Synodes sandboxes?

Each sandbox runs in its own container with dedicated PID, filesystem, and network namespaces. By default, sandboxes can make outbound network requests. You can restrict this with --network-block-all or specify allowed CIDR ranges with --network-allow-list. Sandboxes on the same account are isolated from each other — they cannot see or access each other's processes, files, or network interfaces.

What happens to my data when a sandbox is deleted?

Sandbox filesystems and auto-provisioned Turso databases are permanently destroyed on deletion. If you need persistent data, use volumes (which survive sandbox deletion), snapshots (which capture the full sandbox state), or a manually provisioned Turso database that you manage independently. Snapshot storage is billed at $0.10 per GB-month.

Can I run Synodes on my own infrastructure?

Yes. Synodes is open-source and deployable on your own Kubernetes clusters via the synodes-region Helm chart. Supported providers include AWS, GCP, Azure, DigitalOcean, Fly.io, Hetzner, and Docker (for local development). The hosted platform at app.synodes.io is the managed, zero-ops option.

What's open-source and what's proprietary?

The CLI, SDKs (Go, Python, TypeScript, Java, Ruby), cloud providers, Helm charts, and integrations are all open-source under AGPL-3.0 or Apache-2.0 licenses. The hosted control plane at app.synodes.io includes proprietary multi-tenancy, billing, and usage metering features. See LICENSES.md for the full license table.

What does the AGPL license mean for my usage?

The CLI is licensed under AGPL-3.0, which means if you modify the CLI and make it available as a network service, you must offer the source code to users. The SDKs, providers, and Helm charts are Apache-2.0, which is permissive — you can use them in commercial products with attribution. If you use the hosted platform, AGPL does not apply to you as an end user.

How does billing work? When am I charged?

Synodes uses consumption-based (pay-as-you-go) billing. You're charged $0.05 per container-hour (billed per second) for sandbox runtime and $0.25 per GB-month for Turso database storage. Billing stops when the sandbox is stopped or deleted. Every account includes 5 free container-hours per month. There are no monthly plans, no minimums, and no commitment — you only pay for what you run. See the Pricing page for detailed rates and cost examples.

What base images / languages are supported?

Synodes supports all major languages through Docker-based images: Python, TypeScript/Node.js, Go, Java, Ruby, Rust, and more. You can create custom snapshots with your own toolchain, or build from a Dockerfile. Custom base images let you pre-install packages, configure environments, and bake in API keys (securely via environment variables).

How do Turso databases work with sandboxes?

Each sandbox can be provisioned with its own Turso (libSQL) database. Set TURSO_DATABASE_URL and TURSO_AUTH_TOKEN to {{auto}} and Synodes creates a fresh database on sandbox creation, injects the real credentials, and tears it down on deletion. You can also bring your own Turso database by passing real credentials. See the Turso Databases page for details.

How do I connect my AI agent framework?

Synodes has first-class integrations for LangChain, Google ADK, n8n, OpenCode, and any MCP-compatible client. Use the Python or TypeScript SDK to programmatically create sandboxes, run code, and capture results. For frameworks without a dedicated integration, the SDK gives you complete control over sandbox lifecycle — create, exec, read files, and destroy — all from a few lines of code.

Is there a free tier? Do I need a credit card?

Every account includes 5 free container-hours per month (worth ~$0.25) — no credit card required. You can spin up sandboxes and try the platform without any payment. To go beyond 5 hours, you'll need a payment method on file for the consumption billing. Since you only pay for what you use, there's no subscription lock-in and no minimum spend.