Prox Cloud Roadmap

Prox Cloud is the future hosted Prox OS runtime for personal workspaces, private moments, app bundles, and eventually creator spaces. It is not a normal SaaS dashboard. It is a cloud-hosted personal and community OS runtime where apps, files, AI context, workspaces, and activity can share one operating surface.

This roadmap is intentionally non-implementation. The current repo should keep architecture-ready hooks without building the hosted product too early.

Product Position

Prox Cloud should eventually provide:

• hosted personal Studios,
• private app and data bundles,
• durable file and artifact storage,
• workspace-scoped search and activity,
• AI context surfaces,
• creator and community spaces later.

The difference from a conventional dashboard is that the user opens a living OS space, not a collection of isolated settings pages.

Early Stages

1. Single-user private cloud alpha.
2. Invite-only private beta with narrow workspace limits.
3. Public profile surfaces later.
4. Creator spaces much later, after trust, storage, and operational loops are mature.

Possible Infrastructure

Likely building blocks:

• Cloudflare Workers for API edges.
• Cloudflare Pages for deployable web surfaces.
• Cloudflare R2 for object storage.
• Cloudflare KV and Durable Objects for lightweight coordination.
• Cloudflare Queues for async jobs.
• Neon Postgres for relational product data.
• Email provider for invites and notifications.
• Payment provider for plans.
• Product analytics for activation and retention signals.

These choices are directional. They do not authorize implementation until the hosted product has explicit acceptance criteria.

Cost Is Not Only Infrastructure

Hosted Prox OS creates operational obligations:

• user support,
• abuse handling,
• backups and restores,
• security response,
• billing support,
• data migration,
• incident communication,
• operational monitoring,
• long-term data retention decisions.

Infrastructure can be cheap while operations are expensive. The roadmap should avoid turning the repo into a hosted service before those responsibilities have owners.

Activation Conditions

Start real Prox Cloud implementation only when several conditions are true:

• the browser OS shell has a clear retained-use wedge,
• app bundles have repeatable activation signals,
• storage and workspace contracts are stable enough to persist,
• operational ownership is explicit,
• billing and support paths are ready enough for private users,
• the package taxonomy keeps browser, runtime, data, and backend boundaries clear.

Current Principle

Do not build Prox Cloud now. Keep package contracts, workspace context, files, AI UI, activity, and admin growth surfaces ready for a future hosted runtime.