Errors shouldexplain themselves.
Cluebase is the layer that makes them: when an app breaks, an AI agent appears to the person it broke on, explains what happened, and hands the team a complete incident.
Why it exists.
Every other part of software has learned to talk. Deployments announce themselves, analytics describe behaviour, support chats answer questions. The error message stayed frozen: a code, a blank screen, a button that stops working, shown to the least technical person involved at the worst possible moment.
Cluebase started from a simple conviction about that moment. The person hitting the error deserves an explanation in their own words, and the team shipping the app deserves to know who the error reached, what they were trying to do, and how it ended for them. Nothing else in the error-monitoring stack captures either half, because none of it talks to the user.
The widget mounts outside the React tree, so it still works when the app white-screens or fails to hydrate. That is the bar the whole product is built around: functioning precisely when everything else is not.
How we build.
The agent tells the truth.
It explains an error only when it has the details to do so, and says plainly when it does not. It never claims a payment went through or that data was saved, because a confident wrong answer costs more trust than an honest small one.
The user is a person, not a log line.
Every error has someone on the other side of it. Cluebase records who was affected, talks to them while the failure is live, and hands your team their name and what happened to them, not just a stack trace.
Nothing to configure that you cannot see.
One package, one provider, one publishable key meant for the browser. Setup is five steps end to end, and everything the SDK sends is documented in the open API spec.
Who builds it.
Cluebase is built by Zion Abubakar in Lagos, Nigeria, with contributors across time zones. The product was formerly named Lumely; older references to Lumely refer to this same product.
Where we are as a company.
Incorporation is in progress, so our legal entity, registered address and governing law are marked as pending rather than stated in the terms and privacy policy. We would rather show you the gap than paper over it.