Three waves, six weeks, one platform
If you run N-able N-central, the last six weeks have been a bad time to sleep. Between August and September 2026, N-central was hit by three distinct waves of critical vulnerabilities. The latest, CVE-2026-86218, is a CVSS 10.0 pre-auth remote code execution flaw. Huntress confirmed it was being actively exploited, and Shadowserver tracked nearly 1,500 internet-exposed N-central servers, each one a potential lateral path into every client network under management.
That last part is the part that should keep you up. This is not one advisory. It is a cadence. Three waves in six weeks is a pattern, and patching under that kind of pressure is its own risk. Miss one window during a busy month-end run and the blast radius is your whole book.
The real problem is the shared blast radius
Here is the uncomfortable question owner to owner: when your monitoring console is compromised, what else does that login touch? For a lot of MSPs, the answer is everything. Tickets, contracts, time, client contacts, billing. When your PSA and your RMM sit behind the same all-in-one platform, a monitoring-console zero-day is not a monitoring problem. It is a business-continuity problem.
That is not a knock on any single vendor patching hard. It is the architecture. One internet-facing surface, one login, one very good day for an attacker.
We don’t do RMM. That’s the point.
Opentra is a PSA, on purpose. We do not do monitoring, and we never will. Your RMM stays yours: Level.io, ScreenConnect, NinjaOne, whatever you already trust. Their alerts ingest into Opentra as billable tickets, so nothing about your workflow gets slower. See integrations for what plugs in today.
The difference is separation. Opentra is self-hosted and single-tenant. Your client book lives on infrastructure you control, not in a shared cloud console that becomes a headline. A zero-day storm in your monitoring stack never becomes the path into your PSA. Two systems, two surfaces, two very different bad days.
Ownership is the security story
Self-hosted single-tenant is not a slogan. It means your data is not co-located with hundreds of other MSPs behind one vendor login. It means you decide your patch cadence, your exposure, your export. Read the details on security.
And flat pricing across every tier means separation costs you nothing per head: Community is free to self-host, Pro is $149/mo, Opentra Cloud is $249/mo, all unlimited techs and client orgs.
Separate the systems that run your shop from the systems that watch your clients. When the next wave lands, your book is not in the blast radius.
Check what flat, single-tenant PSA actually costs on the pricing calculator, or request early access.