Building in the open: how we're sequencing Nexus from Foundation to GA

It would be easy to write a feature list for Nexus that reads like every other RMM/PSA landing page — dozens of capabilities, all "available," most of them thin. We'd rather do the slower, less flattering thing: build a smaller number of modules completely, tell you exactly which phase we're in, and only claim something ships once the real path behind it — not just a convincing demo — actually exists.

The four phases

• Foundation — the multi-tenant core every module depends on: authentication, tenant isolation, encrypted secrets, outbound-only monitoring. Done first, because nothing above it is trustworthy without it.
• Core modules — helpdesk, assets, network monitoring, security suite, compliance, client/staff portal, and the agentic AI layer across all of them. Where we are now.
• Private beta — a small set of design partners running Nexus against real workloads, where AI capabilities graduate from "in development" to "live" one at a time, each only after it earns it.
• General availability — open signup, full documentation, SLA-backed support.

The full detail — what's shipped, what's in progress, and what each phase includes — lives on the roadmap page, and we update it by hand as things actually move, not on a marketing schedule.

A module is done when the real path is wired and tested — not when the sample data renders.

That standard applies to us as much as it does to the software: this blog won't carry a customer case study until there's a real customer willing to be named, and it won't claim an AI capability is live until it's live. If that means this site occasionally reads as more honest than exciting, that's the trade we're making on purpose.