System Availability
Bitaic uses service monitoring, maintenance practices, backup and recovery processes, and incident response to support reliable monitoring workflows. Availability commitments can vary by product, workspace policy, and customer agreement.
Reliability Practices
Platform reliability is handled through operational controls rather than customer-managed hosting steps.
| Practice | How it supports availability |
|---|---|
| Service health monitoring | Bitaic operations teams monitor platform services and investigate customer-impacting degradation or outages. |
| Maintenance controls | Planned maintenance, release validation, and rollback readiness reduce avoidable disruption during platform changes. |
| Backup and recovery processes | Recovery procedures cover restoration, validation, and customer communication for service-impacting events. |
| Incident response | Operational incidents are triaged through support and incident response workflows, with customer updates through approved communication channels. |
Monitoring Continuity
Collection behavior depends on the product because managed checks and installed agents have different failure modes.
| Area | Continuity behavior |
|---|---|
| Managed checks | Certificate, Endpoint, DNS, and Domain Monitoring checks run from Bitaic-managed collectors and report the latest check state, latency, expected-state comparison, or failure reason supported by each product. |
| Installed agents | Private-beta product agents follow beta-specific continuity guidance for enrolled workspaces until Q1 2027 public-release planning. |
| Alert routes | Alerts can route through configured dashboard, integration, API, and webhook workflows. Webhook delivery records follow the published delivery-retention baseline. |
| Unknown or stale data | Product pages define how each monitoring type reports unknown, stale, degraded, unavailable, or recovered states. |
Recovery and Data Protection
Recovery planning works with the shared data-management baseline rather than product-specific storage promises.
- Active monitoring and audit history use the shared retention baseline unless a workspace policy or customer contract sets a different period.
- Stored monitoring, configuration, account/profile, audit, session, token metadata, and integration configuration are protected by managed encryption at rest.
- Deletion requests remove qualifying customer data from active product surfaces after verification and processing. Retained backups age out through the backup lifecycle.
- Exports use approved dashboard or API jobs with least-privilege permissions.
Customer Preparation
Customers can improve monitoring continuity by keeping ownership, access, and escalation paths current.
- Keep Admin ownership current so workspace settings, alert routes, tokens, and integrations can be updated during an incident.
- Use product-specific troubleshooting steps when a check reports stale, degraded, unavailable, unauthorized, or unknown state.
- Keep webhook receivers reachable over HTTPS and review delivery failures before subscriptions are disabled by system protection limits.
- Include recent check IDs, agent IDs, alert IDs, timestamps, and troubleshooting output when opening support requests.