Orchea: engineering intelligence for teams and AI coding agents

Engineering intelligence layer

Don't manage tasks. Understand engineering.

Every commit, PR, task, agent run, and CI result in one stream.

Invite-only. Sign in with the account your invite was sent to.

Signal

pr.merged: auth refactor lands in main2m
agent.tests_passed: 214 specs green9m
pr.opened: event ingestion pipeline1h
task.completed: BCN-42 shipped4h
GitHubCI/CDCoding agentsKnowledge
What Orchea is, and how it works ↓

Under the hood

Every signal, one endpoint

Coding agents and CI pipelines report straight into the same event stream a person's work produces, with no separate integration to maintain.

Live pulse

Real-time visibility without asking for status updates.

Agent-native

Coding agents and CI push structured events, and Orchea attributes them to people and work.

events.http
POST /api/events
Authorization: Bearer orc_****

{
  "type": "agent.tests_passed",
  "summary": "CI green on orchea#482",
  "actor": "claude-code"
}

Frequently asked

What Orchea is, and how it works

Orchea replaces the status update with a derivation. Below is what that means in practice: the model underneath, what it connects to, and where the boundaries are.

What is Orchea?

Orchea is an engineering intelligence layer that sits above GitHub, CI/CD, coding agents and team communication. It continuously ingests what happens across an engineering organisation into a single append-only event stream, then derives status, dashboards and answers from that stream instead of asking people for updates.

What is software engineering intelligence?

Software engineering intelligence (SEI) is the practice of measuring engineering work from the systems it already produces (version control, CI, issue trackers, agent runs) rather than from self-reported status. An SEI platform normalises those signals into a shared model so leaders can see delivery, flow and risk without instrumenting people directly.

How is Orchea different from Jira or Linear?

Jira and Linear are systems of record: a human moves a ticket, and the board reflects what that human remembered to do. Orchea stores no status at all. Work item status is a projection folded from the event stream: task.started resolves to in progress, pr.opened to in review, pr.merged to done, so the board cannot drift from what the repository actually shows.

How does Orchea give visibility into AI coding agents?

Coding agents and CI push structured events straight to Orchea over a single authenticated endpoint, POST /api/events, using a workspace API key. An agent reports agent.planning when it forms a plan, agent.tests_passed when a suite goes green, and agent.completed when work is verified done. Identity resolution attributes each event to the right engineer and the right work item, so agent output appears in the same stream as human output rather than in a separate tool.

What data sources does Orchea connect to?

Orchea takes signals two ways. Connectors pull from tracked sources (GitHub repositories today) and normalise them into typed events such as code.commit, pr.merged and task.status_changed. The ingestion API lets coding agents, CI pipelines and internal scripts push events directly. Notes, documents and meeting summaries can also be ingested into a semantic knowledge base that the AI chat searches alongside the event stream.

Can an AI assistant query Orchea directly?

Yes. Orchea exposes a Model Context Protocol server at /api/mcp with OAuth dynamic client registration, so MCP-capable coding agents such as Claude Code, Codex and Cursor can authorise themselves and then read work items, plans, documents, events and the knowledge base as first-class tools. The agent writing the code and the system reporting on it talk to the same API.

How does Orchea decide a work item is done?

By folding the events attached to it, in order. Orchea never writes a status field that a projection would later contradict; status is recomputed from the stream, which means the history that produced it is always inspectable. If a task shows as done, the merge commit that made it done is one click away.

Does Orchea monitor individual engineers?

No, and the role model enforces it rather than merely promising it. Engineers see their own teams’ timeline, work and chat, and roster names only, no peer metrics. Managers see dashboards for the teams they are responsible for. Team lead is a per-team flag granting manager-like visibility for that one team. The design rule is to assist engineers, not to monitor them.

Who can sign up for Orchea?

Orchea is invite-only. An admin issues a one-time /join link that carries a predefined role and team assignment and expires after seven days; sign-in is GitHub OAuth against the account named on that invite. A GitHub account with no workspace membership is refused at the callback.

GitHub · CI/CD · Coding agents · Knowledge

Powered byIntellina© 2026 Intellina. All rights reserved.