Trust center
How we run the control plane
Paid plans include a 24h business support posture. Availability of your databases is still your operational responsibility the Executor sits in your network. This page covers how we operate Migratrix itself.
Monitoring
Signals, on-call, and what we will not put in a log
Telemetry
Application, Executor, and infrastructure logs with centralized aggregation and defined retention limits.
Alerting
On-call rotations with thresholds for availability, error rates, and security events.
Privacy in ops
Logs exclude customer secrets and sensitive payloads by design.
Support
Business-hours response with a 24h target on paid plans, as described on Plans. A contractual uptime SLA for the control plane is confirmed in the order form, not inferred from this page.
Incidents
When something breaks on our side
| Practice | What we do |
|---|---|
| Runbooks | Defined severity levels, roles, and communication channels. |
| Customer notification | Affected customers are notified without undue delay if a data incident is confirmed. |
| Post-mortems | Corrective actions and prevention steps are documented after incidents. |
| Backups | Encrypted automated backups of control-plane data, with multi-AZ coverage where applicable. |