Product Hunt Launch Deck

Deck Metadata

Slide 1: Prox OS

An AI-native Web OS for solo founders, community apps, personal data, and future agent workflows.

Speaker note: Position Prox OS as an operating layer, not another generated app tool or static dashboard.

Slide 2: The Problem

AI can generate more software than a solo founder can safely organize.

• Ideas live in chats.
• Specs drift across docs, issues, and code.
• Apps, sources, permissions, launches, and decisions are scattered.
• AI work becomes hard to review when context is private or implicit.

Speaker note: The bottleneck is not only code generation. The bottleneck is operating memory.

Slide 3: The Product Wedge

Prox OS turns product context into an operating surface.

• Docs as team memory.
• Apps as OS surfaces.
• Roadmap and governance objects visible in the shell.
• Storybook, app registry, and design tokens as implementation truth.
• Future agents with scoped inputs, outputs, and review paths.

Speaker note: Keep the claim grounded in what exists or is documented. Do not promise autonomous agent execution.

Slide 4: What Exists Today

• Browser OS shell with registry-driven apps.
• Internal Docs and Docs app.
• Governance, Join Us, Roadmap, Pricing, and platform prototype apps.
• App contract and Proxied App direction.
• Storybook / UI Workshop for component truth.
• AI Control Plane docs, role maps, and task workflow templates.

Speaker note: Be explicit that several platform objects are prototypes or planning docs.

Slide 5: Why Now

Software 3.0 makes natural language a serious interface, but text without governance creates product debt.

Prox OS explores a middle path:

prompt
-> docs
-> task graph
-> app / UI / story
-> review
-> release note
-> roadmap status

Speaker note: This is the "prompt-driven design system" story.

Slide 6: Who It Is For

• AI-native solo founders.
• Micro-teams building product systems.
• Developers who want app surfaces around their workflows.
• Communities that may eventually publish OS Spaces.
• Contributors who work through docs, scoped prompts, and reviewable artifacts.

Speaker note: Avoid making it sound enterprise-ready today.

Slide 7: What Makes It Different

Speaker note: Do not frame this as direct replacement. Frame it as a layer.

Slide 8: Launch Ask

Try the preview, read the internal docs, and tell us which operating object should become real first:

• Join Us role map.
• Governance Console.
• Roadmap.
• Pricing / Founder Preview.
• App registry and Proxied Apps.
• Storybook-backed UI patterns.

Speaker note: The CTA is feedback and early contributor alignment, not payment.

Slide 9: Not Yet

Not implemented yet:

• Live billing.
• Public marketplace.
• OAuth production auth.
• Autonomous agent runtime.
• MCP gateway.
• Enterprise compliance.

Speaker note: Honesty is part of the launch posture.

Slide 10: Closing Line

Prox OS is a text-first, system-first, AI-native, craft-aware operating system for people building with AI.

Speaker note: This should match the Join Us app and Design Operating System language.