Pluto

The description states that Pluto is a teacher-controlled learning workspace that connects schools and community organisations. It allows partners to submit local challenges, which are then shaped into structured missions by AI tools (specifically Codex and GPT-5.6). These missions include curriculum links, roles, milestones, deliverables, sources, rubrics, and safeguards.

Students work through checkpoints, research, collaborate, document evidence, reflect, and submit their work. Teachers assess individual contributions, while partners validate the usefulness of outcomes. The system generates a “Pluto Proof” record that includes consent awareness, audit history, and evidence provenance.

The product supports three AI modes:

• Live AI: Uses configured OpenAI models.
• Template mode: Deterministic local structures when live generation is unavailable.
• Restricted policy mode: Enforces server-side safety limits on coaching.

It also features an assignment engine that proposes balanced student teams based on interests, strengths, availability, accessibility needs, and role coverage — all of which must be approved by a teacher.

The system includes:

• Partner challenge intake
• Teacher mission review and approval
• Roster import and team assignment
• Student workspace with research, artefacts, reflection, and submission flows
• Evidence linking, consent, publication controls, audit history
• Per-student assessment and gradebook export
• Pluto Proof verification record

It is built using Next.js, React, TypeScript, OpenAI, Codex, SQLite, Zod, Vercel, and GitHub Actions.

Not evidenced No evidence of actual users, real data handling, or production deployment beyond the demo environment. The product is described as an open pilot foundation, not a production-ready system.

The description states that Pluto aims to address two key problems:

1. Schools want learning to feel useful beyond the classroom.
2. Community organisations have meaningful local problems but lack safe, structured ways to work with students.

It positions itself as an alternative to generic AI tools by asserting:

• AI helps structure complex work but does not silently decide truth, assignments, or grades.
• Teachers remain responsible for mission approval, student access, assessment, and publication.
• Partners validate usefulness, not individual student grades.
• The system clearly labels every AI state (Live AI, Template, Restricted).
• It enforces policy boundaries server-side.

Pluto’s positioning is framed around accountability, control, and structured learning. It claims to offer a “different contract” in education AI — one that prioritizes teacher agency and ethical use of AI over automation.

Inference This suggests a move away from tools that treat AI as a black box toward systems where educators maintain oversight and responsibility for outcomes.

The description identifies three main user types:

1. Partners: Local community organisations with real challenges.
2. Teachers: Responsible for reviewing missions, assigning students, assessing work, and publishing results.
3. Students: Engage in structured learning missions with clear roles and deliverables.
4. School administrators: Likely involved in managing access and operational support.

It also mentions that the system is designed for use by schools and educators working with external partners to create meaningful student experiences.

Not evidenced No evidence of actual customers, target segments, or market segmentation beyond these user roles. No mention of specific school sizes, geographic scope, or institutional adoption.

The description does not contain any information about pricing, monetisation, or business model. It only describes the product’s functionality and technical architecture.

Not evidenced No indication of how Pluto intends to generate revenue, whether through subscription, licensing, grants, or other means.

Pluto is built with:

• Frontend: Next.js, React, TypeScript
• Backend/Infrastructure: OpenAI (Codex and GPT-5.6), SQLite, Zod
• Deployment: Vercel, GitHub Actions
• AI Implementation: Codex used for interface consolidation, workflow logic, policy enforcement, deployment fixes, design refinement, type checking, linting, testing, and builds.
• GPT-5.6: Powers live mission generation and coaching paths when configured.

It includes:

• Server-side authorization
• Migrations
• Evidence handling
• Assignment constraints
• Audit path recording

Not evidenced No information on scalability, data security, cloud infrastructure beyond Vercel, or integration capabilities with LMS/SIS systems. No mention of managed identity, storage, malware scanning, monitoring, accessibility validation, localization, or operational support.

The description states that Pluto is an open pilot foundation, not a production system for real student data. It includes:

• A public repository with a seeded Kochi waste-separation mission
• Demo accounts for partner, teacher, student, and admin roles
• Pilot password: pluto-demo

It explicitly notes that before school-wide deployment, Pluto still needs:

• Managed identity
• Managed relational and object storage
• Retention and deletion controls
• Malware scanning
• Monitoring
• Accessibility validation
• Localisation
• LMS/SIS integrations
• Operational support

Not evidenced No evidence of real-world pilots, customer feedback, or actual usage beyond the demo environment. No mention of traction metrics, user engagement, or adoption rates.

The description does not provide any information about competitors or competitive positioning. It does not name other platforms or tools in the education AI space.

Not evidenced No evidence of market analysis, competitive landscape, or differentiation from existing solutions.

1. Unproven traction: The product is described as a demo and pilot, with no real-world usage or customer data.
2. Limited maturity: The system is explicitly stated to be incomplete for production use, lacking features like managed identity, storage, compliance, and integrations.
3. Unclear monetisation: No business model or pricing strategy is described.
4. AI dependency without clarity on governance: While it claims to enforce policy boundaries, there’s no evidence of how these are enforced in practice or audited.
5. Single-founder team: The project is attributed to one person (Koushik Ghosh), raising questions about scalability and resource capacity.

1. What specific feedback have you received from teachers, students, or partners during the pilot phase?
2. How do you plan to scale beyond the current demo environment into a production-ready system?
3. Have you identified any real-world use cases or partnerships with schools or community organisations?
4. What are your plans for addressing compliance, data privacy, and accessibility requirements?
5. Is there any intention to monetize this platform? If so, what is your go-to-market strategy?
6. How do you intend to manage the transition from AI-assisted mission creation to full autonomy in a classroom setting?