Roadmap

What we are building next

Orbit is in private preview. We would rather show the whole picture than hide the gaps, so every item on this site carries its real status. Dates are not promised.

Built

No badge. Finished and working today. It is described on the product pages.

In development

In development

Built and in final testing, not yet open to everyone.

Planned

Planned

Designed and not started.

Order of work: the Orbit core and its redesigned interface first, then the redesigned Forge, Pulse, Folio and Lumen screens, then everything needed for launch.

Orbit

Finish automation, integrations and Jira import, then bring every screen to the redesigned interface.

Next

  • Automation: final testingIn development

    Rules, triggers, schedules, actions, run history and usage limits are built and in final testing.

  • Outgoing webhooksIn development

    Signed event subscriptions with retries and a delivery log.

  • GitHub and GitLab development information, smart commitsIn development

    Branches, commits, requests and deployments linked to work items.

  • Jira Cloud import: final testingIn development

    The four-step import wizard and the compatibility report.

  • Presence and feature switchesIn development

    See who is reading a work item. Turn preview features on per site.

  • Locale, time zone and accessibility passesIn development

    Unicode, daylight-saving-time digests, and keyboard and contrast checks on every screen.

  • Remaining screens in the redesigned interfaceIn development

    The rest of the Orbit screens move across, then a unified e-mail style.

Later

  • Service managementPlanned

    Customer portal, request types, queues, SLAs, on-call, incidents and changes.

  • Assets and configuration managementPlanned

    Object schemas, typed attributes, graph view and imports.

  • Product discoveryPlanned

    Ideas, prioritisation, roadmaps and delivery links.

  • Enterprise operationsPlanned

    Sandboxes, data residency, organization policies, multi-site administration and BI connectors.

  • Orbit MCP server and extension frameworkPlanned

    Permission-checked read and write tools for external agents, and namespaced fields, panels and actions.

  • Notification centre, sprint planning by people, mobile PWAPlanned

    Planned for after launch.

Orbit Forge

Finish local CI tooling and enterprise sign-in, then grow deployment: templates, progressive delivery, Pages and agents.

Next

  • Local CI lint and dry runIn development

    Check a pipeline from the command line before you push.

  • SSO, SCIM and organization groupsIn development

    Follows the Orbit sign-in work.

  • Forge screens in the redesigned interfaceIn development

    Forge moves to the redesigned interface after the Orbit screens.

Later

  • Shared runnersPlanned

    Hosted runners with CI minutes and concurrent jobs per plan. Your own runners do not use minutes.

  • Deployment templatesPlanned

    Components for blue/green, Kamal, Swarm, Helm, static CDN and database migrations.

  • Progressive delivery checked by PulsePlanned

    Canary steps that compare errors and latency and roll back automatically.

  • Environment targets and "what runs where"Planned

    A view of what is deployed where.

  • Forge PagesPlanned

    Static sites on a CDN.

  • Kubernetes agentPlanned

    A GitOps agent for clusters.

  • Feature flagsPlanned

    Unleash-compatible flags.

  • DORA metricsPlanned

    Delivery metrics from deployments.

  • Smaller Forge itemsPlanned

    Conflict editor, draft merge requests, after-script steps, service containers, other package formats and active security scanning of running apps.

Orbit Pulse

Separate data per organization first, then monitoring for your own databases and the rest of your stack.

Next

  • Pulse per organizationPlanned

    Telemetry kept separate for each company site, needed before launch.

  • Pulse screens in the redesigned interfacePlanned

    Pulse moves to the redesigned interface after the Orbit screens.

Later

  • Integrations for your own stackPlanned

    A catalog, agents in your network, remote configuration and secrets kept beside the agent.

  • PostgreSQL for team databasesPlanned

    Connect your own PostgreSQL databases with a guided wizard.

  • Prometheus, OpenMetrics and OTel CollectorPlanned

    Bring existing metrics in.

  • MySQL and MariaDBPlanned

    Database monitoring for MySQL family.

  • Redis and ValkeyPlanned

    Cache monitoring.

  • MongoDBPlanned

    Document database monitoring.

  • ClickHousePlanned

    Analytics database monitoring.

  • Queues, streams and agentless cloud integrationsPlanned

    Later stages of the integrations plan.

  • Version-compare API for progressive deliveryPlanned

    Lets Forge check a new version against Pulse data.

Orbit Folio

