Hub App Model

Status

This is platform doctrine for productized Hub lines and marketplace semantics. The shell now has a registry-driven /app-hub/* route group for built-in Hub surfaces. This does not implement subscriptions, backend registry, revenue split, owner-scoped Store listings, or creator canonical URLs.

Hub Definition

A Hub is a runnable, installable, subscribable product workspace or bundle that can contain apps, internal modules, workflows, data surfaces, and future revenue split logic.

A Hub is not a normal Folder and not a simple App list. It has product logic: shared context, workflow shape, included modules, packaging boundaries, governance, and future commercial semantics.

Built-in Hub Runtime Routes

The first-party Hub routes are shell runtime routes. They stay separate from creator canonical URLs and owner-scoped Store listing URLs.

Runtime route	Hub	Goal
`/app-hub/founder-suite`	Founder Suite Hub	OS-native cockpit for AI-native founders and micro-startup teams.
`/app-hub/product-studio`	Product Studio Hub	Product production line from idea to brief, waitlist, launch, experiment, and analytics.
`/app-hub/developer-platform`	Developer Platform Hub	App contract, manifest, runtime type, permissions, publishing readiness, and review workflow.
`/app-hub/agent-control-plane`	AI Agent Control Plane Hub	Agent registry, prompt library, run monitor, evaluation, handoff, permissions, cost, and safety.
`/app-hub/personal-data-sovereignty`	Personal Data Sovereignty	Data maps, source inboxes, consent, import/export, AI memory boundary, and storage policy.
`/app-hub/community-spaces`	Community Spaces Hub	Creator profiles, spaces, public apps, datasets, collections, remix culture, and contribution boards.
`/app-hub/operations-observability`	OS Operations Hub	Environment map, deploy pipeline preview, quality gates, performance, analytics placeholders, incidents, runbooks, and cost readiness.
`/app-hub/commerce-revenue`	Commerce & Revenue Hub	Pricing strategy, plan bundles, offer lab, checkout readiness, revenue split preview, invoices, trust, and metrics.

Founder Suite Hub

Founder Suite is the first productized vertical. It serves the Prox OS founding team first, then AI-native founders, solo builders, developer-workers, and micro-startup teams.

Included direction:

Roadmap.
Sprint planning.
Waitlist.
Launch.
Pricing.
Contribution.
Compliance.
GitHub signals.
Metrics.

Current UI incubation:

Founder Suite is the first productized vertical and currently ships as an internal-alpha, UI-only Hub cockpit at /app-hub/founder-suite.
P0 modules are cockpit-grade panels; P1/P2/P3 modules are a future module map, not top-level OS apps.
The surface does not provide legal, tax, immigration, or visa advice, and it does not include live billing or payment processing.

After OS shell persistence, the priority is not to backend every Founder Suite module. The first real backend loops should be visitor, waitlist, activation code, and feedback. Moments and personal data come later.

Product Studio + Launch/Growth Hub

Product Studio + Launch/Growth Hub is the second productized vertical. It focuses on the product launch loop: idea to product brief, waitlist, public launch prep, growth experiments, and metrics review.

Current UI incubation:

Product Studio currently ships as a UI-only internal alpha at the /app-hub/product-studio route.
P0 modules are cockpit-grade launch panels; P1/P2/P3 modules remain a future module map rather than top-level OS apps.
Product Hunt Room is prep UI only and does not publish, schedule, submit, or connect to Product Hunt.
Growth Experiments is a mock planning board and does not connect to analytics, ads, email, or community APIs.
Pricing, revenue readiness, and billing-adjacent panels do not include live billing, checkout, subscriptions, invoices, or payment processing.
The Hub complements Founder Suite: Founder Suite covers the founder operating system, while Product Studio covers product validation, public launch, and growth loops.

Micro-app Platform + Developer Platform Hub

Micro-app Platform + Developer Platform Hub is the third productized vertical. It focuses on the app builder loop: app contract, manifest, runtime surface, permissions, local dev tools, quality gates, and Store listing readiness.

Current UI incubation:

Developer Platform currently ships as a UI-only internal alpha at the /app-hub/developer-platform route. The restored Developer Console is a separate admin surface at /app-admin/developer.
P0 modules are cockpit-grade app-builder panels; P1/P2/P3 modules remain a future module map rather than top-level OS apps.
The Hub does not live-publish apps, publish packages, deploy projects, run CI, create developer tokens, or connect OAuth.
Permission scopes are mock declarations for review and do not grant access or enforce runtime permissions.
Store listing prep stays owner-scoped and does not implement a marketplace, global alias, live billing, revenue split, or app review backend.
The Hub complements Founder Suite and Product Studio: Founder Suite covers the founder operating system, Product Studio covers launch and growth, and Developer Platform covers OS-native app builder readiness.

AI Agent Control Plane Hub

AI Agent Control Plane Hub is the fourth productized vertical. It focuses on agent operations: agents, mission planning, context packs, tool permissions, human review, evaluation, cost awareness, and run timelines.

Current UI incubation:

Agent Control Plane currently ships as a UI-only internal alpha at the /app-hub/agent-control-plane route.
P0 modules are cockpit-grade agent operations panels; P1/P2/P3 modules remain a future module map rather than top-level OS apps.
The Hub does not run real agents, call model providers, execute tools, modify files, create background jobs, or connect external automations.
Permission scopes, context freshness, evaluation scores, and cost estimates are mock review rows and do not create real permissions, tokens, deployments, provider usage records, or billing.
The Hub complements Founder Suite, Product Studio, and Developer Platform: those Hubs define founder, launch, and app-builder workflows, while Agent Control Plane shows how AI work can be planned, reviewed, audited, and kept human-in-the-loop.

Personal Data Sovereignty Hub

Personal Data Sovereignty Hub is the fifth productized vertical. It focuses on the personal data cockpit: data maps, source inboxes, permission ledgers, consent categories, export readiness, backup readiness, data quality, privacy risk review, and AI context boundaries.

Current UI incubation:

Personal Data Sovereignty currently ships as a UI-only internal alpha at the /app-hub/personal-data-sovereignty route.
P0 modules are cockpit-grade data ownership panels; P1/P2/P3 modules remain a future module map rather than top-level OS apps.
The Hub uses local mock data only and does not handle real personal records.
The Hub does not upload, sync, back up, encrypt, export, import files, connect external APIs, enforce permissions, store consent, or provide legal compliance automation.
The Hub complements Founder Suite, Product Studio, Developer Platform, and AI Agent Control Plane by showing how personal data ownership and AI context boundaries should be visible before real storage or connector runtimes exist.

Community Spaces Hub

Community Spaces Hub is the sixth productized vertical. It focuses on community operating workflows: spaces, creator and org namespaces, member roles, contribution flow, rituals, knowledge commons, open datasets, and trust review.

Current UI incubation:

Community Spaces Hub currently ships as a UI-only internal alpha at the /app-hub/community-spaces route. The restored Community Admin surface lives separately at /app-admin/community.
P0 modules are Hub-internal panels, not separate top-level OS apps.
The surface does not create real Spaces, membership records, feeds, comments, invites, reports, moderation actions, payouts, or billing events.
It does not connect GitHub, Discord, Slack, Matrix, Telegram, Product Hunt, Notion, Airtable, analytics, or other external community APIs.
Trust and moderation panels are preview UI only. They do not provide legal, tax, immigration, visa, payout, or compliance advice, and they require human review before any future production behavior.
The Hub complements Founder Suite, Product Studio, Developer Platform, AI Agent Control Plane, Personal Data Sovereignty, App Store, and Pricing by making community space collaboration visible without changing URL doctrine.

OS Operations & Observability Hub

OS Operations & Observability Hub is the seventh productized vertical. It focuses on the operations loop: environment map, deploy pipeline preview, quality gates, build and bundle health, performance budget, analytics snapshot, incident readiness, runbooks, release train, and cost readiness.

Current UI incubation:

Operations & Observability currently ships as a UI-only internal alpha at the /app-hub/operations-observability route. The separate Admin Monitor lives at /app-admin/monitor.
P0 modules are cockpit-grade operations panels; P1/P2/P3 modules remain a future module map rather than top-level OS apps.
The Hub does not deploy, roll back, monitor, ingest logs, ingest analytics, create incidents, send alerts, meter costs, run queues, write config, handle secrets, or connect Cloudflare, Neon, GitHub, PostHog, Sentry, Statuspage, DNS, Pages, Workers, R2, billing, or provider APIs.
The Hub complements Founder Suite, Product Studio, Developer Platform, AI Agent Control Plane, Personal Data Sovereignty, Community Spaces, App Store, and Pricing by making release readiness and reliability review visible before real automation exists.

Commerce & Revenue Hub

Commerce & Revenue Hub is the eighth productized vertical. It focuses on commercialization readiness: pricing strategy, plan and bundle matrix, offer lab, checkout readiness, subscription lifecycle, revenue split preview, invoice and tax readiness, refund and trust policy, commercial metrics, and the open-source/commercial boundary.

Current UI incubation:

Commerce & Revenue currently ships as a UI-only internal alpha at the /app-hub/commerce-revenue route. User-facing concept Pricing remains separate at /app-os/pricing.
P0 modules are Hub-internal panels; P1/P2/P3 modules remain a future module map rather than top-level OS apps.
The Hub does not run checkout, billing, subscriptions, invoices, refunds, payouts, tax calculation, marketplace transactions, analytics, or entitlement checks.
The Hub does not connect Stripe, Paddle, Lemon Squeezy, Polar, PayPal, bank, tax authority, invoice provider, billing, analytics, or payment APIs.
The Hub does not provide legal, tax, or accounting advice.
The Hub complements Founder Suite, Product Studio, Developer Platform, AI Agent Control Plane, Personal Data Sovereignty, Community Spaces, OS Operations, App Store, and Pricing by making commercialization readiness visible before real commerce infrastructure exists.

Object	Meaning
`App`	A single runnable product surface.
`Hub`	A runnable product bundle or workspace that can include apps and modules, and may become subscribable.
`Collection`	A curated list or editorial playlist. It references resources but is not normally a runnable product.
`Folder`	User-defined desktop organization for shortcuts and layout.
`Space`	Collaboration or project context with members, permissions, installed surfaces, shared data, and logs.
`Module`	Hub-internal incubation unit that can later be promoted into an App.
`Surface`	Generic OS-visible resource that can be opened, installed, referenced, pinned, collected, or displayed.

Packaging Rules

A Hub can include apps and internal modules.
A Hub can be listed in the Store.
A Hub can support bundle pricing later.
A Hub can support developer revenue split later.
A Hub should not recursively own arbitrary Hubs by default.
A Hub should expose product workflow, not only visual grouping.

Hub App Model

On this page