Proxima OS

What the company appears to be: Proxima OS is a self-reported AI-native operating system that helps users move from an outcome goal to prepared work using GPT-5.6 and Codex. It orchestrates emails, calendars, docs, and code across multiple platforms, allowing users to describe what they want to do, review a plan or draft, and then act on it — all while remaining in control.

What changed: The project was submitted as part of the OpenAI 2026 hackathon. It is described as a prototype built by one person (MUAZU MUHAMMED ABDULLAHI), with no evidence of prior traction, revenue, or customer adoption.

Single most important open question: Is there any evidence that Proxima OS has moved beyond the prototype stage, or that it has been used by anyone other than its creator?

The description states that Proxima OS is an AI-native operating system powered by GPT-5.6 and Codex. It allows users to describe a goal (e.g., “prepare a meeting,” “research competitors”) and receive a structured plan or draft. Users can review, edit, save, or execute the work.

It integrates with services such as Gmail, Google Calendar, Slack, Notion, X, LinkedIn, Facebook Pages, and WhatsApp Business through supported authentication flows.

The system supports:

• Meeting planning
• Email drafts
• Research briefs
• Proposals
• Campaign planning
• Saved knowledge
• Approvals
• Activity history

It also supports recurring campaigns for social media publishing, where users can define a topic and schedule posts to be published daily or weekly until stopped.

The frontend is built with Next.js; the backend uses FastAPI. It uses technologies like WebSockets for live updates, durable storage for workflows, and various APIs (e.g., Gmail API, Google Calendar API, Slack API).

Inference: The product appears to be a personal productivity tool that automates routine tasks through AI-generated content and workflow orchestration.

The author positions Proxima OS as an AI-native OS that helps people move from idea to action without losing control. It emphasizes:

• Autonomy: Users can review and edit before executing.
• Integration: Works across multiple platforms (email, calendar, social).
• Control: Nothing is sent unless explicitly approved by the user.

The claim evolution shows a progression from solving a common problem—“work gets stuck between an idea and small steps”—to offering a solution that combines AI planning with human oversight.

Inference: The positioning reflects a desire to create a seamless, intelligent workspace for individuals who want automation without relinquishing control.

The description does not clearly define the target customer or ideal customer profile (ICP). It implies that Proxima OS is intended for individuals who need help organizing everyday work tasks—such as preparing meetings, drafting emails, or managing social campaigns.

It suggests a user base that values:

• Productivity
• Control over automation
• Integration across tools

However, there is no indication of whether the tool targets professionals, freelancers, teams, or enterprises.

Inference: The ICP likely includes solo users or small teams looking to streamline repetitive work using AI-generated content and workflow orchestration.

There is no evidence in the description of a business model or pricing strategy. The project is described as a hackathon submission with no mention of monetization, subscriptions, or paid features.

Not evidenced

The product was built using:

• Frontend: Next.js
• Backend: FastAPI
• Authentication: OAuth 2.0
• APIs: Gmail API, Google Calendar API, Slack API, Notion API, LinkedIn API, Facebook Pages API, WhatsApp Business API
• AI models: GPT-5.6, Codex
• Databases: PostgreSQL, Supabase
• Hosting: Vercel, Render

It supports:

• Real-time updates via WebSockets
• Workflow persistence
• Drafts and approvals
• Campaign scheduling
• Recurring campaigns

The system is described as deployable locally with a Next.js frontend and FastAPI backend.

Inference: The technical stack indicates a modern, scalable architecture suitable for integration-heavy applications. However, there's no evidence of production deployment or performance metrics.

There is no evidence of traction, revenue, or customer adoption beyond the author’s own account. The project was submitted to a hackathon and built by one person (MUAZU MUHAMMED ABDULLAHI). No data on usage, retention, or user feedback is provided.

Not evidenced

The description does not mention competitors directly. However, based on the features described—AI-driven task planning, workflow orchestration, multi-platform integration—the product overlaps with:

• Workflow automation tools (e.g., Make, Zapier)
• AI productivity assistants (e.g., Notion AI, ChatGPT plugins)
• Email and calendar management platforms (e.g., Gmail, Google Calendar)
• Social media scheduling tools (e.g., Hootsuite, Buffer)

It also shares similarities with personal knowledge management systems like Notion or Roam Research.

Inference: Proxima OS operates in a crowded space but may differentiate itself through its AI-native approach and focus on human-in-the-loop execution.

• Single-person development: The entire project was built by one individual, raising questions about scalability, maintenance, and long-term viability.
• Unverified claims: The use of GPT-5.6 is not confirmed; the version of OpenAI models used is unclear.
• No traction or revenue data: No evidence of users beyond the creator.
• Limited deployment info: While deployable locally, there’s no indication of cloud infrastructure or production readiness.
• Unclear monetization path: No business model or pricing strategy is described.

Inference: The lack of external validation and limited scope raises concerns about whether this will evolve into a viable product or remain a prototype.

1. What specific version of GPT/Codex are you using? Is it publicly available?
2. How many users have tested the system beyond yourself?
3. Have you considered how to scale beyond one developer?
4. What is your plan for monetization or commercialization?
5. Are there any known issues with API integrations that could affect reliability?
6. Can you demonstrate actual usage of the tool by others, not just internal testing?