Architecture
Bitaic combines managed checks, installed agents, customer-facing surfaces, processing, storage, and alert delivery in one monitoring workspace. This page describes how those pieces fit together for the scheduled public release products. Private-beta agent-backed products remain documented separately until Q1 2027 public-release planning.
Architecture Surfaces
| Surface | Role |
|---|---|
| Bitaic App | Web interface for setup, dashboards, alert review, historical views, exports, and administration. |
| Bitaic CLI | Local setup and diagnostics surface for installing agents, checking agent state, and retrieving selected status or metric data. |
| Bitaic API | Workspace-scoped REST API for automation, configuration, metric retrieval, exports, integrations, and webhook administration. |
| Managed checks | Bitaic-managed collection for Certificate Monitoring, Endpoint Monitoring, DNS Monitoring, and Domain Monitoring. |
| Installed agents | Private-beta product collection for enrolled workspaces, with setup and runtime details kept in beta-specific documentation. |
| Processing and storage | Normalizes product-specific results, evaluates thresholds or expected-state rules, updates status and alert state, and retains monitoring history. |
Collection Model
| Product | Collection model | Primary data |
|---|---|---|
| Certificate Monitoring | Bitaic-managed HTTPS certificate checks. | Certificate expiration, chain health, hostname coverage, issuer metadata, and diagnostic TLS details. |
| Domain Monitoring | Bitaic-managed registry and delegation checks. | Expiration state, registrar metadata, nameservers, DNSSEC state, registrar-lock state, and expected-state drift. |
| DNS Monitoring | Bitaic-managed resolver and optional authoritative checks. | DNS answers, lookup state, latency, TTL, DNSSEC validation state, and propagation comparison. |
| Endpoint Monitoring | Bitaic-managed HTTP and HTTPS availability checks. | Availability state, response time, redirect handling, status-code results, and alert state. |
Private beta products
Health Monitoring and Windows Event Monitoring remain private beta only until Q1 2027 public-release planning. Detailed collection models, agent behavior, and API fields stay in beta-specific documentation until public-release planning begins.
Data Flow
- Configure: Users create targets, checks, thresholds, expected states, alert routes, and integrations in the Bitaic App, API, or supported CLI workflows.
- Collect: Managed checks run from Bitaic-controlled collectors. Private-beta agent collection is documented separately for enrolled workspaces.
- Transmit: User, API, webhook, agent, and service traffic uses TLS in transit. Installed agents use outbound HTTPS and product-specific local buffers during temporary egress loss.
- Process: Bitaic normalizes check results, evaluates configured thresholds or expected states, updates monitored-resource status, and creates or updates alerts.
- Display and retain: Current state, historical views, audit records, and exports are available according to workspace permissions and the shared data-management baseline.
- Deliver: Alerts and operational events can route to configured notification paths, integrations, and webhooks.
Architecture Boundaries
| Boundary | Docs guidance |
|---|---|
| Product behavior | Product pages define the exact status labels, collection cadence, thresholds, filters, and troubleshooting steps for each monitoring type. |
| Availability | The availability page describes reliability practices and customer preparation. Contract-specific commitments belong in customer agreements. |
| Deployment topology | Public product docs describe customer-facing platform behavior, not internal hosting topology or docs-site deployment details. |
| Security and data controls | Security, compliance, privacy, audit, session, and data-management pages define the shared control baseline. |
Security by Design
Bitaic's architecture uses the shared platform/security baseline for transport security, managed encryption at rest, workspace access, auditability, and session controls.
| Area | Architecture baseline |
|---|---|
| Transport | User, API, webhook, agent, and service traffic uses TLS in transit. |
| Storage | Stored customer monitoring data, configuration data, account/profile data, audit records, session records, token metadata, and integration configuration are protected by managed encryption at rest. |
| Access | Workspace access uses Viewer, Operator, and Admin roles, explicit API scopes, and separate local host permissions for agent operations. |
| Audit and sessions | Audit records cover security and administrative activity. Sessions support inactivity expiration, manual logout, Admin revocation, and session/device review. |