From unexpected errors to fix.
Faster.
ByeBugs collects your errors, groups them into issues, and has an AI agent point to the line that caused them.
Compatible with the Sentry SDKs you already use.
5,000 events a month for free. No credit card required.
shop-api / issues / SHOP-API-4F
TypeError
Cannot read properties of undefined (reading 'email')
- 1,284 events
- First seen 2 hours ago
- Release 2.14.0
40async function notifyCustomer (order) {41 const customer = await customers.find(order.customerId)42 await mailer.send(customer.email, receipt(order))services/orders.js in notifyCustomer
Analysis of the agent
customers.find() returns nothing when the customer was deleted. The line 42 then reads email on an undefined value: check the customer before sending the receipt.
Suggested fix
const customer = await customers.find(order.customerId)Added: if (!customer) {Added: return logger.warn('Order without customer', order.id)Added: } await mailer.send(customer.email, receipt(order))Works with the official Sentry SDKs
- and every other one
Built for the Sentry SDK you already use
ByeBugs speaks the protocol of Sentry. There is no library to install and no code to rewrite.
What stays
The Sentry SDK
The official package you installed, at the version you run today.
Your code
Every captureException and captureMessage keeps working as written.
Your configuration
The environment and the release you already send with each error.
What changes
The DSN, in the configuration of the SDK or in the environment variable that holds it.
- SENTRY_DSN=https://4f1c9a7e@o450712.ingest.sentry.io/4507891+ SENTRY_DSN=https://4f1c9a7e:8d03e5b2@ingest.byebugs.io/12Deploy, and the next error of your application is grouped into an issue.
Keyboard shortcuts for everything
Optimized for efficiency. Resolve, Archive, next/previous event and issue and many more actions can be done without ever leaving your keyboard.
Try it here:
Click the list, then use your keyboard.
An agent that reads the code, not only the error
For each issue, the AI agent of ByeBugs goes through the stack trace, the code around it and the context of the event. It tells you why it broke, and what to change.
TypeError
Cannot read properties of undefined (reading 'email')
40async function notifyCustomer (order) {41 const customer = await customers.find(order.customerId)42 await mailer.send(customer.email, receipt(order))43}services/orders.js in notifyCustomer
customers.find() returns nothing when the customer was deleted, which is the case for 37 orders since the release 2.14.0. The line 42 then reads email on an undefined value.
Suggested fix
const customer = await customers.find(order.customerId) if (!customer) { return logger.warn('Order without customer', order.id) } await mailer.send(customer.email, receipt(order))Alerts where your team already talks
A new issue, a regression after a release, an error that escalates: ByeBugs tells you once, on the channels you chose for each project.
Email
To the members of the project
Slack
In the channel of your team
Discord
In the channel of your server
Telegram
In a group or a private chat
Webhooks
A request to your own tools, for everything else
No tracing. No replays. No dashboards to configure.
Just your errors, the reason they happened, and the way to fix them.
Pay for error tracking, not for a platform
Sentry bills a whole observability suite. ByeBugs does one thing, and do it well.
Errors per month
- Sentry Team
- $44.13 / month
- ByeBugs Team
- $24 / month
46% less than Sentry for 100,000 errors a month.
Public price of the Sentry Team plan billed annually, with its pay as you go rate, read on sentry.io/pricing on November 20, 2026. Sentry includes products that ByeBugs does not offer, such as tracing and session replay.
| Plan | Events a month | AI analyses a month | Price a month |
|---|---|---|---|
| Free | 5,000 | $0 | |
| Starter | 30,000 | $9 | |
| Team | 100,000 | $24 | |
| Business | 250,000 | $49 | |
| Scale | 1,000,000 | $99 | |
| Enterprise | Custom | On request |
Every plan has every feature. Compare the plans in detail
Made in the EU, hosted in France
Stack traces carry more than code: names, addresses, requests. Yours stay in Europe, under European law, with a company you can reach in Paris.
Servers in France
Every server, database and file of ByeBugs is operated by OVHcloud, in France.
An AI agent that stays in France
The agent runs on language models hosted by OVHcloud, in France. Your code and your errors are not sent to any other AI provider.
Emails sent from Paris
Account emails and alerts go through Amazon SES, in its Paris region.
Nothing leaves
The data of your application goes nowhere else. There is no other provider behind.
Questions, answered
Something else to ask? Write to support@byebugs.io, a developer answers.
Is there a free plan?
Yes. The free plan has no time limit and does not ask for a credit card. You can upgrade, downgrade or cancel at any time from the billing page.
Do I need to change my code or install a new library?
No. ByeBugs speaks the same protocol as Sentry, so you keep the official Sentry SDK you already have, at the version you run today. You only replace the DSN in its configuration, deploy, and the next error of your application appears in ByeBugs.
Can I import my existing issues from Sentry?
No. Most error trackers skip import, because old errors lose value fast and live errors reappear within hours of switching the DSN.
Does ByeBugs do tracing, session replay or logs?
No. ByeBugs only tracks errors, which keeps the product simple and its price low. If your SDK sends traces or replays, ByeBugs ignores them and they do not count in your plan.
How does the AI agent work?
When an error arrives, the agent reads its stack trace, the code around each frame and the context of the event. It explains the likely cause in plain language and suggests a change to fix it. You stay in control, since nothing is changed in your code without you.
Does the AI agent have access to my repository?
Not by default. The agent only reads what the event carries, which is the stack trace, the lines of code the SDK attached to each frame and their variables, once the values that look like secrets are removed. If you want it to read more of your code, you can install the GitHub or GitLab integration to give ByeBugs access to your repository.
Is my code used to train an AI model?
No. Your code and your errors are only used to write the suggestion for your own issue. They are never used to train a model.
Can I turn the AI agent off?
Yes. A switch in the settings of your organization turns the agent off. Nothing is sent to the language model anymore, and your errors are still received, grouped and alerted the same way.
How many team members and projects can I have?
As many members as you want, on every plan, the free one included. An organization starts with 10 projects, and we raise that number on request.
Can I share an issue with someone outside my team?
Yes. You can create a public link for an issue. Anyone with the link sees the error, its stack trace and how often it occurs, without what could be sensitive, such as the users, the requests and the variables. You can stop sharing at any time.
What happens when I reach the quota of my plan?
The events over the monthly quota of your plan are refused until the next period, and you are never billed more than the price of your plan. A spike protection also stops a single issue that floods from using your whole quota.
Your next error could already be here
Create a project, replace a DSN, deploy.
The free plan has no time limit and asks for no credit card.