Frictionless portal for sharing internal AI-built tools
Problem
Developers vibe-coding internal tools hit a wall after deployment: coworkers must be manually told to visit obscure URLs and log in each time, so adoption of useful internal micro-tools is an endless chore and many tools die unused.
Opportunity
An internal 'tool store' that one-click deploys AI-built apps behind company SSO, lists them in a searchable catalog with notifications — solving distribution and access for the flood of AI-generated internal tools.
Market analysis
The pain is real and growing with the vibe-coding wave, but the space is surrounded: Backstage is the dominant open-source internal portal, Intune Company Portal handles private app distribution on corporate devices, and every vibe-deploy platform (VibeNest, ChatAndBuild) already bundles one-click deploy with hosting. What is genuinely missing is a lightweight 'app store for vibe-coded micro-tools' layer — SSO in front, catalog behind — for teams too small for Backstage.
Market · Small-to-mid engineering and ops teams adopting AI coding tools; strong macro demand signal (Gartner-cited projection that most engineering orgs will run an internal developer portal by 2027), but the specific micro-tool-catalog niche is unproven.
Pricing · Comparables: Backstage is free but operationally expensive; Retool monetizes internal tools at roughly $8-10/end-user/month with SSO gated to higher tiers. A per-seat SaaS portal (e.g. $2-5/user/month) is the plausible wedge.
Pros
- + Timing is right: the flood of AI-generated internal tools is brand new and unaddressed by incumbents.
- + Thin layer over existing hosting — an MVP can wrap auth proxying plus a directory rather than re-platforming.
- + Clear wedge into companies that find Backstage too heavy.
Cons
- − Backstage, though heavy, is free and dominant; platform teams default to it.
- − Vibe-deploy platforms are incentivized to ship catalogs natively — constant feature-absorption risk.
- − Selling 'internal tool distribution' to IT touches security review, SSO integration and procurement — slow for a solo builder.
- − Many teams solve this today with a pinned Slack message or a Notion page.
Existing / similar tools
Source
Hacker News (Ask HN)
The hard part is not the catalog — it is the identity boundary. Wrapping arbitrary vibe-coded apps behind company SSO means an auth proxy that understands every app’s login flow, plus enough access control to satisfy IT, which is exactly the muscle solo builders lack. Backstage loses on weight but wins on trust: platform teams that already run it will not adopt a second portal, so the real audience is the 10-200 person company with no platform team at all. That company also has no budget owner for “tool distribution”, so pricing has to be self-serve and cheap, more utility than enterprise. The durable moat, if any, is being the default deploy target that AI coding tools mention in their own docs — a distribution race against Vercel- and Netlify-shaped incumbents.