OpenAI 2026 hackathon

Angels Board

A governed multi-agent workspace and Model Context Protocol (MCP) host that turns ambiguous developer tasks into evidence-backed, budget-capped, and human-approved outcomes.

Solo project by Konstantin Merdzhanov · 1 likes · 0 comments

Archive position — measured, not model output

1 like on Devpost

506 of the 7,856 archived projects have more likes, and 1,758 share exactly 1 — so this project's #602 place in the like-ranked listing is a tie-break inside that group, not a ranking.

Projects (log scale)

1
10
100
1k
10k
05,592
11,758
2285
3–4132
5–975
10+14

Likes on Devpost. ▲ marks this project's group.

Show the figures
LikesProjectsShare of archive
05,59271.2%
11,75822.4%
22853.6%
3–41321.7%
5–9751.0%
10+140.2%
Devpost like counts for all 7,856 archived projects, captured when this archive was built.

Executive Summary

What the company appears to be: Angels Board is a self-reported governed multi-agent workspace and Model Context Protocol (MCP) host designed to transform ambiguous developer tasks into evidence-backed, budget-capped, and human-approved outcomes. It is described as a system that manages autonomous AI coding agents in a controlled environment with safety gates, real-time visibility, and cost controls.

What changed: The project was submitted as part of the OpenAI 2026 hackathon. No indication of prior development or commercial activity exists beyond this submission.

Single most important open question: Is there any evidence of actual usage, traction, or product-market fit beyond the author's own description?

Back to contents

What The Product Actually Is

The description states that Angels Board is:

  • A governed multi-agent workspace
  • An MCP host (Model Context Protocol)
  • Designed to convert high-level developer prompts into safe, verified execution plans
  • Built with Dart backend, Flutter frontend, and GPT-5.6 Structured Outputs
  • Powered by a JSON-RPC Content-Length MCP host and client architecture

It features:

  • Shared Blackboard Architecture for real-time agent deliberation display
  • Dynamic Agent Lifecycle (Pool → Bench → Board pipeline)
  • Context Broker & Evidence Hygiene
  • Human Approval Gates
  • Budget Governor with cost cap enforcement

Inference: The system appears to be a developer tool aimed at managing AI agents in code workspaces, especially where safety and governance are critical.

Back to contents

Positioning & Claim Evolution

The description states that Angels Board was built out of a core engineering necessity:

"when agents gain the capability to modify production workspaces, their execution must be completely transparent, strictly governed, and human-in-the-loop by design."

It positions itself as solving problems with unmonitored AI agents ("black boxes") in development environments.

Claims include:

  • Converting ambiguous tasks into evidence-backed outcomes
  • Enforcing budget caps per debate
  • Requiring explicit human sign-off before applying changes
  • Using deterministic backend validators instead of relying on LLM self-regulation

Inference: This is a positioning statement about safety, transparency, and governance in AI-assisted development workflows.

Back to contents

Target Customer & ICP

The description states that Angels Board targets developers who:

  • Work with autonomous AI coding agents
  • Need to manage agent execution in production workspaces
  • Require visibility into agent deliberations and actions
  • Want to enforce cost controls and safety gates

It is implied to be a tool for engineering teams or individuals working on software development projects where AI agents may make changes.

Not evidenced: No specific customer segments, personas, or use cases beyond general developer needs are provided.

Back to contents

Business Model & Pricing Evidence

The description does not provide any information about:

  • Revenue model
  • Pricing structure
  • Monetization strategy
  • Customer acquisition plans

Inference: There is no evidence of a business model or pricing mechanism in the self-reported materials.

Back to contents

Technical & Delivery Signals

The project was built with:

  • Dart (backend)
  • Flutter (frontend)
  • GPT-5.6 Structured Outputs
  • JSON-RPC Content-Length MCP host/client
  • Context Broker
  • Budget Governor
  • Sandboxed test execution engine
  • Human-in-the-loop approval dashboard

It includes features such as:

  • Real-time event feed and graph display
  • Vote distribution charts
  • Cost/cache telemetry
  • One-click session abort control

Inference: The technical stack suggests a developer-focused tool with strong emphasis on security, observability, and control.

Back to contents

Traction & Maturity Signals

The description states that this is:

  • A hackathon submission (OpenAI 2026)
  • Built by one person (Konstantin Merdzhanov)
  • Not described as having any revenue, customers, or product-market fit

Not evidenced: No evidence of traction, adoption, or commercial maturity beyond the author’s own account.

Back to contents

Competitive Context

The description does not mention:

  • Competitors
  • Market landscape
  • Differentiation from existing tools
  • Prior art in multi-agent systems or AI governance for developers

Inference: The competitive context is unknown based on the provided information.

Back to contents

Key Risks & Red Flags

Key risks and red flags inferred from the description:

  • No evidence of product-market fit or traction
  • Only one team member involved
  • Self-reported only; no independent verification
  • No pricing, monetization, or business model described
  • The system is presented as a hackathon prototype, not a commercial product
  • Heavy reliance on GPT-5.6 and structured outputs without clarity on scalability or deployment

Back to contents

Diligence Questions To Ask The Founders

  1. What specific developer workflows does Angels Board aim to improve?
  2. How does it differ from other agent orchestration tools currently available?
  3. Is there any evidence of early adopters or pilot users?
  4. What is the plan for monetization and customer acquisition?
  5. Has the system been tested in real-world development environments?
  6. Are there any known limitations or trade-offs with the current architecture?

Back to contents

Investment/Partnership Verdict

Verdict: Not evidenced.

The description provides no evidence of:

  • Revenue
  • Customers
  • Traction
  • Product-market fit
  • Business model
  • Team traction or prior experience

This is a self-reported hackathon project with no indication of commercial viability or market readiness. The author states that it was built for the OpenAI 2026 hackathon, and there is no evidence of any further development or product launch.

Confidence Level: Low — based entirely on self-reporting without corroboration or external validation.

Back to contents

Source

Submitted to the OpenAI 2026 hackathon on Devpost. Project home on DevPost.

The analysis above was generated by a language model from the project's own one-line description. It is not independent research and contains no verified traction, revenue or customer data.