Optional by design
A workspace can be hosted and powered by integrations without paying for development runtime.
Sandbox pricing
Sandbox runtime is for building, not merely existing.
Some users will never need a sandbox. Others will use one when Studio Nova or an external coding harness needs a development environment.
Core rule
Studios are free. Pay for live workspaces, business add-ons, optional sandbox runtime, and optional Studio Nova AI credits.
Do not force sandbox cost into every workspace.
A commerce site assembled from integrations can run as a workspace without a development sandbox. A custom app under active development can add runtime only when it needs build infrastructure.
For building, testing, and coding
The sandbox is where agents or coding harnesses run commands, build apps, clone repos, and start dev servers.
Separate from workspace hosting
Keeping an app live and running a build environment are different costs, so DLX Studios should bill them separately.
Self-hosted runtime direction
New pricing should treat sandbox as Docker runtime infrastructure, not a third-party-specific product.
No sandbox
Integration-built workspace
Example: a $5 workspace plus $20 commerce add-on for a $25/mo store.
Temporary sandbox
Build or modify code
Example: use runtime only while Studio Nova builds a custom feature or runs tests.
Dedicated sandbox
Ongoing custom development
Example: a Studio with separate sandboxes for separate custom workstreams.
Sandbox pricing remains an open implementation decision.
The pricing plan intentionally defers the exact runtime unit until the self-hosted Docker runtime cost profile is known. The user-facing model should stay simple and separate from workspace hosting.