What is Orneos?

Orneos is a work platform for software teams where the purpose of a change stays attached to the change. Issues, team documentation, the agreed requirements for a piece of work, and the material a reviewer needs to judge it all live in one place, on a local-first substrate that responds instantly and keeps working when the network does not.

The shortest honest description:

Orneos exists so that whoever reviews a change can tell whether it does what the team agreed it would do — without reconstructing the agreement from memory, chat scrollback and a pull request title.

That problem got sharper when agents started writing code. A person who writes a change carries its intent in their head. A person who reviews someone else’s agent-assisted change carries none of it, and the change itself rarely says.

Who it is for

Orneos is aimed at small software teams, and inside those teams at the person doing the reviewing — usually a technical founder, a lead, or the engineer who ends up approving everyone else’s work.

It is a reasonable fit if you:

• review changes you did not write, increasingly ones an agent had a hand in;
• have lost time to “what was this supposed to do again?”;
• want work tooling that is instant and survives a dropped connection;
• would rather have the decisions behind a change written down than re-derived.

It is a poor fit today if you need enterprise administration, a mature integrations catalogue, or a guarantee of availability. See Known limits — we would rather you read that page before you commit a team to this.

What it actually is right now

Three things, in one app:

A work tracker. Issues with the usual fields, three views over them (Board, Backlog, Timeline), labels, projects, sub-issues and typed relations, comments, filters and saved views, and search. Multiple teams inside a company, with roles. Personal favorites keep frequently used pages and views close, with drag ordering and controls to hide custom tabs.

A documentation layer. Vault — spaces and pages of rich text, co-edited in real time, sitting next to the issues they describe rather than in a different product.

An agreement and review layer. Intent records what a piece of work is supposed to accomplish, as an approved, versioned statement with a named approver. Context bundles assemble the task, that agreement, available discussion and linked Vault references, without page bodies, into one inspectable block of markdown you can hand to a reviewer or an agent.

Underneath all three is a local-first sync engine: your changes are written to a database inside your browser first and pushed to the server in the background.

What it is not, yet

Specifically, and stated plainly:

• Agents do not execute work in Orneos. There is no agent that picks up an issue and changes your code. That remains a planned direction.
• Context delivery, capture and review are work in progress. Automatic bundles and Intent already work. The complete review surface is not released; assisted early access bridges the remaining steps.
• There is no integrations catalogue. No Slack app, no GitHub sync, no importers.
• Programmatic access is minimal. Two read-only tools over MCP, Work in progress and requiring a separately enabled implementation. No public GraphQL or REST API.

Product status is the full matrix, kept as the single place where availability is claimed.

How to get access

Orneos is invite-only. Request a pilot and tell us what you are actually trying to review — we read every request and prioritise teams with a concrete case rather than a general interest.

If you already have access, go to Quickstart.

Feature guide and new-feature hints

The first-run guide opens a tour of core features. You can skip it or finish it, then reopen the guide from its help launcher. A badge highlights new feature hints you have not seen. Tour progress is saved in this browser, so another browser or cleared site data can show the tour again.

Optional app installation

Where supported, use your browser’s Install app or Add to Home Screen command to open Orneos in a standalone window. Availability and wording depend on the browser. This uses the same web application and its storage boundaries; it does not provide a separate native runtime or guarantee offline launch. See Offline and reconnect.

Browser requirements

Orneos runs in the browser; installation is optional. It depends on a shared worker, an origin-private filesystem and a live WebSocket, so it needs a current browser:

Use a current desktop browser with SharedWorker, origin-private storage and WebSocket support enabled. API availability alone does not establish a tested browser/version combination; we do not publish verified minimum versions yet. If startup fails, share the browser version and storage settings with support.

Private or incognito modes can restrict the storage APIs the app needs, so startup is not guaranteed. Where the app runs, treat that storage as temporary: closing the private session can discard unsent work. Use an ordinary browser profile for work you need to retain.