Ngentix Enterprise

It doesn't just find the problem. It fixes it, and proves it.

Most fleet tools stop at the dashboard: they show you what is wrong and hand you the work. The control plane, paired with the engine in each client environment, is action-based — you propose a fix, approve it, and it runs, across one tenant or the whole fleet. Then it hands you the receipt.

Observability without action is half a product.

A dashboard that lights up red points at a problem you still have to solve by hand, tenant by tenant, in the native tool. And when the client asks did you actually do it, and can you show me — the honest answer is a screenshot and a promise.

RMM and PSA track your tickets. They do not run the fix, and they do not prove the outcome.

From signal to fix to proof.

Every problem the control plane surfaces carries a fix, and every fix moves through three states you can see.

Lifecycle
Detected A real, typed finding — not a dead-end alert.
Held Waiting for your approval. High-blast-radius actions never auto-run.
Done Run, and on the record with a receipt that links to the outcome.

What the console does.

Findings The console detects real problems — an outdated engine, a flapping connector, a tripped breaker, spend-cap pressure, grant drift. Each finding carries the exact remediation verb that resolves it, so there is no hunting and no context-switch into the native tool.
Actions Apply a release, hit the kill switch, roll a change back, raise the ticket — typed, named procedures invoked from the console. Each engine advertises the actions it can run, and the console will not send one it cannot.
Approval A version change lands as a proposal in a waiting-for-you queue with the exact request, reason and target. You approve, and only then does it deliver. The console never claims a fix it did not make.
Fan-out When a security finding hits many tenants, the console stages one batch and a single approval fans it out per tenant. It reports back honestly: patched 6 of 7; tenant 5 is offline, queued, applies on reconnect.
Receipts Every completed action produces a receipt — the finding it fixed, the prior→new state, who approved it and why, and a live link that opens the outcome in the client's own engine. Hash-chained and tamper-evident, exportable as a one-click evidence pack.

What the rest of the stack leaves on the table.

RMM Surfaces the problem and stops. The fix is still manual work in the native console, tenant by tenant.
PSA Tracks that a fix should happen. It does not run the action and it cannot prove the outcome landed.
Scripting Can act, but leaves no verifiable record tying the change to who approved it and why.

The control plane closes the loop — detect the problem, run the fix from one screen, fleet-wide on one approval, and hand back a hash-chained receipt that links to the real outcome. Observe, act, prove.

Why an MSP buys it.

Revenue Sell managed remediation, not another dashboard — a per-client, per-month service that does the work, priced on outcomes you can prove.
Margin Batch fan-out and one-click approvals turn a night of console-hopping into a single action. More tenants per technician.
Trust The exportable receipt is your QBR evidence and your SOC-2 pack — a deliverable competitors cannot hand over.
Fit Single-tenant engine per client, one multi-tenant console for you. It matches how you already run managed services.
Get early access Or take the one-pager: control plane, two pages (PDF)

Who else this is for