Traditional monitoring project
- Months of tool selection before the first useful picture
- Agents, exporters, and dashboards treated as a programme
- Alerts without an evidence pack or a next step
- SAP credentials often copied into a central tool
Built for people who understand SAP operations.
SAP operations without another monitoring project.
Install. Connect. Monitor.
Your Basis team already knows where to look. BasisPilot brings the signals together so you can monitor the landscape, investigate problems, and act on evidence.
Trial is a placeholder. Signup, verification, and entitlements are not implemented yet.
Command CenterBasisPilot Demo Organization
Open incidents
3
Systems
6
Landscape
Critical
Attention
S4-PROD
No free DIA work processesCritical
S4-PROD · wp_dia_free · sap_work_processS4-PRODCritical2 open · DIA free
HANA-PRODDegraded1 open · HDB yellow
PO-PRODHealthyStable probes
BW-PRODDegraded1 open · BTC queue
QAHealthyStable probes
DEVHealthyStable probes
S4-PROD · DIA free
Same systems as the Interactive DemoOpen demo →
The problem
Monitoring projects take months. Production incidents do not wait.
You already know SM50, SM37, SM21, ST22, SM12, and HANA pressure. You should not need another platform programme before you can see a landscape.
BasisPilot
- Install a connector. Connect a system. Watch the first signals.
- Incidents open from repeated telemetry, not from a workshop
- Explanation, evidence, and catalog citations on the incident
- SAP passwords stay on the customer host
How it starts
Install. Connect. Monitor.
01 INSTALL
Put the connector on a host that can see SAP
Outbound only. SAP credentials never leave that host. No monitoring programme to stand up first.
02 CONNECT
Register the SID
Heartbeat, then identity. Optional read-only discovery. No RFC password in the API.
03 MONITOR
Signals become work
Collectors post observations. Repeated warning or critical samples become incidents you can investigate.
Capabilities
Built around how Basis already works
See the landscape
Health, stale signals, and what is open — in one Command Center, not six transactions.
Incidents, not noise
Repeated warning or critical samples become something you can work. Not another alert storm.
Evidence on the incident
Observations and sibling incidents stay with the problem, so the next person can pick it up.
Notes you already trust
Seeded SAP Notes and SOP matches sit next to the evidence. Citation, not a guess.
Humans stay in control
Advisory next steps need approval. AI does not execute changes in your SAP systems.
Credentials stay put
The outbound connector talks to SAP on your host. Passwords never reach BasisPilot.
Investigation
Don't just detect a problem. Understand it.
A stored evidence pack, a clear explanation, and ranked Notes/SOP citations. Humans approve the next step. Real SAP change stays fail-closed.
AI investigation
A later step — not the public demo
SignalAlertEvidenceInvestigationAI AnalysisProbable CauseRecommended Action
The Interactive Demo walks this sequence with sample copy. It does not call an AI API. AI investigation in a future trial is planned at 5 uses to start, on your systems, after signup.
Security
The connector is the trust boundary
SAP credentials stay customer-side. The API never receives RFC passwords. Read-only first. Governed change is off by default. Authentication for the public SaaS is still planned — we do not claim it here.
Read the security modelPricing preview
Start with a demo. Pay when you run real systems.
Initial offering. May evolve. No payments on this site.
Interactive Demo
Free
Fictional systems. Not a production plan.
Starter
$79
per month · planned
Professional
$249
per month · planned
Service Provider
Contact
MSP / multi-customer