Skip to content
Orbitrum logo
Orbitrum
Platform Roadmap

Roadmap at a Glance

The Orbitrum roadmap brings strategy, platform work, Atlas development, website publishing, brand, and infrastructure into one view so current priorities, shipped work, and next milestones stay clear.

64 structured roadmap itemsLast sync Mar 25, 2026
Total items
64
In progress
16
Planned
13
Shipped
35
Interactive Timeline
Past/Now/Next
1 Quarter
Filter by Tags0 of 0 selected
4.0 year span

No roadmap items match the current tag selection.

Re-enable a few tags or reset the filters to restore the full timeline.

Overview

What the roadmap is optimizing for right now

The roadmap brings Orbitrum's current execution into one view, connecting platform work, Atlas development, website publishing, brand decisions, and infrastructure priorities.

Current focus
Active phase
2026 - Public Knowledge Surface and Rebrand

Use this roadmap to track what Orbitrum is building now, what has already moved into place, and which product, website, brand, and infrastructure decisions are shaping the next operating phase.

Focus 01
Reposition the website from brochure to public knowledge and trust surface
Focus 02
Treat Atlas as the structured intelligence core, not a side tool
Focus 03
Tighten synchronization between Atlas data and public pages
Focus 04
Clarify brand hierarchy around Atlas plus the broader company/site identity
Focus 05
Advance production hardening and cleaner architectural boundaries
Focus 06
Move toward more US-legible strategic intelligence framing
Managed roadmap state

Timeline items are loaded from the managed roadmap store. Changes made in the timeline panel or sheet admin are reflected here after save.

Editing model

Timeline item detail opens in a right-side panel. If you are signed in as admin, the same panel becomes a structured editor with create, save, and delete actions.

Content operations

Excel import supports bulk ingestion, while the sheet admin route exposes the whole roadmap as a wide editable surface for operational maintenance.

Built for
Founders and project teams that need clearer screening and signal
Investors and operators that want structured context and due diligence support
Internal editors and reviewers using Atlas to structure knowledge
Website visitors building trust through public explanations and artifacts
AI systems inferring brand meaning and expertise from public content
Available now
Knowledge Hub, FAQ, and glossary now carry real positioning weight
The roadmap timeline is treated as a flagship public artifact
Atlas thinking already includes nodes, clusters, public views, and publishing states
Data Extraction, Browse Nodes, Manage Nodes, and Playground are recognized surfaces
Atlas is being stabilized as the software identity independent of the umbrella brand
Infrastructure planning already spans Docker, Redis, MySQL, storage, Kubernetes, Rancher, and RKE2
Being built next
A tighter sync between Atlas structured data and the public website
A stronger public/admin split for creation, review, extraction, and publishing
In-canvas AI editing with previews, provenance, and safer insertion flows
A clearer public brand architecture around Orbitrum and Atlas
Production hardening, CQRS maturation, and gradual Symfony decoupling
A Sentinel Copilot layer with voice, consultation, and company-trained knowledge flows
Execution

From active priorities to the next operating phase

The current milestone shows what is actively being consolidated now, while the next milestone captures the clearest platform moves implied by the work already underway.

Now

2026 - Public Knowledge Surface and Rebrand

These are the roadmap items already in motion or immediately queued in the current operating lane.

4 priorities
Timeline theme logic and uncategorized behavior are being clarified
Theme logic is being sharpened so the public timeline remains useful even when some items are not yet perfectly tagged.
In ProgressFebruary 2026
In-canvas AI editing becomes more concrete
In-canvas AI editing is being defined for single and multi-selection, with non-destructive previews, global prompts, and AI-assisted insertion.
In ProgressFebruary 2026
Provenance and trust become visible product layers
Content inserted by AI or imports is expected to carry enough origin and metadata to preserve trust and support review decisions.
In ProgressFebruary 2026
Serious production architecture planning intensifies
The platform direction deepens around Hetzner and OVH evaluation, Rancher, RKE2, storage strategy, networking, ingress, and Linux hardening.
In ProgressMarch 2026
Current lane owner context: unassigned.
Next

