free for individuals.
powerful for teams.

No. Studio, the free tier, gives you the full local demo experience — the proxy engine, click-to-edit rule builder, JSON mutations, HTML transforms, and unlimited local rulesets. Solo adds hosted AI, cloud sync, and a live viewer session. AI SE puts the AI Sales Engineer on duty for your prospects. Start free and upgrade when you need it.

AI SE is built for a team: pooled AI credits, pooled live-session hours, shared rulesets, and one knowledge base that every seat draws on. 3 seats is the floor; add seats any time from your billing dashboard.

Hosted AI on Solo and AI SE runs on Anthropic's Claude — no API key needed, usage draws from your monthly AI credits. Prefer your own key? Every tier supports BYOK with Anthropic, OpenAI, or Google Gemini, and your key runs locally in the app.

One balance that powers every AI feature — assistant answers, walkthrough generation, demo scaffolding, the AI design kit, AI rule generation, and mining your support channels into the knowledge base. Your plan grants credits every month, and you can top up any time from your billing dashboard.

Time a live viewer session spends running on a MyAISE GPU runtime, from the moment it goes live until it ends. Solo includes 10 hours a month; AI SE includes 20 hours per seat, pooled across the team. Past the allowance, sessions keep running and draw 50 credits per hour from your AI credits, prorated to the minute.

Nothing breaks. Your demos keep playing — they don't spend credits to run. AI features pause until your next monthly grant, or top up instantly from the billing dashboard to keep going.

Monthly grants reset at each billing cycle. Top-up credits never expire — they stay on your balance until you spend them.

When you turn on self-healing for a demo, MyAISE captures a rich baseline for every targeted element — selector candidates, role, accessible name, position, and a per-step full-page screenshot. MyAISE validates the demo's anchors in the background at viewer-session boot (the viewer never waits on it) and on the drift-check schedule you set (or on demand), detects elements that have drifted (moved, renamed, restyled), and asks Claude to re-find them using the stored baseline plus structural descriptors of the live page's candidate elements. Fixes that verify against the live page and clear your workspace's auto-apply threshold apply as a new demo version when auto-healing is enabled; everything else — including any check on a demo that uses pre-demo or entry actions, which background checks can't execute — lands as a reviewable finding. You get an email summary when a check adjusts or flags your demo. Available on the AI SE plan.

No. MyAISE demos are built to run on data faked by your ruleset's proxy rules, and background validation applies those same rules in its own proxy session, so the pages it checks reflect the faked values your rules cover. When an anchor needs healing, Claude receives the stored baseline and bounded structural descriptors (tags, roles, labels, short text snippets) from that rule-transformed page; the viewer-session path can also include the stored baseline and current screenshots. Neither path sends raw DOM. Cover any values you don't want captured with a rule. You can also purge all healing assets for any demo at any time from the demo settings panel.

MyAISE works with most ordinary browser-based HTTP(S) web apps. Services that enforce certificate pinning are deliberately bypassed and cannot be intercepted. Non-HTTP protocols, device-bound or app-specific SSO flows, and responses served entirely from an existing service-worker or offline cache can require product-specific setup or may not be editable.

Yes. The proxy engine and desktop app are published on GitHub as source-available software under a commercial license — you can read and audit every line that runs on your machine. It is not an open-source license: redistribution and hosting it as a service need a commercial agreement. The cloud backend (sync, teams, billing) is the paid component.

Yes. Cancel from your billing portal and your subscription ends at the next billing cycle. Your local rulesets are always yours — they live on your machine and don't disappear if you downgrade.