What works, what’s next, and what isn’t coming.

Only what’s under Available and Beta is described as working anywhere on this site. Nothing here has a date.

Updated 31 October 2026

Available7

Covered by automated tests on two independent apps, one also walked through in a browser.

Works and has tests. Its limits are written in the docs.

Install with your coding agentOne prompt, /llms.txt and /llms-full.txt. No outside founder has tried it yet.
Effect scannerMatches known packages and literal URLs. It can miss wrappers and variable URLs.
Isolation probeEnters your demo as two visitors and reads only. Reaches records linked from pages, and uses two demo starts.
Usage budgetsAtomic reservations per visitor. Overruns are recorded after the fact; only wrapped calls count.

Likely next steps. Each one waits for a team using Trylane to ask for it.

MCP serverCheck and run your demos from an AI agent, with your confirmation.
Visitor budget displayRemaining allowance, shown in the in-demo checklist.
Pre-seeded workspacesA small warm pool, so visitors start instantly.
Supabase adapterFor apps built with AI app builders.
AI-assisted sample dataA first recipe drafted from your schema.
Demo-to-revenue attributionLinking kept workspaces and signups to paid accounts.
One-click demo deploymentsTemplates for standing up a demo copy of your app.
Shared demo workspacesInviting a teammate into the same demo.

Things we've decided against, so you don't have to wait for them.

AI presenters and chatbotsNo avatars or bots talking over your product.
Click-through tour editorsTour tools already do this well.
Autonomous publishingA coding agent can prepare a demo. A person always presses Publish.
Arbitrary code sandboxesTrylane runs your app, not code visitors bring.
A universal framework layerTypeScript on PostgreSQL, done properly, comes first.
Silent visitor enrichmentWe won't look up who your visitors are behind their backs.

Need something on this list, or something that isn’t? Your request decides the order.

Loading…