Errors with answers
Group repeated exceptions, inspect stack traces and breadcrumbs, and catch an issue when it returns.
ExplorePRODUCT RELIABILITY, IN CONTEXT
Find the error.
Understand
the impact.
Connect what breaks with what people actually use. Errors, performance and product analytics in one place, so you know what to fix next.
Built for web, mobile and .NET desktop applications.
Have a beta access code? Create your account.
ErrorDock / Acmeproduction · v2.8.4Product overview
A clear view of what needs attention.
Active users12,804↑ 8.4% this week
Crash-free sessions99.2%Across all releases
Affected users843 issues to investigate
Activity & errors● Sessions ● Errors
Checkout failedNullReferenceException · CheckoutService.cs:142
62 users ↗Payment request timed outTaskCanceledException · PaymentClient.cs:88
17 users ↗Inventory query failedSqlException · InventoryRepository.cs:61
5 users ↗Product illustration · sample data
01 / A connected view
Every signal.
The same story.
Move from an exception to the experience behind it. Keep the context that gets lost between separate tools.
Performance in context
Follow a slow request through its trace. See the operations behind the latency and the release it belongs to.
ExploreUsage that means something
Understand active users, sessions and feature adoption alongside the problems those users encounter.
ExplorePriorities with perspective
Feature health shows each feature’s adoption, errors and latency. Priorities ranks what to fix first in one list that explains every row.
ExploreMore deliberate rollouts
Control feature flags per environment, roll out gradually and compare the health of exposed cohorts.
ExploreAvailability from outside
Check your endpoints, track confirmed outages and watch certificate expiry alongside application health.
Explore02 / Context before guesswork
A stack trace tells you what.
A session tells you why it matters.
See the path to the failure: the feature they opened, the action they took and the exception that stopped them.
One project connects the issue, session, release and trace. Follow the evidence without rebuilding the story by hand.
Follow a session →Opened the application
release v2.8.4 · web
Viewed the cart
page_view · /cart
Applied a discount
interaction · checkout.apply_discount
NullReferenceException
CheckoutService.ApplyDiscount · line 142
03 / An informed next step
A second set of eyes.
You stay in control.
Investigate an issue with AI grounded in the error, breadcrumbs and repository context. Bring your own model key and set the budget.
Inside the AI workflow ↗Repository writing is not enabled in the current beta setup.
01 Gather the relevant evidence
02 Explain the likely cause
03 Review a proposed change
04 Keep the decision with your team
04 / Built for your stack
A small integration.
A much clearer picture.
Start with errors. Add the features and interactions that matter to your application as you go.
The SDKs are published as release candidates on NuGet and npm. Pin version 0.1.0-rc.2 when you install, and send telemetry to https://api.errordock.com.
Explore SDK guides →.NET
dotnet add package ErrorDock.AspNetCore --version 0.1.0-rc.2JavaScript
npm install @errordock/core@0.1.0-rc.2 @errordock/browser@0.1.0-rc.2React
npm install @errordock/core@0.1.0-rc.2 @errordock/browser@0.1.0-rc.2 @errordock/react@0.1.0-rc.2Release candidates · pinned to 0.1.0-rc.2, because npm’s latest tag still points at rc.1
A few things to know
Common questions.
What makes ErrorDock different?
Errors and product usage share the same project. Read an exception alongside its session, feature and release, so you can judge the effect on your users before choosing what to fix.
Which platforms can I connect?
The SDKs support .NET, including ASP.NET Core, WPF and WinForms, JavaScript in the browser, React and React Native. They are published as release candidates (0.1.0-rc.2) on NuGet and npm.
Does it record my users' screens?
No. Sessions are event timelines, not screen recordings. They connect page views, named interactions and errors. You choose what to instrument and what user identity to attach.
Can AI change my code?
AI analysis uses your own model key. Repository writing is a separate capability and is not enabled for the current beta setup. It will require explicit human approval when available. ErrorDock does not automatically merge changes.
Can I use it today?
ErrorDock is in a closed beta. Request access and tell us about your stack. When we approve it, we send you a beta access code: create your account at app.errordock.com and enter the code when you create your organisation. People you invite need no code. The SDK packages are published as release candidates; final terms are being completed before wider availability.
Build with a clearer picture
Know what to fix next.
Tell us what you are building. Let’s find the right way to bring ErrorDock into your workflow.