Public roadmap
A curated view of customer outcomes taking shape now, the commitments that follow, and the product direction connecting them. It is intentionally selective and is not a release calendar.
Now
Customer-facing initiatives in active development.
Next
Committed product outcomes following the current work.
Direction
Specific product areas for longer-term investment.
Reviewed July 2026. Priorities may change with customer insight and what the work reveals.
Now
Customer-facing initiatives with active work behind them. Each one describes the product experience taking shape.
Monitors adapt as applications change without losing sight of what they are meant to verify. The agent uses intent, check code, configuration, and failure evidence to separate a real incident from monitoring drift, then proposes an auditable repair.
Expected impact
Self-healing spans monitor types, from Playwright workflows to API assertions and other monitoring logic, with Playwright as the richest repair surface.
Usage comes together in one trustworthy view across accounts, checks, time, and meter types, available both in Checkly and programmatically.
Expected impact
Teams can understand how usage grows, allocate it across their organization, and plan confidently.
Projects become visible in the Checkly UI so teams can see what each project manages, understand its deployment context, and reconcile changes made in the UI with code.
Expected impact
Ownership becomes explicit and reversible, so teams can move between UI and code without hidden bindings or one-way doors.
Browser Checks and Playwright Check Suites converge into one path that starts with a fast, focused monitor and grows into advanced Playwright capabilities.
Expected impact
Teams keep simple authoring when it is enough and add advanced configuration, dependencies, retries, artifacts, and suite management as they need them.
Next
The outcomes are committed; exact implementations may evolve as the work develops.
Projected usage, timely notifications, and explicit budget controls make upcoming consumption and spend visible throughout the billing cycle.
Expected impact
Teams can act before an overage and choose clear limits with the monitoring trade-offs explained up front.
Monitor changes flow from Checkly back to GitHub as reviewable pull requests, whether initiated by a person in the web app or by the self-healing agent.
Expected impact
Monitoring changes stay connected to the repository, with a clear diff, code review, CI feedback, and an auditable path to deployment.
A focused on-call rotation experience lets teams define schedules and see who is responsible now and next.
Expected impact
Teams get a clear, lightweight foundation for incident ownership and the response workflows that follow.
Direction
Longer-term product investment centers on enterprise access, reliability expertise, alerting and incident control, and Playwright in production.
The goal is organization-level access: SCIM-provisioned users, identity-provider groups mapped to Checkly teams, and precise permissions applied consistently across accounts.
The Checkly reliability agent should be available through the web app and Slack, while MCP and Agent Skills equip developers’ own agents with the same monitoring context and expertise.
Richer signals, thresholds, time windows, priorities, and routing give teams finer control over when Checkly alerts, who gets notified, and when incident automation acts.
Live execution progress and logs, richer result views, and better suite-level insights make Playwright checks faster to understand and debug in production.
Have a feature request?
This roadmap stays selective. Use the feature-request board to propose an idea, add context, and vote on requests from other Checkly users.