Manalens vs Sentry for game crashes
Sentry is an error and crash reporting tool with SDKs for Unity, Unreal, Godot and consoles. It captures native crashes with minidumps on Windows and Linux, and symbolicates them with your debug files. A free Developer plan has 1 user and 5K errors; Team is $29 a month and Business $89 a month when billed monthly ($26 and $80 a month when billed yearly), each with 50K errors. Manalens is the analytics and growth engine built for games. It sends errors as events, captures engine errors in Unity and Godot, and counts crash-free sessions, but it does not store native crash dumps or symbols. Use Sentry to fix native crashes. Use Manalens to see which players, builds and campaigns the errors hit. Many games use both.
Features and prices
| Manalens | Sentry | |
|---|---|---|
| Price | Indie $79 a month for up to 10K MAU. Scale $199 to $999 a month for 20K to 100K MAU. Enterprise above 100K MAU, by contract. A year costs the price of ten months. Hosted checkout is not open yet. | Developer: free, 1 user, 5K errors. Team: $29 a month, or $26 a month billed yearly. Business: $89 a month, or $80 a month billed yearly. Team and Business include 50K errors. |
| Billing unit | Monthly active users (MAU). A player on your website and in your game counts once. No overage charges. | Errors a month, with an optional pay-as-you-go budget for overage. |
| Game SDKs | Unity (2021.3 or later) and Godot 4 SDKs, a web SDK and server events. Other engines, such as Unreal, send events to the HTTP endpoint. | Unity, Unreal, Godot, native C and C++, and SDKs for Xbox, PlayStation and Switch. |
| Native crashes | No crash dumps or symbols. A crash is counted at the next launch with app_unclean_exit. | Native crash capture, with minidumps on Windows and Linux, and a symbol server for your debug files. |
| Script errors | Unity exceptions, Debug.LogError and failed asserts, and Godot 4.5+ engine and script errors, grouped by fingerprint. | Unity C# exceptions and Godot script and shader errors. |
| Players and marketing | Errors share the same player, session, build and campaign as your other events, so you can use them in funnels, retention and filters. | Not listed on the gaming page. |
| Steam and store data | Import the Steam UTM Analytics CSV for visits, wishlists and purchases by source and campaign. An optional Steamworks Financial API key (the automatic Steam sync is in early access) syncs all wishlists and sales each day. | Not listed on the pricing page. |
Prices are in USD, before tax. They come from each company's own pages on the date above and can change.
Detailed feature comparison
| Feature | Manalens | Sentry |
|---|---|---|
| Setup and SDKs | ||
| Unity SDK | YesUnity 2021.3 or later. Desktop, mobile and WebGL builds. | YesSource: Sentry for gaming |
| Godot SDK | YesGodot 4. Engine and script errors on Godot 4.5 or later. | YesSource: Sentry Godot SDK |
| Unreal SDK | NoNo SDK. Unreal games send events to the HTTP endpoint. | YesSource: Sentry for gaming |
| GameMaker SDK | NoNo SDK. Any engine can send events to the HTTP endpoint. | NoNo GameMaker SDK on its platform list.Source: Sentry platforms |
| Web SDK for sites and web games | YesOne script tag or the npm package. | YesBrowser JavaScript SDK.Source: Sentry JavaScript SDK |
| Offline queue in the game SDK | YesUnity and Godot save events on disk and send them later, up to 7 days old. | YesThe Unity SDK stores events on disk and sends them later.Source: Sentry Unity options |
| Server events or HTTP API | YesServer events with a secret key, and a Node SDK. | YesServer SDKs such as Node.js, Python and Go.Source: Sentry platforms |
| Player analytics | ||
| Custom events | YesAny event name with your own properties. | PartialCustom metrics and logs, not analytics events.Source: Sentry JavaScript SDK |
| Sessions and session length | YesA session ends after 30 minutes without focus or events. | PartialSessions count toward release health. No session length is listed.Source: Sentry release health |
| Retention (D1, D7, D30) | YesDay and week cohort retention. | Not listed |
| Funnels | YesFunnels and flows. | Not listed |
| Cohorts | YesRetention cohorts and install cohorts. | Not listed |
| One player across website and game | YesA game link joins the browser to the game install. The player counts once. | Not listed |
| Marketing and attribution | ||
| Campaign and link attribution (UTM) | YesUTM, referrers and tracked short links, with six attribution models. | Not listed |
| Steam UTM Analytics data | YesImport the Steam UTM Analytics CSV: visits, wishlists and purchases by source and campaign. | Not listed |
| Steam wishlists | YesBy UTM source, from the Steam UTM Analytics CSV. All wishlists each day with a Steamworks Financial API key: the automatic Steam sync is in early access. | Not listed |
| Creator links and codes | YesTracked short links and typed creator codes. | Not listed |
| Creator search and outreach | NoWe do not find or contact creators. | Not listed |
| Ad spend and ROAS | Not yetAd-spend import is planned. | Not listed |
| Press and coverage | ||
| Press kit builder | YesA free tool: import from Steam, export a ZIP that you host, with a tracked link for each outlet. | Not listed |
| Hosted press kit and newsroom | NoWe do not host press kits or press releases. | Not listed |
| Coverage and mention tracking | Not yetCoverage tracking is planned. Tracked links and creator codes count what coverage sends. | Not listed |
| Coverage alerts in Discord or Slack | NoSlack and webhook alerts are for your own events, not for coverage. | Not listed |
| Game key distribution | NoWe do not send or track game keys. | Not listed |
| Revenue | ||
| Steam sales | Early accessUnits, gross and net sales per day and country with a Steamworks Financial API key. The automatic Steam sync is in early access. | Not listed |
| itch.io purchases | YesPurchases matched by email. | Not listed |
| Stripe payments | Yes | Not listed |
| Paddle payments | Yes | Not listed |
| Errors and quality | ||
| Error events | YesUnity exceptions and Godot engine errors, grouped by fingerprint. | YesUnity C# exceptions and Godot script and shader errors.Source: Sentry for gaming |
| Crash-free sessions | YesCounted with app_unclean_exit at the next launch. | YesCrash-free sessions and crash-free users by release.Source: Sentry release health |
| Native crash dumps and symbols | NoNo crash dumps or symbols. Keep Sentry or Backtrace for those. | YesMinidumps on Windows and Linux, and a symbol server.Source: Sentry for gaming |
| Bug reports and player feedback | ||
| In-game bug report form | NoNo in-game report form or player feedback inbox. | Not listed |
| Screenshots, logs and files on reports | NoError events carry a short stack trace. No screenshots or log files. | Not listed |
| Issues in GitHub, Jira or Trello | NoAlerts go to Slack or a webhook. We do not open issues in other tools. | Not listed |
| Steam reviews in the dashboard | NoWe do not import Steam reviews. | Not listed |
| LiveOps and backend | ||
| A/B tests | No | Not listed |
| Remote config or feature flags | No | Not listed |
| Session replay | No | YesSession Replay for web apps. 50 replays on each plan.Source: Sentry Session Replay |
| Player accounts and backend | NoNot a backend. No player accounts, inventories or leaderboards. | Not listed |
| AI and agents | ||
| Ask questions in plain language | YesAsk AI answers from your reports and can write charts. | YesAsk Seer in plain language. Seer is a paid add-on.Source: Sentry Seer |
| MCP server | YesProject-scoped MCP server for Claude, Cursor and other clients. | YesMCP access is on the free Developer plan.Source: Sentry pricing |
| Privacy and data | ||
| Consent mode with no storage before consent | YesConsent mode stores no cookies or IDs until the player consents. | Not listed |
| SQL on your events | YesSQL Explorer. | Not listed |
| CSV export or data API | YesCSV export and a REST API. | YesExport query results as a file, up to 10 million rows.Source: Sentry Discover queries |
| Data warehouse or raw export | Not yetWarehouse export is planned. | Not listed |
| Pricing | ||
| Free plan | No | YesDeveloper plan: 1 user, 5K errors.Source: Sentry pricing |
| Free trial | Yes7 days, no card. | Yes14 days of the Business plan, no card.Source: Sentry pricing |
| Price basis | Monthly active users (MAU)No overage charges. | Errors a monthWith an optional pay-as-you-go budget.Source: Sentry pricing and quotas |
| Starting price | $79 a monthIndie plan, up to 10,000 MAU. | FreeTeam is $29 a month.Source: Sentry pricing |
Not listed means we did not find the feature on the pages we checked. It may still exist. Each fact about another tool links to its source.
When Sentry is the better choice
- Your game crashes in native code, for example in the engine or a GDExtension, and you need the stack trace.
- You ship on consoles and need crash reports there.
- You want a free start: the Developer plan has 5K errors.
When Manalens is the better choice
- You want crash-free sessions and errors by build next to retention, funnels and campaigns.
- You want to know if players from one campaign or creator crash more often.
- You sell on Steam and want wishlists, sales and store visits by source, campaign and creator.
- You want one price by MAU, with errors included.
Attribution · Retention · Stripe and Paddle revenue · Pricing
Frequently asked questions
Which should I choose: Manalens or Sentry?
Sentry is an error and crash reporting tool with SDKs for Unity, Unreal, Godot and consoles. It captures native crashes with minidumps on Windows and Linux, and symbolicates them with your debug files. A free Developer plan has 1 user and 5K errors; Team is $29 a month and Business $89 a month when billed monthly ($26 and $80 a month when billed yearly), each with 50K errors. Manalens is the analytics and growth engine built for games. It sends errors as events, captures engine errors in Unity and Godot, and counts crash-free sessions, but it does not store native crash dumps or symbols. Use Sentry to fix native crashes. Use Manalens to see which players, builds and campaigns the errors hit. Many games use both.
When Sentry is the better choice
Your game crashes in native code, for example in the engine or a GDExtension, and you need the stack trace. You ship on consoles and need crash reports there. You want a free start: the Developer plan has 5K errors.
When Manalens is the better choice
You want crash-free sessions and errors by build next to retention, funnels and campaigns. You want to know if players from one campaign or creator crash more often. You sell on Steam and want wishlists, sales and store visits by source, campaign and creator. You want one price by MAU, with errors included.
Sources
We checked these pages on . We leave out any fact that we could not find on them.