Separate knowledge per organization and the redesigned interface; richer content types come after the first version.

Next

  • Folio per organizationPlanned

    Knowledge kept separate for each company site, needed before launch.

  • Folio screens in the redesigned interfacePlanned

    Folio moves to the redesigned interface after the Orbit screens.

Later

  • Whiteboards and Notion-style databasesPlanned

    Out of the first version.

  • Public product documentation inside FolioPlanned

    Docs-as-code showing published documentation in a space.

Orbit Lumen

Agents, administrator tools and your own model for customer-run installations, with a spending safeguard before the Free plan opens.

Next

  • Claude Haiku 5.5 on Orbit’s cloud: final testingIn development

    The Anthropic provider that answers on Orbit’s cloud, tested live with plan limits.

  • Your own model on a customer-run installationPlanned

    An open-weight model through an OpenAI-compatible endpoint, with a paid provider only when an administrator adds a key and a budget ($0 by default). Needs the self-hosted licence.

  • Usage dashboard on live dataIn development

    Calls, tokens and cost by model, function, person and agent.

  • Access explanations and settings previewsIn development

    Why a person has no access, and what a setting will change before you publish it.

  • Built-in agents on live eventsIn development

    Triage, release notes, code review, pipeline doctor, incident analyst and more.

  • MCP server: final testingIn development

    Read-only tools for coding agents.

  • Spending safeguard before the Free plan opensPlanned

    A cap on AI costs that has to be in place before the Free plan opens.

  • Lumen per organizationPlanned

    The assistant kept separate for each company site, needed before launch.

Later

  • Agent hand-off of work with recorded outcomesPlanned

    Agents take work and record what they did.

  • Governed backlog-to-merge-request loopsPlanned

    From a backlog item to a merge request under policy.

  • Voice and imagesPlanned

    Out of the first version.

Platform

What has to be finished before launch, then scale: more servers, own domains, self-hosting and more languages.

Next

  • Single sign-on and SCIM: final testingIn development

    SAML, OIDC, SCIM and enforced single sign-on.

  • Multi-factor sign-in and Google and Microsoft sign-inPlanned

    On every plan.

  • Forge, Pulse, Folio and Lumen separated per organizationPlanned

    All four products on every company site.

  • Plans, limits and checkout through PaddlePlanned

    Plans and limits enforced, payments through Paddle.

  • Sign-up with plan choice and email confirmationPlanned

    The flow previewed on the sign-up page.

  • Service administration tools, full organization export and legal pagesPlanned

    Terms, Privacy, Refunds, DPA and sub-processors.

  • Updates without downtime, before openingPlanned

    Services are replaced one at a time, and database changes are made in compatible steps.

Later

  • Self-hosted Enterprise licencePlanned

    A signed licence file checked offline.

  • Several sites per organization and own domainsPlanned

    Enterprise.

  • CDN by RUM data, a second server with load balancer and PostgreSQL replicaPlanned

    Scale-out steps from the deployment plan.

  • Multilingual interface, wave 1Planned

    English, Russian, Ukrainian, German, French, Spanish, Brazilian Portuguese, Italian, Polish, Turkish, Dutch, Japanese, Korean and Simplified Chinese.

  • Multilingual interface, wave 2Planned

    Traditional Chinese, Arabic, Hebrew, Hindi, Indonesian, Vietnamese, Czech and Swedish.

  • Multilingual documentationPlanned

    With a translation pipeline.

Needed before launch

Public sales open when all of these are in place.

  • SAML, OIDC and SCIM finished and tested
  • Forge, Pulse, Folio and Lumen separated per organization
  • Plans, limits and checkout through Paddle
  • Sign-up with plan choice and email confirmation
  • Legal pages: Terms, Privacy, Refunds, DPA and sub-processors
  • Updates without downtime in place

Languages

English is the source language. The structure allows more, and translated documentation follows the interface in waves.

Wave 1 Planned

English, Russian, Ukrainian, German, French, Spanish, Brazilian Portuguese, Italian, Polish, Turkish, Dutch, Japanese, Korean and Simplified Chinese.

Wave 2 Planned

Traditional Chinese, Arabic, Hebrew, Hindi, Indonesian, Vietnamese, Czech and Swedish.

Dates are not promised.

Follow along from the inside

Orbit is in private preview. Every new organization will start with a 14-day Business trial, no card required.