Roadmap  /  What ships next

The path forward.

Field & wireless orchestration. Disaster recovery mode. AI capability expansion. The roadmap is the production backlog: what operators have asked for, what we're building, what we're shipping.

In flightRecently shipped
Operator-drivenQuarterly majorsNo vapourwareSame-day ship across tenants12+ years cadencev3.4 current
In flight & on the horizon

Three major streams currently in development.

Each item is a real backlog entry with an estimated ship window. Roadmap dates are intentions, not contracts; we communicate slips as they happen.

01
Field & wireless orchestration
In flight · ship target Q3 2026

Native orchestration for fixed-wireless ISP operations. WISP equipment provisioning, RF link planning, sector-load aggregation, mounting-tower inventory, and the wireless-specific dispatch flows (line-of-sight verification, signal-target tuning) integrated with the existing fibre-side topology.

  • WISP equipment provisioning (sector radios, point-to-point links)
  • RF link planning with terrain-aware line-of-sight
  • Sector-load aggregation by frequency band
  • Tower / mast inventory with structural maintenance schedule
  • WISP-specific dispatch flows (LoS verification, signal-target)
02
Disaster recovery mode
In flight · ship target Q4 2026

A first-class operational mode for ISPs experiencing major incident events: regional power outages, fibre backbone cuts, datacentre evacuations. The system enters a constrained-operations posture: critical-only billing actions, manual-override on auto-escalations, supervisor-broadcast comms to staff, customer-side status-page integration with auto-update from the incident note.

  • Operational mode toggle for major incidents
  • Critical-only billing (suspension grace, no auto-suspend)
  • Auto-escalation override with supervisor broadcast
  • Status-page integration with auto-update from incident note
  • Per-tenant DR runbook attached to mode-entry transition
03
Aelita capability expansion
Continuous · ongoing

Aelita's eighteen v3 capabilities are the foundation, not the destination. Currently in development: contract-renewal negotiation drafting, network-anomaly detection across multi-OLT pattern correlation, supplier-reliability scoring across RMA history, and an Atlas voice mode for new staff onboarding. Each capability ships when it passes the draft-only safety review and the per-tenant scoping verification.

  • Contract-renewal negotiation drafting (in dev)
  • Multi-OLT anomaly correlation (in dev)
  • Supplier-reliability scoring from RMA history (in dev)
  • Atlas voice mode for new-hire onboarding (research)
  • Capabilities ship when they pass safety + scoping review
How we prioritize

The roadmap is the production backlog.

Three rules for what makes it onto the roadmap. They have not changed since 2014.

01
Real operators ask for it.
Every roadmap item starts as a production note. A NOC engineer hits a wall. A finance clerk says "this should be automatic." A field tech describes the workflow they invented because the system did not support it. We log it, prioritize against the rest, and build.
02
It earns its surface.
If a feature does not pull operational weight (saves a real workflow, prevents a real failure mode, removes a real manual step), it does not ship. ISPCQ is already a substantial codebase; new features add maintenance cost. The bar is operational ROI, not "interesting."
03
It ships across all tenants on the same day.
Per-tenant features are forbidden. If it is not generalisable across the codebase, we either generalise it or we don't build it. Same code, both tenants, same deploy day, every time.