The platform
Orbit is a work platform for software and business teams. Orbit (work tracking), Forge (code and CI/CD), Pulse (observability), Folio (knowledge) and Lumen (an AI assistant) run as one product with one account and one project membership model. Each company works on its own address, with its data isolated at the database level.
Orbit is in private preview. Nothing is sold yet.
The chain, in detail
Each link below is a built, tested behaviour. Where a link is still in development or planned, it carries a badge.
A repository belongs to an Orbit project and inherits its members. Put a work item key in a branch, a commit or a merge request and the link is made for you.
Pulse records each Forge deployment, compares error rate and latency before and after it, and points at the commits behind a new error.
An error group or a monitor files an Orbit bug through Orbit’s own create path, as a person, and keeps it in sync in both directions. A recurring problem comments on the existing bug.
A runbook page shows the live state of every monitor that points to it. When an incident closes, a postmortem page is generated from its timeline.
A key in text becomes a live link with status and title. Select text, create a work item from it, and the page and the work item keep a link to each other.
Show a file or line range from a repository at a pinned commit, and sync a Markdown folder into a space. Changes to managed pages go through merge requests.
One cited answer from the incident, its monitors, the deploy and its commits, the related work items and the Folio runbook. Lumen reads each product through its API as you, so it never shows what you may not see.
One identity
Forge, Pulse, Folio and Lumen resolve the same Orbit session and check your current project role on every request.
Every product reads the Orbit session. Sign in once, and every product knows who you are.
A repository, a space and a telemetry project belong to an Orbit project and inherit its members.
Choose, in one people directory, who may open Code/CI, Observability, Knowledge and Lumen.
Your company, your address
Each company works on <company>.orbit.inortix.com. The site is taken from the host name, and the data sits behind PostgreSQL row-level security on all 139 site tables. The browser test suite runs two company sites side by side with the same project keys, and each sees only its own.
One quota, one bill
Plans will give each organization one storage quota for all four kinds of data, one maximum file size and one bill. Planned Per-organization quotas and billing are still being built, and limits are not yet set per organization. There is no per-seat telemetry: who sees telemetry is decided by project permissions.
AI with guardrails
On Orbit’s cloud, Lumen answers with Claude Haiku 5.5 from Anthropic. How many questions an organization can ask is set by its plan.
The Lumen server cannot write to any product. Every change is a confirm card that your browser runs with your session.
Lumen reads each product through its API as you. Only the question, page context and manifest fields reach the model.
Parallel search across all products with each product’s permissions, even when no model is configured.
OpenTelemetry first
OTEL_EXPORTER_OTLP_ENDPOINT=https://<your-orbit-address>/otlp
OTEL_EXPORTER_OTLP_HEADERS=X-Pulse-Key=<project ingest key>
OTEL_SERVICE_NAME=checkoutPulse takes OTLP/HTTP logs, traces and metrics in protobuf or JSON. Angle brackets mark values you fill in.
Durable and verified
Every write appends history and an outbox row in the same transaction. Workers de-duplicate and resume after a crash.
A PostgreSQL or Redis outage answers a typed, retryable error. It is never a fake success, and committed work survives.
Backups cover the database, attachments and configuration. A drill checks row counts and every attachment hash.
Integrations and API
A versioned REST API, tokens you control and manifests that let a product join Lumen without code changes.
/api/v1 with typed error bodies, paging headers, rate limits and a public OpenAPI document.
A committed route list is compared with the server, and responses are checked against the schemas.
Logs, traces and metrics with project ingest keys.
Scoped, expiring, hashed project access tokens and SSH keys.
A product publishes a manifest and Lumen reads it, with no code changes. Joining a new product is a Lumen setting that Orbit controls, so it is not available on Orbit’s cloud yet.
Signed HMAC-SHA256 event subscriptions with filters, rotation, retries and a delivery log.
Orbit is in private preview. Every new organization will start with a 14-day Business trial, no card required.