Error monitoring for CTOs, with AI access you control

The perfect overview of your applications

Do you ever feel like you are missing an overview of the current quality of your applications, instead of just waiting for customers to report bugs? With the elmah.io dashboard, your team can see the errors introduced in your software, and you can follow the quality of each release.

By combining severity and frequency, we help you and your team prioritize what to fix first. In our experience, we uncover previously unknown errors when you integrate with elmah.io.

Using deployment tracking, we monitor each deployment of your software. When a bug is introduced in a new version, we notify you instantly. Introducing zero bugs is impossible, but finding them before your customers do is not.

Predictable cost

Plans are flat monthly prices, and you pay the same no matter how many servers, containers or CPUs you run. Business+ and Enterprise include unlimited users, so growing the team does not change the bill.

Start with the free 21-day trial, without a credit card. The plans and what they include are on the pricing page.

You decide what AI can see

AI is useful for fixing errors, and your logs can be sensitive. These are the controls you have:

• Off by default. Bugster, the AI assistant in elmah.io, can only read log data after an admin turns on Extended Access. Source code and breadcrumbs are separate toggles.
• Bring your own model, or use ours. On Business and Business+, Bugster uses your own OpenAI, Gemini or Claude API key. On Enterprise, you can pick a model hosted by elmah.io, so log data does not leave our data center.
• Your logs are not used for training. elmah.io does not use your log data to train Bugster. With your own key, the settings of your provider apply, and we recommend turning off model improvement there.
• Scoped access for agents. Developers connect their AI tools to the MCP server by signing in with their own elmah.io account. Scripts and pipelines use API keys, with the permissions you give each key.

Read how Bugster is configured and how the MCP server is set up.

Securely store errors in the Cloud

By using the Cloud to store your errors, you no longer need a budget for maintaining a local logging infrastructure. Installing and maintaining software like SQL Server and Elasticsearch is time consuming and expensive, and with elmah.io we take care of it for you. For your security team:

• Data is stored in Microsoft Azure in the United States, in private, isolated networks with DDoS protection and daily backups.
• An external partner runs penetration tests every month.
• Two-factor authentication works with all sign-in methods.
• API keys are scoped, so a key can be limited to for example writing messages or deployments.
• We are PCI compliant, and a copy of our SAQ A is available on request. A dedicated GDPR commitment document describes the personal data we collect and how we handle it.

Read more on the security page.

What your team gets

Developers get errors in the dashboard, on Slack and Microsoft Teams, or in an issue tracker like GitHub or Jira. They can also search from the terminal with the CLI, or ask an AI agent through the MCP server.

Beyond errors, the same account covers uptime monitoring, heartbeats for scheduled jobs and deployment tracking.

Frequently asked questions