ExeWatch vs Sentry for Delphi and C++Builder
Sentry's list of official SDKs has no entry for Delphi, C++Builder or RAD Studio. ExeWatch was built for them: you install a setup, turn ExeWatch on from the Project menu, and errors arrive with unit, function and line.
ExeWatch vs Sentry, side by side
| ExeWatch | Sentry | |
|---|---|---|
| Cost of a Delphi stack trace | Free, on every plan: unit, function and line on Win32 and Win64 | No official Delphi SDK, so no Delphi stack trace out of the box1 |
| Alerts, AI anomaly detection, logs and timings for a Delphi app | Yes, from the same SDK: alerts by email on every plan, Discord from Pro, webhooks from Business | Not for Delphi out of the box: there is no official Delphi SDK1 |
| Delphi SDK | Native units for Delphi XE8 to 13 Florence, installed by the ExeWatch for RAD Studio setup. A DLL covers Delphi 5 to XE7. | Not in the list of official SDKs1 |
| C++Builder | The same units, added to the project from the Project menu. Older versions use the DLL. | Not in the list of official SDKs1 |
| Delphi stack traces | Unit, function and line on Win32 and Win64, from the map file linked into the executable. There is nothing to upload. | Symbols must be PE/PDB, ELF, Mach-O, Breakpad, WASM or ProGuard files. Delphi map files are not among them2 |
| Other C and C++ compilers on Windows | A DLL with a plain C interface, tested with MSVC. MinGW and Clang call it through the same Windows ABI | Native SDK for MSVC (Visual Studio 2022 or later) and LLVM-MinGW3 |
| Free plan | 1 application, 5,000 events a month, 7 days of data | 1 user, 5,000 errors, 30 days of data4 |
| First paid plan | Pro, €19 a month: 5 applications, 100,000 events, 30 days, 5 team members | Team, $29 a month or $26 billed annually: 50,000 errors, up to 90 days4 |
| Where the data is stored | Telemetry on servers in Germany, run by an Italian company | US or EU (Frankfurt), chosen when the organization is created. Some account data may be stored in the US whatever you choose5 |
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 Sentry
Made for RAD Studio
The setup finds every RAD Studio from XE8 on and adds an ExeWatch entry to the Project menu. Enable ExeWatch Telemetry adds the configuration unit and the two calls your program needs.
Line numbers without shipping a map file
Link map file writes the symbol map inside the executable at every build, so a trace from a customer's machine shows unit, function and line. On a build server, ExeWatchMapCLI does the same.
Windows, Linux and Android from one SDK
The same units compile for VCL, FireMonkey, console applications and services on all three.
Old Delphi versions too
The DLL SDK works from Delphi 5 to XE7, so an application that never moved to a newer compiler can still report its errors.
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.
Nothing lost offline
The Delphi, C/C++, .NET and Python SDKs write events to disk within seconds and send them when the connection comes back, after a restart too. Unsent files are kept for 7 days by default.
ExeWatch vs Sentry: questions
Does Sentry support Delphi?
No. Sentry's list of official SDKs has no entry for Delphi, C++Builder or RAD Studio (we checked docs.sentry.io/platforms on 17 November 2026). Its native SDK is built for MSVC and LLVM-MinGW, and the symbol formats it reads do not include Delphi map files, so a Delphi integration would be code you write and maintain yourself.
Can ExeWatch replace Sentry for a Delphi team?
For applications written in Delphi or C++Builder, yes: ExeWatch collects errors with their stack traces, logs, timings and metrics from every machine that runs them. If you also have web or mobile projects on Sentry, you can keep them there, or move the JavaScript and Python ones to ExeWatch and keep everything in one dashboard.
How long does it take to start with ExeWatch?
Install ExeWatch for RAD Studio, open your project, choose Project > ExeWatch > Enable ExeWatch Telemetry and paste the API key of your application. The free plan needs no credit card.
Other comparisons: EurekaLog and madExcept · .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.