Network Automation for MSPs and Managed Service Providers
An MSP runs other people's networks for a living, which means the platform has to survive two audits at once — your client's and your own. OrcaMonitor gives each customer a dedicated environment rather than a shared multi-tenant database, runs on a co-branded domain you control, and puts an approval gate in front of every change so your engineers and your clients can both see who authorised what.
Problems we solve
- Client isolation that a single shared database cannot demonstrate
- NOC engineers making changes on client devices with no approval record
- Monitoring costs that scale badly as you add customers and devices
- Client-specific tooling sprawl — one console per customer per brand
- Onboarding a new client taking days of agent and firewall work
Built for service providers
- Dedicated environment per customer, not a shared tenant DB
- Co-branded custom domain (monitor.yourdomain.com)
- Per-device pricing with a floor, so small clients still work
- Approval-gated changes with named approver per client
- Outbound-only connect — typical client sites need no inbound rules
Capabilities
Dedicated environment per customer
Each customer runs in its own isolated environment rather than sharing a multi-tenant database. That is the architecture answer when a client's security review asks how their telemetry and device credentials are separated from your other customers'.
Co-branded on your own domain
Serve the platform from a partner hostname — monitor.yourdomain.com pointed at us — so clients log in to your brand rather than a third-party subdomain you do not control.
Per-device economics
Pricing follows device count with a floor, so adding a small client does not mean buying a full enterprise tier. Your margin per client stays predictable as the book of business grows.
Approval gates your NOC can defend
Every mutating action on a client device is proposed, approved and recorded against a named engineer. When a client asks who changed a firewall rule at 2am, the answer is a record, not a recollection.
Fast client onboarding
The secure connect agent dials out, so typical client sites need no inbound firewall changes — the step that usually turns onboarding into a change request against the client's own network.
Related solutions
FAQ
Can an MSP resell OrcaMonitor to its clients?
Yes. OrcaMonitor supports a partner/MSP mode with a co-branded custom domain, so clients access the platform on your hostname, and each customer runs in a dedicated environment rather than sharing a multi-tenant database. Talk to us about the partner model and per-client pricing before you quote.
How is client data isolated between customers?
Each customer gets its own dedicated environment rather than a shared multi-tenant database, and network connectivity is scoped per customer. That separation is a design choice with a real cost, and it is the one most client security reviews actually ask about.
How does pricing work for an MSP with many small clients?
Pricing is per device with a floor rather than one enterprise licence per client, which is what makes small clients commercially viable. Confirm current bands with us when you model your margins, since the floor and bands are configuration rather than fixed.
Will my engineers be able to make changes without approval?
Only where you deliberately allow it. Every mutating action is approval-gated by default, and low-risk playbooks can be graduated to auto-approved per device group once they have a track record. Either way the action is logged against a named engineer, which is what protects you in a client dispute.
Does onboarding a client require firewall changes on their network?
In typical setups no. The secure connect agent initiates an outbound-only encrypted connection, so no inbound ports need opening at the client site — which removes the slowest step in most MSP onboarding projects.
See every module, pricing tier, and deployment option on the OrcaMonitor overview.