Deploying to Sandbox

Designer can ship the components it generates directly to the public Sandbox. Once deployed, any SDK client can point at the Sandbox and exercise your commands and views.

Caution

The Sandbox is a shared, public environment. Your deployed components and any data they process are visible to all Sandbox users and get purged periodically. See About the Sandbox.

One-click deploy

From the generated project view in Designer, click Deploy to Sandbox. Designer:

1. Builds the WASM components for each State Change and State View in the project.
2. Registers them against a fresh database in your Sandbox namespace.
3. Returns the database name you can point clients at.

Open the Sandbox URL Designer gives you to confirm the deploy and see the initial (empty) state of your views.

CLI deploy

For scripted deploys (CI, demos), use the evidentsource CLI — see CLI reference. The short version:

evidentsource sandbox deploy \
  --project ./my-project \
  --database my-todos

What gets deployed

• Compiled WASM modules for each component
• Component manifests (name, version, subscriptions)
• Schema metadata for introspection

Your generated project’s README has the exact build command.

Iterating

Redeploy at any time. Component versions are tracked per database — rolling forward and back is a metadata change, not a rebuild of the event log.

When you outgrow the Sandbox

When you’re ready for your own EvidentSource — private data, durable storage, real availability — see Operations: containers + S3 and AWS Marketplace deployment.