CurriculumOS

The description states that CurriculumOS is “Git for curriculum design.” It was built using FastAPI, PostgreSQL, Python, React, and TypeScript. The author submitted it to the OpenAI 2026 hackathon on Devpost.

• Not evidenced What specific functionality or features the product offers.
• Inferred (based on tagline): The tool may support version control for curriculum content, similar to how Git manages code changes.
• Not evidenced Whether it is a web application, desktop app, CLI, or other form of delivery.

The author describes CurriculumOS as “Git for curriculum design.” This is a self-reported positioning statement.

• Claim: The tool applies version control principles to educational content creation.
• Not evidenced How this differs from existing tools or platforms used in curriculum development.
• Not evidenced Whether the product has evolved from an initial prototype or concept into a more developed solution.

The description does not identify any specific customer segment or ideal customer profile (ICP).

• Not evidenced Who uses CurriculumOS, if anyone.
• Not evidenced The target audience for this tool — educators, institutions, curriculum designers, etc.
• Inferred (based on tagline): Likely aimed at users who manage educational content and may benefit from version control.

There is no evidence in the description of a business model or pricing strategy.

• Not evidenced How the product generates revenue.
• Not evidenced Whether it is free, subscription-based, one-time purchase, or otherwise monetized.
• Not evidenced Any pricing information or plans.

The project was built using FastAPI, PostgreSQL, Python, React, and TypeScript. It was submitted to a hackathon.

• Evidenced The tech stack includes FastAPI, PostgreSQL, Python, React, and TypeScript.
• Inferred (based on context): Likely a web-based application or tool with backend API and frontend components.
• Not evidenced Whether the product is production-ready, scalable, or has any deployment details.

The project was submitted to a hackathon and has no evidence of traction beyond that.

• Not evidenced Any user base, adoption rate, or usage metrics.
• Not evidenced Product maturity — whether it’s a prototype, MVP, or full product.
• Not evidenced Any feedback from users or early adopters.

The description does not mention any competitors or how CurriculumOS fits into the broader market for curriculum design tools.

• Not evidenced Who the competitors are in this space.
• Not evidenced How CurriculumOS compares to existing tools used for curriculum development or versioning.
• Inferred (based on tagline): It may compete with or complement platforms like Google Docs, Notion, or LMS systems that manage educational content.

• Risk: The product is a hackathon submission with no evidence of traction or commercial viability.
• Red flag: No team beyond one person (Macaulay Praise) — raises questions about execution and scalability.
• Red flag: Lack of clarity on the problem being solved, which may indicate weak market validation.

1. What specific problem does CurriculumOS solve that existing tools do not?
2. Who are the intended users, and how did you validate their needs?
3. How is the product different from current curriculum design or versioning tools?
4. Is there a plan for further development beyond this hackathon submission?
5. What is the long-term vision for the product and its business model?