What is Orbit

Orbit is a work platform for software and business teams. It is made of five products that run as one: Orbit (work tracking and planning), Orbit Forge (code and CI/CD), Orbit Pulse (observability), Orbit Folio (knowledge base) and Orbit Lumen (AI assistant). The platform as a whole is also called Orbit.

One account. Forge, Pulse, Folio and Lumen use the same Orbit session as Orbit itself. You sign in once.
One permission model. The products check your current Orbit project role on every request. Lumen reads the products only through their APIs, as the person asking.
One storage quota per organization is Planned. Pulse data, Forge repositories and artifacts, Folio files and Orbit attachments are meant to share it.
Product access is set in one place. In the people directory a site administrator chooses who may open Code / CI, Observability, Knowledge and Lumen. See People, groups, guests and product access.

Your company has its own address

Each company works on its own address, <company>.orbit.inortix.com, for example acme.orbit.inortix.com. The site is taken from the host name, and the data of every company is isolated at the database level with PostgreSQL row-level security. Every API call, search, export and live event excludes other companies.

Projects are the unit of membership

A project is where work happens, and it is the unit of membership for every product. People get a role in a project (administrator, member or viewer), and that role decides what they can do in Orbit and in the other products for that project. Roles are explained in Invite people and set roles.

From a work item to a postmortem

The products are connected by links that you do not have to maintain by hand.

A work item in Orbit is linked to its branches, commits, merge requests and deployments in Forge. Work item keys in branch names, commit messages and merge requests are extracted and linked to work items of the same project.
Pulse records each Forge deployment and compares the error rate and latency before and after it.
An error in Pulse can file an Orbit bug, and the bug and the error stay in sync both ways: closing the bug resolves the error, and a regression reopens or comments on the bug.
An incident in Pulse becomes a postmortem page in Folio from a template. The follow-up actions are created as Orbit tasks and tracked on the page until they are closed.
Lumen can answer a question such as “What broke?” with the deployment, its commits, the related work items and the runbook in one answer with sources.

What “built”, “in development” and “planned” mean

Orbit is in private preview and nothing is sold yet. These docs say plainly what exists.

Status	Badge	Meaning
Built	none	Available and working.
In development	In development	Working or under way, but still being finished and tested.
Planned	Planned	Not built yet.

A page that describes anything not fully built ends with a status note.