Solution · By Sector

Run many customers on one platform

Providers need one console for many customers without letting them see each other. Unified360 is built multi-tenant: every target, rule, contact, dashboard and report belongs to a customer, and customer-scoped users see only their own, while your team sees them all.

  • Isolatedper customer
  • Distributedproxy servers
  • Accountableaudited access
What is the provider facing?Pick a scenario · sample data
  1. Customer isolationTenants, scoped users and per-customer views
  2. Network and linksCircuits, switches, firewalls and wireless
  3. Compute and virtualizationServers, hypervisors, storage and databases
  4. Service desk and vendorsTickets, SLAs, contracts and vendor escalation
  5. Access and auditVaulted access and recorded sessions
Illustrative example. Rules and settings are configured per environment.

The problem

Providers scale by sharing, and sharing is risky

The economics need one platform, and the contracts need strict separation.

01

Mixed up

One tool for many customers, with no clean separation between their data.

02

Blind at the edge

Customer sites reach you over links you can't see into.

03

Answerable

Technicians touch customer systems, and you must show who did what.

Where it goes wrong

Six gaps, and how each one is closed

No tenant boundary

How it goes wrongData from different customers sits together.

Closed withEvery resource is scoped to a customer, with per-customer views and a customer-locked filter for scoped users.

Circuits with no evidence

How it goes wrongA carrier disputes an outage and you have no data.

Closed withLink monitoring with circuit ID, vendor, provisioned bandwidth and committed uptime.

Sites you can't reach

How it goes wrongCustomer sites sit behind their own firewalls.

Closed withProxy servers and site agents report into one console.

Contracts and vendors off to the side

How it goes wrongVendor delays are handled by email.

Closed withITDesk vendor escalation with acknowledge and resolve tracking, and contract management with expiry alerts.

Technician access unaccounted for

How it goes wrongShared credentials on customer systems.

Closed withSecurita360: vault, approvals, command control and recorded sessions.

Reporting by hand

How it goes wrongMonthly customer reports built from exports.

Closed withScheduled reports in PDF, per customer, with a customer filter on dashboards and reports.

Provider types

Where providers use it

Pick a provider type to see what it typically needs and which capabilities match.

Cloud and data-centre providers

Hosting compute for customers.

  • HypervisorsVMware, Proxmox, Nutanix
  • ServersWindows and Linux
  • DatabasesFour engines
  • HardwareiDRAC and iLO
  • Customer scopingEvery target and rule
  • Capacity alertsDatastores and pools
Customer scoping applies across monitoring targets, alert rules, contacts, dashboards and reports.

Capabilities listed are what the products do today. No provider customers are named on this page.

What changes

When many customers share one platform safely

Customers kept apart

Data is scoped to each customer, and users see only theirs.

Circuits with proof

Measured quality sits beside the committed uptime.

Access on record

Every technician session is approved and recorded.

Reports on a schedule

Per-customer reports arrive without manual exports.

Questions

Frequently asked

How is customer data separated?

Every monitoring target, alert rule, contact, dashboard and report belongs to a customer. Customer-scoped users see only their own customer's data, and the filter is locked. Admins without a customer assignment can see every tenant.

Can customers log in themselves?

Customer-scoped users can be given roles that limit them to their own customer's data and views.

How do remote customer sites report?

A monitoring agent at the site collects data and proxy servers report it back to one console.

Can we track carrier circuits?

Yes. Link monitoring records circuit ID, vendor, provisioned bandwidth and committed uptime, and measures latency, jitter, loss and utilization.

Does it do billing?

No. Billing and quoting aren't part of the products today.

Which providers use it?

No provider customers are named here. This page describes what the products do.

See it for your services

Talk to us about your customers

Tell us how you serve customers and we'll show you how the platforms fit. No commitment required.