Roadmap
What is built, and what is next.
We are preparing beta access. This page gathers, in one list, what the rest of the site says about where each capability stands — so you can see the whole picture without reading twelve product pages to assemble it.
There are no dates here, on purpose. We would rather tell you the order things are being built in than give you a quarter we would have to walk back. If a date matters to your decision, ask us and you will get our honest current estimate, in writing, with its uncertainty attached.
Implemented in the product
7 capabilitiesBuilt capabilities. Availability depends on the beta environment and its configuration.
-
Error monitoring
ImplementedGrouped exceptions, stack traces, breadcrumbs and release attribution.
Read more -
Performance and product analytics
ImplementedConnect traces, sessions, active users and feature adoption in one project.
Read more -
Product Health
ImplementedFeature health per feature, and one ranked list of issues, latency regressions and underused features.
Read more -
Feature flags
ImplementedEnvironment-specific configuration, gradual rollouts and local evaluation in .NET.
Read more -
Uptime monitoring
ImplementedHTTP checks, confirmed incidents and TLS certificate expiry warnings.
Read more -
AI analysis
ImplementedInvestigate evidence with your own model key and a configured budget.
Read more -
SDK packages
ImplementedSDKs published as release candidates (0.1.0-rc.2) on NuGet and npm, for .NET, browser JavaScript, React and React Native.
Read more
Before wider access
3 capabilitiesOnboarding, operational and commercial work still to complete.
-
Beta onboarding
Final access arrangements, operational readiness and applicable terms before wider availability.
Read more -
AI repository writing
The implementation remains disabled pending operational verification. Human approval will be required when enabled.
Read more -
Paid subscriptions
Pricing and billing must be finalised before paid access is offered.
Read more
Want to influence the order?
The ordering above is a judgement, not a law. If something further down the list is what would make ErrorDock usable for you, that is worth knowing — a specific reason from a real team moves things far more reliably than a vote count.