Skip to content

Orbit documentation

Guides and reference for the Orbit platform: work tracking, code and CI/CD, observability, a knowledge base and an AI assistant, with one sign-in and one permission model.

Orbit is one platform made of five products. They share one account and one project membership model, and each company works on its own address, <company>.orbit.inortix.com.

Orbit tracks and plans work: projects, work items, Scrum and Kanban boards, backlog and sprints, workflows, JQL-style search, automation, plans and reports, with Jira import. The platform as a whole is also called Orbit.

Orbit Forge hosts code: repositories, merge requests, .gitlab-ci.yml-compatible pipelines, runners, environments and deployments, all linked to work items.

Orbit Pulse is observability: logs, traces, errors that file Orbit bugs, monitors, metrics, dashboards, SLOs and incidents. It ingests OpenTelemetry (OTLP/HTTP) and stores telemetry in ClickHouse.

Orbit Folio is the knowledge base: spaces, pages, templates, runbooks and postmortems, tied to the work they describe.

Orbit Lumen is the AI assistant across the products. It answers with sources, respects each person’s permissions and changes things only through confirm cards. On Orbit’s cloud it answers with Claude Haiku 5.5 from Anthropic. This is In development. The number of questions an organization can ask is set by its plan.

  1. Start with Getting started: what Orbit is, how to create your company, your first project and how to invite people.
  2. Then read the section of the product you are adopting: Orbit, Forge, Pulse, Folio or Lumen.
  3. Administrators continue with Administration.
  4. Developers go to Integrations & API and the API reference.

Orbit is in private preview and nothing is sold yet. These docs are written alongside the product. A page that describes something not fully built carries a status badge: In development or Planned.