Error tracking on your kanban board.

devbord takes errors from the Sentry SDKs, groups them by cause and links them to the card that fixes them. Change the DSN: that is the whole migration.

From crash to card in three steps.

1. An error comes in: Grouped by cause, with the release and the suspect commit attached.
2. It becomes a card: In one click, or by itself with an automation rule.
3. Card completed, issue resolved: And if the error comes back, the card reopens. With a comment saying so.

What error tracking includes.

• Readable stack traces. Source maps, ProGuard and R8 mappings, and minidumps from native crashes.
• Releases. Crash-free sessions per version, deploys, and “resolved in the next release”.
• Performance. Transactions and spans, with Apdex and a waterfall per trace: see where the time goes.
• Alert rules. Decide who gets alerted and when: a new issue, a regression, or too many affected users.
• Owners. Rules on path, URL or type assign an issue automatically. You can import your CODEOWNERS file too.
• Cron and uptime monitors. Jobs that did not run and sites that do not answer, with a public status page to go with them.
• Bug reports from games. Players report a bug from FiveM, Minecraft, Roblox or Unity and you get a card.
• 100,000 errors a month. And 250,000 transactions, kept for 90 days.

Frequently asked questions

Do I have to change my code for error tracking?

Only the DSN. devbord speaks the protocol of the Sentry SDKs, so the SDK that is already in your app stays right where it is. For the browser and Node.js there are also our own packages: @devbord/browser and @devbord/node.

Which Sentry features are missing?

Session replay and profiling. Errors, releases, performance tracing, cron and uptime monitors and alert rules are all there.

Where does our data live?

On a server we rent from Hetzner, in Germany. We cannot open your projects without approval from an admin of your workspace, and what we look at then lands in your access log.

Which plan includes error tracking?

Error tracking is part of Premium. That is one fixed price per workspace, however many members you have.

Sentry alternative · Status pages · Time tracking

devbord · Pricing: one flat price per team · News · API documentation · Support: help and contact · Privacy: what we can and cannot see · Time tracking and invoicing for dev teams · Status pages with uptime monitoring and incidents · Changelog and release notes from done cards · A Trello alternative for dev teams · A Sentry alternative that keeps your SDKs · A Linear alternative with error and time tracking · A Jira alternative for small dev teams · An Asana alternative for software teams · A ClickUp alternative with error tracking and invoicing · A Toggl alternative with a board and invoicing · A Harvest alternative with a kanban board · A Statuspage alternative with monitoring built in