Public Launch
Q2 2026
April to June 2026
Public Roadmap
This page reflects our current product timeline. Public launch is targeted for Q2 2026, followed by the next planned delivery windows through Q1 2027.
These dates are planning targets, and we will keep this page updated as the roadmap evolves.
Public Launch
Q2 2026
April to June 2026
Monitoring Expansion
Q3 2026
July to September 2026
Broader Coverage
Q4 2026
October to December 2026
Platform Depth
Q1 2027
January to March 2027
Updated Timeline
The cards below show the current quarterly plan for launch and the next phases of platform expansion.
Q2 2026
April to June 2026
Deliver a credible public launch with the first wave of monitoring products, practical integrations, and a platform foundation we can support with confidence.
Focus the initial public release on a smaller, supportable scope rather than trying to ship the entire roadmap at once.
Bring proactive certificate tracking and alerting into the public release so teams can catch expirations and misconfigurations before they become incidents.
Deliver domain-status tracking and alerting to give operations teams clearer visibility into an important layer of external reliability.
Add DNS visibility and alerting so teams can quickly detect misroutes, stale records, and resolution issues that impact availability.
Ship the first public CLI so operators and developers can work with Bitaic from the terminal in faster, scriptable workflows.
Launch integrations for Webhooks, Microsoft Teams, Slack, and PagerDuty so alerts can land in the systems teams already use to coordinate work.
Q3 2026
July to September 2026
Expand beyond the initial release with broader service coverage and foundational trust work for customers who need stronger operational maturity.
Add endpoint and availability monitoring for websites and network targets so teams can detect service interruptions faster.
Introduce Windows host health visibility for CPU, storage, memory, and other operational signals needed to manage server performance.
Continue the process toward SOC 1 Type I as part of building a stronger operational and trust posture for customers evaluating Bitaic seriously.
Q4 2026
October to December 2026
Broaden infrastructure visibility so Bitaic becomes useful across more day-to-day operator workflows instead of serving only a narrow monitoring slice.
Track important server processes in real time so teams can spot unstable, unhealthy, or resource-intensive workloads earlier.
Expand into network-level visibility so teams can troubleshoot connectivity, latency, and bandwidth issues from inside the same platform.
Add Mac system monitoring for environments that need visibility into macOS infrastructure alongside servers and cloud services.
Q1 2027
January to March 2027
Push deeper into platform coverage with event visibility and broader operating-system support as the product matures beyond the initial release footprint.
Centralize collection, alerting, and operational review of Windows events so teams can react faster to system-level issues.
Extend host-health support to Linux systems with deeper operational metrics for the environments most teams rely on in production.
We expect this plan to keep evolving. As milestones move or expand, we will refresh this page so the published timeline stays current.
This roadmap reflects our current best judgment, but we still want direct customer input on what should move up, what should wait, and which launch gaps would block adoption.
If you have suggestions or want to get involved, email support@bitaic.com.