Pillar · MSP
Multi-tenant from the first commit.
OpsLantern was designed around the MSP operating model — not bolted on. Customers, sites, and devices are first-class. Isolation is at the data layer, not just the UI.
Isolation
Tenant model that holds up to audit.
Organization → Customer → Site → Device
Natural hierarchy, queryable at any level, inheritable defaults.
Row-level security
Enforced in the database, not in the application layer. A bug in code cannot leak across tenants.
Per-customer overrides
Runbooks, monitors, hardening policies, maintenance windows, and approvers inherit then override.
Engineer productivity
One engineer, hundreds of servers.
Global command palette
"restart iis on web01.customerY" → executes. Typing beats clicking at fleet scale.
My queue
Tickets + scheduled changes + alerts, filtered to the customers you own.
Context switcher
One click swaps the whole UI to a customer's scope — credentials, runbooks, inventory.
Shift handoff builder
Auto-generated from session logs. No more "who was working on this overnight?"
Customer-facing
Deliverables your customers actually read.
White-labeled status page
One per customer. Real-time uptime, active incidents, upcoming maintenance.
Monthly report
SLA, incidents, changes, patches, capacity trends. Branded. Generated automatically.
Customer approvals
Change requests approved in-app by your customer — no more email threads.
Billable-time rollup
Engineer time per customer, per action category. Feeds your PSA.
License lifecycle
VMware cores, Windows CALs, SQL CALs, Plesk, cPanel, Acronis, FortiMail — renewals, utilization, savings.
EOL / EOS tracker
Pre-seeded database for every OS, hypervisor, DB, appliance firmware — plus hardware warranty via vendor APIs.