Próx OS Positioning
Próx OS is a cloud-first, AI-native OS Space platform for developers, creators, teams, and communities.
One-line Positioning
Próx OS is a cloud-first, AI-native OS Space platform for developers, creators, teams, and communities.
Alternate strategic line:
Prox OS is a personal AI desktop where agents become visible, auditable, data-sovereign apps.For the fuller platform vision, object model, future OS app portfolio, MCP strategy, and competitor landscape, see prox-os-platform-vision.md and competitive-landscape.md.
Product Definition
Próx OS is not only a Web OS shell and not only an iframe bookmark launcher. It is a browser-native operating workspace that organizes GitHub, RSS, Hugging Face-style Spaces, cloud services, AI context, web apps, future local data sources, and public Spaces into a permission-aware personal, small-team, and community operating system.
The short-term product should be:
- Cloud-first: GitHub, RSS, Cloudflare, Neon, Notion / Airtable-style sources, deployed web apps, and hosted dashboards come before deep local indexing.
- GitHub-first: developer project intelligence is the clearest early wedge.
- RSS-first: information radar and knowledge inbox workflows are useful before a full data sovereignty suite exists.
- AI Context-first: the OS should prepare safe, scoped, reusable context for AI agents instead of relying on long ad hoc prompts.
Strategic analogy:
GitHub: where code lives.
Hugging Face: where models, datasets, and demos live.
Prox OS: where personal AI-native workspaces, OS apps, data sources, and AI contexts live.What It Is Not
Próx OS should not position itself as:
- A visual shell that only opens apps.
- An iframe bookmark launcher where embeds are the final value.
- A full Google Drive, Notion, Nextcloud, Eagle, or Apple Photos replacement from day one.
- A data sovereignty suite that tries to ingest all personal data before the cloud-first workflow is compelling.
- A direct GitHub or Hugging Face replacement.
- A heavyweight platform that hosts all code, files, models, inference, and databases before the OS Space loop is proven.
Data sovereignty remains a core long-term capability, but it should land through focused apps, source models, permissions, export flows, and a later local bridge.
Prox OS should not market itself as a finished privacy compliance product in v0.1. The right posture is privacy-by-design: user agency, export/delete direction, visible agent scopes, manual confirmation, auditability, and portable app/data interfaces.
App Store Role
The App Store is not a normal marketplace. It is the incubation entry for:
- Apps: installable or previewable OS surfaces.
- Templates: reusable starting points for radars, dashboards, and homes.
- Spaces: public or private project/data/app workspaces that can later be cloned or remixed.
- Data Sources: GitHub, RSS, cloud, database, knowledge, and future local connectors.
- AI Workflows: source-scoped prompts, summaries, agents, and context packs.
The runtime app registry remains the source of truth for apps that can actually open. The store catalog may include incubating, coming soon, concept, and roadmap items as long as the UI labels them honestly.
Early Product Wedge
The most important near-term demo is Awesome GitHub Radar:
- Input an awesome repository URL.
- Parse the README into structured project entries.
- Enrich entries with stars, license, language, and last update.
- Add AI summaries and comparison notes.
- Save the result into Próx OS as a radar app or Space.
This demo explains the larger OS better than an abstract platform pitch: external source in, structured information out, AI-readable context, reusable views, and a future public Space.
Early narrative:
Paste an awesome GitHub repo. Get a living OS Space.Broader runtime narrative:
Bring your Airtable, Baserow, Notion, GitHub, and local data. Build your own Prox App interface. Own the runtime.v0.1 Market Posture
v0.1 is English-first, public-preview, waitlist-led, and invite-only beta. It
should not start as a broad consumer launch, enterprise compliance launch,
automatic marketplace payout launch, or global paid self-serve launch.
| Stage | Target | Why |
|---|---|---|
| Public preview | Explain the OS Space, data sovereignty, and visible-agent story. | Validate the narrative before collecting sensitive data. |
| Waitlist | Segment early interest by builder type and data/agent need. | Keep onboarding intentional and privacy-aware. |
| Invite-only beta | Work with high-signal builders and developers. | Learn from users who understand agents, data, apps, GitHub, and privacy. |
| Curated builder program | Invite app/Space/template contributors with clear scope. | Build ecosystem quality before opening a marketplace. |