Always on. Like Glitch, inside your IDE.

Turn on persistent mode and the workspace's container stays warm. Run a real web app, a tiny API, or a Discord bot. The URL stays live as long as the workspace exists.

Workspace settings dialog open on the Preview tab. Custom subdomain set to ruicosta, default port 3000, Persistent preview toggle on, startup command running a static file server.

Use cases

When this feature earns its keep.

Three concrete patterns. Use them as templates for your own setup.

Share a demo without asking anyone to install Node

Send a customer the preview URL. They open it in a browser. No install, no "npm install", no waiting for a cold start. The container is already warm.

Run a Slack bot that stays online between sessions

Start the bot process, enable persistent mode, and walk away. It keeps handling events without you leaving a terminal session open or paying for a VPS.

Host a portfolio site on a free Typelets workspace

Spin up a static site or a small Express app, point the persistent preview at it, and share the subdomain link. Free during beta, no infrastructure to manage.

Setup

How the setup looks.

Persistent preview is a single toggle in workspace settings. The container boots immediately and the URL is live within seconds.

Same workspace, same auth, same collaboration features as every other Typelets workspace. See all features

  1. Open Workspace settings, switch to the Preview tab

    Click the gear icon in the workspace toolbar or open the Settings dialog from the workspace menu.

  2. Turn on Persistent preview

    The toggle switches the container from idle (spun down after 15 minutes) to persistent (stays warm indefinitely while the workspace exists).

  3. Set a startup command (optional)

    If your app needs to start automatically when the container boots, add a startup command (for example: npm install && npm run dev). Leave it empty if you want to start processes manually from the shared terminal.

  4. Hit Save. The container boots and stays warm.

    The preview URL appears in the Preview tab. Share it directly or pair it with a custom subdomain so the link is short and memorable.

FAQ

Does the container actually stay warm forever?
For as long as the workspace exists and persistent mode is on, yes. The container is not spun down on inactivity the way a standard workspace is. If you delete the workspace or toggle persistent mode off, the container stops.
What happens if the container crashes?
The orchestrator detects the crash and restarts the container automatically. If you provided a startup command, it runs again on restart. The URL stays the same throughout.
Are there caps on CPU and memory?
Yes. Persistent preview workspaces share the same per-workspace CPU and memory caps as standard workspaces. The container stays warm but it still runs inside a Firecracker microVM with hard resource limits. Exact numbers are listed in the workspace settings dialog.
Can I run a database alongside my app?
You can run SQLite or an in-process store without any extra setup. Running a separate database server process (Postgres, MySQL) inside the same container is possible but the database data lives on a tmpfs volume and does not persist across container restarts. For data that must survive restarts, use an external database and connect to it from your app.

Start interviewing in under a minute.

No card, no install, no yaml. Sign up, create a workspace, share the link. That's it.

Free during beta · No credit card · Cancel anytime