Beta access
Start with a clearer picture.
Grow from there.
We are preparing ErrorDock for wider availability. Tell us about your application, your stack and the traffic you expect.
Early access
Let’s connect your first project.
Explore the workflow with us before committing to a wider rollout.
- Error monitoring and session context
- Performance traces and product analytics
- Feature flags and uptime monitoring
- A conversation about your setup and usage
Requesting access does not start a subscription or charge a card.
Have a beta access code? Create your account.
Clear expectations
No surprise commitment.
Paid subscriptions and automated billing are not available yet. Access, usage limits and applicable terms will be agreed before onboarding.
The SDKs are published as release candidates (0.1.0-rc.2) on NuGet and npm. We will help you connect your first project during onboarding.
Explore the product first →Before you get started.
How does beta access work?
ErrorDock is in a closed beta. Request access and tell us about your application. 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 to that organisation need no code.
Can I buy a paid plan?
Not yet. We are finalising pricing and billing. This page does not offer paid tiers or a trial that automatically converts to a subscription.
What will determine future pricing?
We expect usage, retention and team requirements to matter. Final prices and included limits will be published before paid subscriptions become available.
Is AI included?
AI analysis requires your own supported model key and configured budget. Repository writing is not enabled in the current beta setup.
What about production data?
Data is stored in the EU, on a server in Finland, with encrypted daily backups in France. Discuss data handling and terms with us before sending production telemetry. See our security overview and privacy information.