The public roadmap should clarify direction, not expose an internal backlog. This page groups the work by operating tracks so you can see what is being tightened now, what expands next, and what is still exploratory.
We publish themes and operating outcomes instead of a feature-by-feature ticket sequence.
Identity, platform, workplace, security, and AI are easier to scan than a long chronological ledger.
Partner pull, reliability work, and regulatory pressure can move themes between horizons without notice.
A public roadmap should read like a map, not a changelog.
Use the track filter to collapse the board into one product family without losing the horizon grouping.
Showing all 9 workstreams
This filter currently hides every group. Switch back to all tracks or pick a broader product family.
Short-cycle work around the systems every Altovar product depends on before anything broader ships.
Reduce friction between sign-in, tenant setup, policy, and audit workflows so the whole stack behaves more like one coherent control surface.
Billing, provisioning, lifecycle, and ownership handoff are being tightened so platform products feel less like separate modules and more like one operating system.
Documents, messaging, and calendar are being treated as one daily-use layer, with emphasis on predictability before additional breadth.
Themes that broaden the suite once the shared control layer is stable enough to carry them cleanly.
Compute, storage, networking, and observability are being grouped into a cleaner public offer with more explicit boundaries between self-serve and managed work.
Review, approval, sharing, and collaboration patterns are being expanded where documents, storage, and communication tools overlap the most.
Evidence, policy, and control mapping are being shaped into a clearer operational layer for regulated teams that need security posture to be explainable.
This lane is intentionally less precise. These are the bets we are validating, not release promises.
Automation is being evaluated where it can reduce operator overhead without removing human control, auditability, or predictable failure modes.
Endpoint, telemetry, and response capabilities are being shaped into a more unified EU-operable security layer rather than a collection of isolated tools.
Installer, archive, and companion utilities remain in validation. Only clusters with clear operational fit graduate into the active lanes above.
The public roadmap stays intentionally directional. High-signal customer and partner feedback is what moves themes between lanes.
SHARE FEEDBACK →