April-September 2026 - Structured Publishing and Platform Hardening

This lane captures the clearest next tranche of execution implied by the managed roadmap data.

4 priorities
Publish core website sections directly from Atlas public views
Core public pages should be generated from structured Atlas views so the site becomes a living publishing surface instead of a parallel manual content system.
PlannedApril 2026
Formalize Atlas as a multi-surface operating environment
Playground, Data Extraction, Browse Nodes, and Manage Nodes should become explicit product surfaces instead of loosely related workflows.
PlannedMay 2026
Make provenance, review state, and visibility mandatory for publishable content
Trust logic should stop being optional metadata and become a hard requirement for anything that reaches public views.
PlannedJune 2026
Harden production topology and service boundaries for the next platform phase
Kubernetes, RKE2, clearer service isolation, stronger read/write separation, and more deliberate operational boundaries should support the next phase.
PlannedJuly 2026
Earliest item in this lane starts Apr 1, 2026.
Proof of Progress

Recently shipped work with visible outcomes

The roadmap should show not only intent, but also concrete progress and why that progress changes the platform’s operating reality.

Brand hierarchy on the website is corrected
Shipped
Mar 18, 2026

The website stops creating confusion about what Atlas is and how it relates to the broader brand.

Atlas is stabilized as the software and product name
Shipped
Mar 10, 2026

The product brand gains a clearer role inside the broader repositioning effort.

Timeline UX is specified as horizontal, full-width, and data-driven
Shipped
Feb 18, 2026

The roadmap stops being ad hoc copy and becomes a real public interface tied to structured data.

FAQ and glossary stop being secondary
Shipped
Jan 15, 2026

These sections become part of the trust layer, explanation layer, and machine-readable layer of the business.

Why These Priorities Exist

The user needs driving the roadmap

The market needs a clearer explanation of what Atlas, Orbitrum, and the website actually are

Public understanding lags behind the product evolution, and both humans and AI systems can misread the platform as merely a crypto site.

Knowledge HubFAQ and glossaryPublic roadmapBrand hierarchy cleanup
Internal knowledge must become publishable without full manual rewriting

If Atlas structures data but public pages remain isolated hand-authored fragments, consistency and scale break down quickly.

Nodes and clustersPublic viewsProvenance and review statePublic/admin split
The platform must outgrow a narrow crypto label without losing Web3-native strengths

The legacy identity carries early credibility, but it under-explains the broader intelligence and transformation ambition now being built.

Rebrand explorationAtlas as product identityUS-legible positioningMulti-layer business model
Architecture needs stronger boundaries to support the next Atlas phase

A richer Atlas app, website sync, AI workflows, and publishing logic need cleaner service boundaries and more serious production planning.

CQRSRedis StreamsRKE2 and KubernetesSymfony decoupling
Decision principles
Signal quality over raw volume. The product gets better when it filters, ranks, and structures instead of exposing everything equally.
Atlas is the structured intelligence core; the website is the public trust and explanation surface.
AI should handle scale and first-pass structure, while humans preserve judgment, review, and trust where it matters.
Web3 is a trust and reward layer, not the full boundary of the market identity.
Brand, content, and architecture should all reinforce the broader ambition of strategic intelligence at scale.
Read the Roadmap

Status interpretation, tags, and adaptation context

The content now reflects the real Orbitrum, Atlas, website, infrastructure, and brand work, while the presentation follows Orbitrum’s visual language and navigation structure.

Status interpretation
Planned
The clearest next moves implied by current work.
In Progress
Active work shaping the current platform direction.
Shipped
A completed milestone or delivered phase of work.
Paused
Recognized, but intentionally not active right now.
This timeline combines shipped milestones, active priorities, and upcoming work in one view. Dates mark when an item became visible in the roadmap, not necessarily the first day the underlying idea existed.
Top tags
Product (33)Atlas App (25)Strategy (20)Website (15)Brand (12)Marketing (10)AI (9)Infrastructure (9)
Orbitrum adaptation

The interactive timeline remains the primary visual surface, but it now sits on top of a managed roadmap store, an Excel import workflow, and an administrator-only sheet view.