Creating Sandboxes

Set up sandbox environments, connect to your product infrastructure, and configure sample data.

Sandboxes require a connection to your product's environment provisioning system. This page covers setup and configuration.

Connecting your product

Demoship needs a way to create isolated instances of your product. There are two approaches:

API integration

1. Go to Settings > Sandbox > Environment.
2. Provide your provisioning API endpoint. Demoship calls this endpoint to create and destroy instances.
3. Configure authentication (API key or OAuth).
4. Test the connection by creating a test instance.

Your API should support:

• POST /provision -- Create a new instance. Returns a URL.
• DELETE /provision/:id -- Tear down an instance.
• GET /provision/:id/status -- Check instance health.

Container-based

If your product runs in containers, Demoship can manage provisioning directly:

1. Provide a Docker image or Kubernetes configuration.
2. Configure resource limits (CPU, memory, storage).
3. Set environment variables for the sandbox instance.
4. Demoship handles orchestration, scaling, and cleanup.

Sample data configuration

Each sandbox needs realistic data so prospects have something to explore.

1. Go to Sandbox Settings > Sample Data.
2. Upload a database seed file, or connect to a snapshot of your staging database.
3. Configure data masking rules to remove any real customer information.
4. Test the data by provisioning a sandbox and verifying the experience.

Instance settings

• Expiration -- Set how long a sandbox stays active (e.g., 7 days, 14 days, or until manually deactivated).
• Concurrent limit -- Maximum number of active sandboxes per workspace.
• Access control -- Require email verification, or allow anonymous access.
• Reset behavior -- Allow prospects to reset their sandbox to the original data state.

Note: Pre-warmed pools reduce provisioning time from minutes to seconds. Under Settings > Sandbox > Performance, configure the number of idle instances to keep ready.