Manalens vs Bugnet for game bug reports
Bugnet is an error and bug tracking tool built for games. Its SDKs for Unity, Unreal Engine, Godot, GameMaker, Construct 3, Pygame and the web add an in-game report form for players, capture errors and crashes with the stack trace and recent logs, and track crash-free sessions for each build. It sends reports to Discord, Slack, GitHub, GitLab, Jira, Trello and other tools, and imports your Steam reviews. A free Indie plan covers 1 project and 100 bug reports; Studio is $19 a month and Studio Plus $79 a month. Manalens is the analytics and growth engine built for games. It counts errors and crash-free sessions next to your players, but it has no in-game bug report form, no screenshots or log files and no issue tracker integrations. It measures which links, creators and campaigns bring wishlists, players and sales. Choose Bugnet for bug reports, crash reports and player feedback. Choose Manalens for marketing attribution and player analytics. Many studios use both.
Features and prices
| Manalens | Bugnet | |
|---|---|---|
| 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. | Indie: free. Studio: $19 a month, or $15 a month billed yearly. Studio Plus: $79 a month, or $63 a month billed yearly. Higher limits by custom quote. |
| Free plan | No free plan. A 7-day trial with no card. | Yes, with no card: 1 project, up to 100 bug reports and 100 uploads, 2 team members, the in-game form and up to 1,000 Steam reviews. Report and upload limits are totals for the account, not monthly, and new reports are refused once the 100 are used. |
| In-game bug reports | Not available. No in-game report form, screenshots or player feedback inbox. | An in-game form on every plan and every engine, with screenshots, steps to reproduce, device details and your own files, such as a log or a save. Reports with the same title stack onto one issue. Auto-Triage suggests a category, priority and reply on Studio and above. |
| Crashes and errors | Error events, captured engine errors and crash-free sessions. No native crash dumps. A crash is counted at the next launch with app_unclean_exit. | The SDKs file errors and crashes with the stack trace and recent logs. Crash-free sessions, a health score for each version and regression detection. Native crash dumps and symbols are not listed in its docs. |
| Logs and replays | Error events carry a script stack trace of up to 1,024 characters. No log files and no replays. | Recent logs on auto-captured crashes, and a Live Logs feed of events and reports on Studio and above. A short recording of the moments before each report on Studio Plus. |
| Engines | 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 2020.3 or later, Unreal Engine 5, Godot 4, GameMaker Studio 2 or later, Construct 3, Pygame and web games, plus a REST API for other engines. |
| Integrations and alerts | Slack or signed webhook alerts when one of your events spikes or stops. No issue tracker integrations. | Webhooks, Discord, Slack and Microsoft Teams. Issues in GitHub, GitLab, Linear, ClickUp, Asana, Trello, Airtable, monday.com and Notion, and Jira Cloud on Studio Plus. PagerDuty, Opsgenie and Sentry. Email alerts for bug spikes and crash rate. |
| 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. | Imports your Steam reviews with sentiment, playtime at review and refund signals. Google Play and App Store reviews. Wishlists and sales are not listed. |
| Player analytics | Dashboards, funnels, flows, retention (D1, D7, D30), SQL Explorer, CSV export, REST API and MCP. Warehouse export is planned. | Custom events with daily trends and platform breakdowns on Studio (100,000 a month) and Studio Plus (unlimited), and a Players page keyed on the Steam ID. Retention and funnels are not listed. |
| Marketing attribution | UTM, referrers, tracked short links and typed creator codes. Stripe and Paddle payments, and itch.io purchases matched by email. Six attribution models. | Not listed. |
| Public pages for players | Not available. | A public bug tracker where players can upvote, and a public roadmap and changelog. |
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 | Bugnet |
|---|---|---|
| Setup and SDKs | ||
| Unity SDK | YesUnity 2021.3 or later. Desktop, mobile and WebGL builds. | YesUnity 2020.3 or later.Source: Bugnet game engine SDKs |
| Godot SDK | YesGodot 4. Engine and script errors on Godot 4.5 or later. | YesGodot 4.Source: Bugnet game engine SDKs |
| Unreal SDK | NoNo SDK. Unreal games send events to the HTTP endpoint. | YesUnreal Engine 5.Source: Bugnet game engine SDKs |
| GameMaker SDK | NoNo SDK. Any engine can send events to the HTTP endpoint. | YesGameMaker Studio 2 or later.Source: Bugnet game engine SDKs |
| Web SDK for sites and web games | YesOne script tag or the npm package. | YesA JavaScript module for web and HTML5 games.Source: Bugnet game engine SDKs |
| Offline queue in the game SDK | YesUnity and Godot save events on disk and send them later, up to 7 days old. | Not listed |
| Server events or HTTP API | YesServer events with a secret key, and a Node SDK. | PartialA REST API to send reports, sessions and events from any engine.Source: Bugnet analytics |
| Player analytics | ||
| Custom events | YesAny event name with your own properties. | PartialCustom events on Studio (100,000 a month) and Studio Plus (unlimited). Not on the free plan.Source: Bugnet analytics |
| Sessions and session length | YesA session ends after 30 minutes without focus or events. | PartialSessions are tracked for the crash-free rate. No session length is listed.Source: Bugnet analytics |
| 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. | YesThe SDKs file errors and crashes with the stack trace and recent logs.Source: Bugnet bug reports |
| Crash-free sessions | YesCounted with app_unclean_exit at the next launch. | YesCrash-free sessions for each version, with a health score.Source: Bugnet analytics |
| Native crash dumps and symbols | NoNo crash dumps or symbols. Keep Sentry or Backtrace for those. | Not listedNo crash dumps or symbol uploads in its docs.Source: Bugnet game engine SDKs |
| Bug reports and player feedback | ||
| In-game bug report form | NoNo in-game report form or player feedback inbox. | YesAn in-game form on every plan and every engine.Source: Bugnet bug reports |
| Screenshots, logs and files on reports | NoError events carry a short stack trace. No screenshots or log files. | YesScreenshots, device details and your own files, such as a log or a save.Source: Bugnet bug reports |
| Issues in GitHub, Jira or Trello | NoAlerts go to Slack or a webhook. We do not open issues in other tools. | YesGitHub, GitLab, Linear, Trello, Asana and more. Jira Cloud on Studio Plus.Source: Bugnet integrations |
| Steam reviews in the dashboard | NoWe do not import Steam reviews. | YesSentiment, playtime at review and refund signals. Up to 1,000 reviews on the free plan.Source: Bugnet integrations |
| LiveOps and backend | ||
| A/B tests | No | Not listed |
| Remote config or feature flags | No | Not listed |
| Session replay | No | YesA short recording before each report, on Studio Plus.Source: Bugnet analytics |
| 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. | Not listed |
| MCP server | YesProject-scoped MCP server for Claude, Cursor and other clients. | Not listed |
| 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. | YesCSV export of bug reports on every plan, webhooks and a REST API.Source: Bugnet billing and plans |
| Data warehouse or raw export | Not yetWarehouse export is planned. | Not listed |
| Pricing | ||
| Free plan | No | YesIndie: 1 project, 100 bug reports in total and 2 team members, no card.Source: Bugnet billing and plans |
| Free trial | Yes7 days, no card. | Not listed |
| Price basis | Monthly active users (MAU)No overage charges. | Plan tier, with limits on projects, reports and team membersSource: Bugnet billing and plans |
| Starting price | $79 a monthIndie plan, up to 10,000 MAU. | FreeStudio is $19 a month, or $15 a month billed yearly.Source: Bugnet billing and plans |
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 Bugnet is the better choice
- You want players to report bugs from inside the game, with a screenshot, device details and a log file.
- You want crash and error reports with recent logs, grouped into issues and sent to GitHub, Jira, Trello or Discord.
- You build in Unreal Engine, GameMaker, Construct 3 or Pygame, where we have no SDK.
- You want to read Steam reviews next to bug reports, with refund signals and a public bug tracker.
- You want a free start: the Indie plan has 100 bug reports with no card.
When Manalens is the better choice
- You want to know which link, creator or campaign brought wishlists, players and sales.
- You want Steam UTM data and an optional daily sync of all wishlists and sales (the automatic Steam sync is in early access).
- You want retention (D1, D7, D30), funnels and flows for your Unity, Godot or web game.
- You sell through itch.io, Stripe or Paddle and want revenue by channel with six attribution models.
- You want your data in your own hands: SQL, CSV export, a REST API and an MCP server.
Attribution · Retention · Stripe and Paddle revenue · Pricing
Bugnet and Manalens both report crash-free sessions. To work out crash-free sessions and players from your own counts, per build or platform, and the crashes to fix to reach a target, use the Crash-free rate calculator.
Frequently asked questions
Which should I choose: Manalens or Bugnet?
Bugnet is an error and bug tracking tool built for games. Its SDKs for Unity, Unreal Engine, Godot, GameMaker, Construct 3, Pygame and the web add an in-game report form for players, capture errors and crashes with the stack trace and recent logs, and track crash-free sessions for each build. It sends reports to Discord, Slack, GitHub, GitLab, Jira, Trello and other tools, and imports your Steam reviews. A free Indie plan covers 1 project and 100 bug reports; Studio is $19 a month and Studio Plus $79 a month. Manalens is the analytics and growth engine built for games. It counts errors and crash-free sessions next to your players, but it has no in-game bug report form, no screenshots or log files and no issue tracker integrations. It measures which links, creators and campaigns bring wishlists, players and sales. Choose Bugnet for bug reports, crash reports and player feedback. Choose Manalens for marketing attribution and player analytics. Many studios use both.
When Bugnet is the better choice
You want players to report bugs from inside the game, with a screenshot, device details and a log file. You want crash and error reports with recent logs, grouped into issues and sent to GitHub, Jira, Trello or Discord. You build in Unreal Engine, GameMaker, Construct 3 or Pygame, where we have no SDK. You want to read Steam reviews next to bug reports, with refund signals and a public bug tracker. You want a free start: the Indie plan has 100 bug reports with no card.
When Manalens is the better choice
You want to know which link, creator or campaign brought wishlists, players and sales. You want Steam UTM data and an optional daily sync of all wishlists and sales (the automatic Steam sync is in early access). You want retention (D1, D7, D30), funnels and flows for your Unity, Godot or web game. You sell through itch.io, Stripe or Paddle and want revenue by channel with six attribution models. You want your data in your own hands: SQL, CSV export, a REST API and an MCP server.
Sources
We checked these pages on . We leave out any fact that we could not find on them.