Portal turns live websites, localhost projects, Chrome extensions, and local files into shareable, isolated product environments. Sales, developer relations, and product teams can let people explore a real product or follow an AI-guided demo without requiring installation or signup.
Portal is a shareable product-environment platform for turning a live browser state into a link. A recipient opens the link in an isolated cloud browser session and can try the real interface rather than watching a video or using a static mockup. Portal supports websites, localhost projects, Chrome extensions, local files, HTML, videos, and public GitHub repositories, according to the site’s product and documentation pages.
A Portal can preserve a signed-in starting point, define the pages, buttons, prompts, API methods, or endpoints that visitors cannot access, and apply controls such as API stubs and rate limits. Each visitor can receive a fresh copy of the environment, while persistent workspaces are available for teams that need shared, logged-in sessions for short tasks. Developers can deploy from a coding agent with the Portal CLI or MCP, while GTM teams can use the conversational web builder without code.
Visitors can use Play Mode to explore within the defined guardrails or Watch Mode to follow an AI-led walkthrough. The AI agent can be grounded in product documentation, answer questions, narrate a demo, and highlight interface elements. Portal also records session activity, including pages opened, time spent, stalled points, and requests for help, providing click-level and session analytics for product research, onboarding, and sales follow-up.
Portal is offered with a free plan and paid tiers. The pricing page lists a free plan with one Portal, three active drafts, and 10 opens across Play or Watch; Builder is listed at $20 per month with two Portals, three active drafts, 50 monthly opens, persistent logins, and a multi-tab sandbox. Higher tiers add capabilities such as persistent portals, simulations, resets and seeding, dynamic links, CRM integration, custom usage, analytics, webhooks, and support, with availability varying by plan.
Turn a website, localhost project, Chrome extension, local file, HTML project, video, or public GitHub repository into a link that opens in an isolated browser session. Recipients can try the real product without installing it or creating an account.
Configure the environment’s initial URL, saved login, or uploaded file so visitors land in a prepared product state. Custom pre-seeding and reset scripts can populate an environment before use and clean it up afterward.
Block URLs, buttons, prompts, API methods, or endpoints to limit what visitors can reach. Portal also supports API stubs, allowlisted endpoints, rate limits, and reset hooks for controlled demonstrations.
Play Mode lets visitors explore within the configured limits. Watch Mode puts an AI agent in control of the browser for a guided walkthrough, with the visitor able to ask questions.
An AI agent can use uploaded product documentation to answer questions, narrate demos, teach users, and highlight interface elements. Session data shows opened pages, time spent, stalls, and help requests, including click-level interaction activity.
Sales and solutions teams can send prospects a working, provisioned environment instead of arranging an initial call or sharing a video. A prepared demo account and defined guardrails let prospects evaluate the product asynchronously.
Teams can send new users directly into a configured application state and optionally use an AI guide to explain features or answer questions while the user explores.
Product teams can review where participants navigate, hesitate, stall, or request help. The session record provides behavioral evidence beyond whether someone watched a demo.
Developers and DevRel teams can share localhost projects, GitHub repositories, or Chrome extensions as links. Workshop participants can open the same type of environment without local setup or an extension installation.
The recipient opens the shared link in a browser. The site says Portal sessions require no installation, setup, signup, or password for the visitor; the session is isolated and can use a prepared login.
A Portal provides access to a real, running product interface that the recipient can explore. It is not a video, mockup, onboarding overlay, or static walkthrough, although Watch Mode can provide an AI-led guided experience.
Yes. Portal supports guardrails for blocking URLs, buttons, prompts, API methods, and endpoints. Documentation also describes API stubs, rate limits, and allowlists for limiting potentially destructive or unwanted actions.
Developers can deploy a project through the Portal CLI or MCP from a coding agent. The documentation gives `npx makeportals deploy` as the one-line deployment command and says the project is packaged, uploaded to a cloud VM, dependencies are installed, and a shareable link is returned. GTM teams can instead use the no-code conversational web builder.
Yes. The pricing page lists a free plan with one Portal, three active drafts, and 10 opens across Play or Watch. It also lists paid plans, including Builder at $20 per month, with limits and capabilities varying by tier.
Traffic data is for reference only.
