Customer-Facing Product Experiences
This category is the second-highest priority in the plan because it turns AerolVM into part of the product surface itself. Instead of only helping internal engineering, the sandbox becomes the runtime behind previews, databases, code execution, labs, and per-user environments.
Selected subcategories
Section titled “Selected subcategories”| Use case | Rating | Why it made the cut |
|---|---|---|
| Embedded code runner inside a SaaS product | 10/10 | It is one of the strongest direct product integrations for AerolVM. |
| Deploy your own Postgres | 10/10 | It shows how AerolVM can host a tenant-scoped database runtime while still publishing an HTTP surface for product integration. |
| Create your own Upstash Redis | 10/10 | It shows how to host a per-tenant isolated Redis instance with an HTTP admin surface. |
| Interactive tutorial or lab backend | 9/10 | It maps well to sessions, previews, and short-lived isolated workspaces. |
| AI app hosting | 9/10 | It clones a real website repo, runs the Bun build pipeline, and leaves the app live on a hosted preview URL. |
| Secure burner browser | 9/10 | It makes sandbox speed visible by streaming a disposable Chromium desktop straight into the user's browser. |
| Secure burner VPN proxy | 9/10 | It shows how to expose both an HTTP dashboard and a raw TCP SOCKS5 proxy from one sandbox so browsing egress stays isolated from the local machine. |
| One-click user sandbox per workspace | 9/10 | It is the cleanest multi-tenant runtime pattern for developer and AI products. |
Why AerolVM fits this category
Section titled “Why AerolVM fits this category”createturns a product event into a dedicated runtime in seconds.exposePortmakes app and API previews easy to surface to users.- Sessions support long-running tutorials, labs, and user-owned shells.
runtime: "gvisor"andnetworkBlockAllare useful when end users submit untrusted code.- Lifecycle controls let the platform shut down idle runtimes automatically.
Recommended implementation pattern
Section titled “Recommended implementation pattern”- Create a sandbox per user action, workspace, or generated project.
- Upload starter or generated files into the sandbox.
- Boot the app, shell, or interpreter with
execStreamor sessions. - Expose the necessary preview or API port.
- Stop or destroy the sandbox when the workspace becomes idle.