ExeWatch vs EurekaLog and madExcept
EurekaLog and madExcept are libraries you compile into your Delphi application to catch an exception and send a bug report about it, and you pay for them per developer. ExeWatch catches the exception too, with a stack trace that shows unit, function and line, and that is free on every plan. Then it does what a bug report cannot: alerts by email, Discord and webhook, AI anomaly detection, and the logs, timings, metrics and hardware of every machine that runs your application, in one dashboard.
ExeWatch vs EurekaLog and madExcept, side by side
| ExeWatch | EurekaLog | madExcept | |
|---|---|---|---|
| Cost of the stack trace | Free, on every plan: unit, function and line on Win32 and Win64 | €149 per developer (Professional) or €249 (Enterprise), with 12 months of updates1 | €159 per developer with one year of updates, then €49 a year. Free only for non-commercial use2 |
| Where the reports go | An online dashboard with every customer and machine in one place, plus alerts by email, Discord and webhook | By email, to your configured web endpoint or to a supported bug tracker3 | Email, web upload and printing4 |
| Alerts | When errors or slow operations cross a threshold you set: email on every plan, Discord from Pro, webhooks with your secret token from Business | Not listed among its features3 | Not listed among its features4 |
| AI anomaly detection | The AI engine learns how your application normally behaves and warns you when it changes: error anomalies from Pro, timing anomalies too from Business | Not listed among its features3 | Not listed among its features4 |
| Logs and breadcrumbs | Every log line from every machine, and the steps the user took before each error | Not listed among its features3 | Not listed among its features4 |
| Timings and metrics | Average and P95 of each operation, traces split into steps, counters and gauges | Not listed among its features3 | Not listed among its features4 |
| Self-healing apps | On paid plans, ExeWatchMCP lets Claude Code, Codex and KAI in RAD Studio read the crashes, slow operations and metrics from the field and propose the fix instead of guessing. You review it and ship it | Not listed among its features3 | Not listed among its features4 |
| Delphi versions | XE8 to 13 Florence natively, Delphi 5 to XE7 through the DLL | Delphi 5 or later, C++Builder 2006 or later5 | Delphi 4 to 7 and 2005 to 12, C++Builder 5 to 6 and 2006 to 12 in 32 bit4, Delphi 13 since version 5.2.06 |
| Targets | Windows 32 and 64 bit, Linux 64 bit, Android | Win32 and Win645 | 32 and 64 bit Delphi4 |
Each fact about another product links to the vendor page it comes from, listed at the bottom of this page.
Where ExeWatch is stronger than EurekaLog and madExcept
Stack traces on the free plan
A stack trace with unit, function and line comes with every plan, the free one included, on Win32 and Win64 and with no map file shipped next to the program. A commercial licence costs €149 per developer for EurekaLog Professional1 and €159 for madExcept2.
Every customer machine in one place
You search, filter and count errors across all your customers instead of reading reports one at a time in an inbox.
More than the crash
Logs, breadcrumbs, timings with average and P95, counters and gauges come from the same SDK, next to the errors.
The hardware it ran on
CPU, RAM, disks with their free space, monitors, operating system version and build, time zone and locale, collected by the SDK with no code of yours.
Alerts where your team already is
An alert reaches you by email, in a Discord channel or at your own webhook when errors or slow operations cross a threshold, and the AI engine flags what is unusual for your application without a threshold to set.
Linux and Android
The same Delphi units compile for Linux 64 bit and Android, as well as Windows.
Customers and machines
Every event carries the customer you set at startup, the machine and the application version, so you can open one customer and see each of their machines. On a Terminal Server, each Windows user is a separate device.
Using them with ExeWatch
They work side by side. If madExcept or EurekaLog catches an exception first, forward its report to ExeWatch: madExcept has already resolved the stack with unit names and line numbers, and ExeWatch shows it as it is. The documentation has the code.
ExeWatch vs EurekaLog and madExcept: questions
Do I have to remove madExcept or EurekaLog to use ExeWatch?
No. It can stay, and each exception it catches goes on to ExeWatch with the stack it has already resolved. The documentation shows how, with a sample for Delphi 12 and 13.
Can ExeWatch replace EurekaLog or madExcept?
For what happens on your customers' machines, yes. With the native SDK (Delphi XE8 and later) ExeWatch catches unhandled exceptions by itself and shows the stack trace with unit, function and line, on the free plan too, and adds logs, breadcrumbs, timings, metrics, hardware, alerts and AI anomaly detection from every machine. A library that sends a bug report for each crash covers a small part of that.
What does ExeWatch add to an application that already uses madExcept?
A view across all your customers: how often each error happens, on which machines and versions, what the user did before it, how long the slow operations take, and an alert by email, Discord or webhook when something crosses a threshold or the AI engine sees an anomaly.
Other comparisons: Sentry for Delphi and C++Builder · .NET desktop: Sentry, Raygun, Application Insights
Sources
Checked on 17 November 2026. Vendors change their pages and prices: if one of these facts is out of date, tell us and we will correct it. Product names are trademarks of their owners, and ExeWatch is not affiliated with them.