Showrunner

The description states that Showrunner:

• Turns a product release into a “bounded, rehearsed, stage-ready story.”
• Connects a public GitHub repository and HTTPS deployment.
• Resolves the default branch and exact commit.
• Performs a server-side deployment handshake.
• Stores workspace, project, and release under Supabase Row Level Security (RLS).
• Runs a fixed, authorized Atlas product scenario in an isolated Chromium context.
• Detects semantic control changes (e.g., renamed buttons).
• Uses GPT-5.6 to select recovery candidates from a set of safe options.
• Replays the full story in another clean browser context.
• Produces a readiness receipt and stage-ready presenter controls.

Inference The tool appears to be a demo rehearsal and recovery system for product releases, intended to prevent “demo failure” due to release drift. It is not a general-purpose CI/CD or testing tool but rather a specialized solution for pre-demo validation.

The description states that Showrunner treats a demo like a “release artifact,” aiming to map, rehearse, verify, and carry a recovery route onto the stage.

It positions itself as a tool that:

• Prevents demo failures due to release drift.
• Provides a “verified proof” of readiness.
• Offers “stage-ready presenter controls.”

Inference The positioning is focused on product demos in a pre-release context. It does not claim to be a general-purpose testing or CI/CD platform, but rather a tool for ensuring demo stability.

The description states that Showrunner:

• Supports public GitHub repositories and HTTPS deployments.
• Allows approved users to connect repositories.
• Uses invite-only access and token-free onboarding.
• Is built for teams presenting product releases.

Inference The target customer appears to be internal or external product teams, developers, or product managers who present product releases. The ICP is likely small to mid-sized teams with public-facing products that require demo stability.

The description does not state:

• Any pricing model.
• Revenue streams.
• Monetization strategy.
• Customer acquisition approach.

Not evidenced

The description states that Showrunner uses:

• React, Vite, TypeScript for frontend.
• Node.js service on Google Cloud Run.
• Playwright for browser execution.
• Supabase Auth and RLS for access control.
• GitHub REST API for repository resolution.
• GPT-5.6 for structured outputs (not arbitrary browser control).
• Zod for canonical JSON contracts.
• Vercel for frontend hosting.

Inference The system is built with a clear separation of concerns: deterministic execution and evidence control, with AI used only in bounded planning or selection tasks. It uses modern tools and cloud infrastructure.

The description states:

• Built in one week by one team member (YIP Labs).
• 118 automated tests.
• Invite-only access.
• Public-repository import and Atlas rehearsal are separate in this build.
• No mention of customers, users, or revenue.

Not evidenced

The description does not state:

• Direct competitors.
• Market size or positioning.
• How it compares to existing tools for demo rehearsal or release validation.

Not evidenced

• The project is a hackathon submission with no evidence of traction, revenue, or users.
• GPT-5.6 is used only in structured outputs — this is a positive signal for safety but does not indicate adoption or commercial viability.
• No mention of scalability, performance, or long-term maintenance plans.
• The tool is limited to public repositories and invite-only access, which may restrict market reach.

Inference The project lacks evidence of commercial traction or product-market fit beyond the hackathon. It is a proof-of-concept with no known users or monetization strategy.

1. What is the current usage or adoption rate outside of this hackathon build?
2. How does Showrunner plan to scale beyond invite-only access and public repositories?
3. Are there any plans for private GitHub App integration or authenticated target applications?
4. What are the long-term monetization strategies?
5. How does the tool handle edge cases in browser execution or recovery?