Demos
Demos represent the live configuration and deployment of your play directly on our infrastructure. We require internal hosting, rather than allowing external links, to guarantee the quality of your work and prove that the code successfully deploys.
How it works
Demos are automatically prepared for deployment on Playbooks using AI-assisted configuration.
Alternatively, you can take full control by supplying a custom playbooks.json file with your preferred setup.
All demos are provisioned within a secure, isolated sandbox using Docker.
Each sandbox is generously allocated 2 vCPUs, 4GB of RAM, and 4GB of disk space. After a successful initial deployment, sandboxes are cached and stored to ensure instant start times for future visitors. All sandboxes operate in a highly scalable, serverless environment that is dynamically load-balanced based on real-time activity.
Configuration
Demos offer flexible configuration options, allowing us to deploy almost any project on our infrastructure within reasonable constraints.
Strategy
To get started, you will need to select from the following deployment strategies based on your project's complexity.
Strategy | Description |
|---|---|
| Basic | Select a base image, port, and server commands to generate a Dockerfile on the fly. |
| Dockerfile | Specify a primary port and supply your own custom Dockerfile. |
| Compose | Define a primary port and provide a docker-compose.yml file. |
| Partial | Choose an existing template to build upon and define the runtime code storage location. |
Environment Variables
Playbooks allows you to inject environment variables to ensure your demo runs correctly.
These variables utilize end-to-end (E2E) encryption and are strictly accessible only by the account owner. They are injected securely at runtime, meaning they never travel with the downloadable source code. This makes them perfect for powering functional demonstrations that require private API keys.
Key | Value |
|---|---|
PORT | •••••••••••••••••••••••••••••••• |
NODE_ENV | •••••••••••••••••••••••••••••••• |
DATABASE_URL | •••••••••••••••••••••••••••••••• |
Private Files
Similar to environment variables, Playbooks allows you to upload private files necessary for your demo to function. These private files also use E2E encryption and remain entirely restricted to the account owner. They are mounted exclusively at runtime and are stripped from the code before distribution. This feature is ideal for functional demonstrations that rely on private configuration files or certificates.
Path | Value |
|---|---|
/.env | •••••••••••••••••••••••••••••••• |
/.npmrc | •••••••••••••••••••••••••••••••• |
Debugging
All demos come equipped with built-in observability tools to help you debug and monitor the performance of your sandbox. For each tool, you can filter the view down to a specific service or observe the sandbox as a whole.
Tool | Capability | Implementation |
|---|---|---|
| Logging | Observe real-time output and activity streams for your entire sandbox or individual services. | Streaming Logs |
| Shell | Perform interactive debugging sessions directly within your browser. | Server-Sent Events (SSE) |
| Stats | Monitor the CPU, memory, and network performance of your sandbox and services. | Real-time Metrics |