Built for the teams that keep SAP running.
Same platform, four very different audiences. Pick the one that sounds like you.
Managed Service Providers
Operate dozens of customers from one console. Per-tenant data isolation; per-customer SLAs; one bill at the end of the month.
- !Every customer wants their own dashboard but you don't want to run 12 of them.
- !On-call rotates between humans who only know half the landscape.
- !Audit responses cost three days because logs live in seven places.
Multi-tenant by design
Per-customer data isolation enforced at every query. Customers see their landscape; you see all of them.
Customer-scoped alerts
Routing rules, channels, escalation policies — all per customer. The Slack channel for Acme stays the Slack channel for Acme.
Cross-customer automation
Runbooks once, deploy everywhere. SCC5/SCCL batches across customers from one screen.
Audit packs per customer
Filter audit log by customer + date range, export CSV/PDF. SOC2-aligned retention up to 365 days.
In-house Basis teams
A web-based view across SAP systems for SM50, SM37, ST22 and related transactions. Cross-system filtering, drill-down, and an attributed action history.
- !Cross-system queries today mean repeating the same work in SAPGUI on each system.
- !There is no central record of who did what to which SAP system.
- !New team members spend weeks learning the click paths for routine work.
Web-based Basis transactions
SM50, SM37, ST22, DB02, SM21, SM12, SM59, SM04, ST03 in one view across the SAP systems in scope.
Trends and history
Work-process utilisation, job runtimes and dump frequency over time, with threshold-based alerts.
Runbooks and sapcontrol
Codified routine operations: start, stop, restart from the UI. Every action is recorded with operator and source IP.
Live updates
The view refreshes on its own as new data comes in from the agents.
SOC analysts & security teams
A queryable audit trail across the SAP estate with 69-permission RBAC. Service desk gets read-only triage without touching production.
- !When someone asks "who approved that?", the answer takes a day to find.
- !Service desk needs to triage incidents without getting production access.
- !Auth failures across systems are invisible — no central log.
69-permission RBAC
Granular per-tab, per-action, per-role permissions. Six built-in roles plus a marketing-only support_agent role.
365-day audit retention
Every login, role change, token reveal, runbook execution, sapcontrol command. Exportable as CSV/PDF for compliance reviews.
Security Pulse callouts
Failed-login spikes, brute-force patterns, top hostile IPs — surfaced live on the Dashboard and the Audit Logs page.
Read-only service desk
service_desk role sees alerts, incidents, and short dumps — no SAP transaction access, no config changes, no token reveal.
Service-delivery leadership
A scheduled monthly report per customer and a current view of availability across the estate.
- !Monthly reporting takes engineer time that should go elsewhere.
- !Customer SLAs are tracked in spreadsheets with manual entries.
- !There is no single up-to-date view of how the estate is doing right now.
Availability and SLA
Per-system uptime, maintenance windows and SLA credits. The monthly compliance report is a one-click export.
Scheduled reports
Recurring PDF reports per customer covering system count, incidents and alert trends.
Estate-wide view
A consolidated dashboard with per-customer health alongside the underlying signals.
Don't fit any of the boxes?
We've onboarded teams of 2 and teams of 200. Tell us about your shape and we'll figure out whether it's a fit — honest answer, no pressure.