Luciq.

Somewhere right now, a Luciq agent is reading a stack trace before a human is.

The agent reads the crash. It cross-references the release. It scores the business impact - is this an edge-case affecting twelve users, or the checkout flow on Verizon's iOS app? Then it does the part that, until very recently, no observability vendor would dare do unsupervised: it drafts the fix, opens a pull request, and posts the diff into Slack with a polite recommendation. The on-call engineer pours coffee. The agent has already triaged.

This is Luciq in May of 2026, eight months after it stopped calling itself Instabug. The company that spent thirteen years politely reporting bugs has decided, with the conviction of a startup that has finally figured out what it actually sells, that reporting is no longer enough. The product now does the thing it used to merely describe.

The Problem They Saw

Mobile is a feral platform. Two operating systems, four major frameworks, six device generations actively in use, and a global user base that will give your app exactly one chance before uninstalling. Every minute spent staring at dashboards is a minute not spent shipping. And there are a lot of dashboards.

The mobile observability market, as Luciq's leadership team likes to say in investor decks, is fragmented. Translation: a typical enterprise mobile team in 2024 was paying for crash analytics from one vendor, performance monitoring from another, session replay from a third, bug reporting from a fourth, and feature flags from a fifth - and stitching them together with a Slack channel called #mobile-incidents-please-look.

Luciq's bet is that none of those tools, by themselves, will survive the agentic era. The dashboard is becoming the AI's eyes. The human is becoming the AI's editor. And the company that owns the agent layer for mobile owns the next decade of mobile reliability.

The Founders' Bet

Omar Gabr and Moataz Soliman met as engineering students at Cairo University. In their final semester, somewhere around 2012, they built a simple SDK that let mobile users shake their phone to report a bug. It was a small idea. It was also, in hindsight, the wedge.

By 2016 they were in Y Combinator's W16 batch. By 2019, Accel was leading a Series A. By 2022, Insight Partners was writing the $46 million Series B check that funded what would become the agentic pivot. None of those rounds were enormous by Silicon Valley standards, which is the polite way of saying the founders had to choose their bets carefully. The agentic pivot was the bet.

The rename, when it came in September 2025, was the cleanest signal a company can send: we are no longer the thing we used to be, and the old name will haunt the new product. Instabug sounded like a bug tracker. Luciq - pronounced LOO-sik, somewhere between lucid and circuit - is harder to pin down on purpose.

The Product

What Luciq actually ships is a layered system. At the bottom, SDKs for iOS, Android, Flutter, and React Native, sitting inside the app and quietly collecting telemetry that ranges from crash stack traces to user-session video. In the middle, a streaming pipeline that ingests this data at the scale of apps with hundreds of millions of monthly active users. At the top - and this is the part that took thirteen years to earn the right to build - a set of autonomous AI agents that do something with all of it.

The agents are not a chatbot bolted onto a dashboard. They are, in the company's own framing, extensions of the mobile engineering team. They watch releases roll out, compare new builds against production baselines, detect regressions before users complain, escalate the ones that affect revenue, and - here is where Luciq's pitch lives or dies - suggest the fix. Sometimes they write the fix. The engineer's job becomes review, not detection.

What you can actually do with it

If you are a mobile engineering lead, Luciq replaces between two and five line items on your tooling invoice. Crashlytics goes. Bug reporting goes. The session-replay vendor goes. Some piece of your APM goes. In exchange, you get a single platform that promises to make the alerts you do receive worth receiving - because the agent already filtered out the ones that don't matter.

The Proof

Numbers, in order: 25,000+ mobile teams on the platform. 290 employees, give or take, split between San Francisco and remote. $53 million raised, total, across all rounds. An estimated $36.5 million in annual revenue. Customer logos that include DoorDash, T-Mobile, Verizon, Decathlon, and Saturn. G2 has given them Momentum Leader and High Performer badges, which is the SaaS equivalent of an Oscar nomination.

The customer roster matters more than the funding. DoorDash is not a logo a mobile observability vendor wins by accident. T-Mobile does not sign with a vendor whose SDK might crash the dialer. Each of those names is a multi-year procurement cycle, a security review, and a series of bake-offs against the incumbents. That Luciq won them - and kept them through the rebrand - is the closest thing to product-market fit that an enterprise SaaS company gets.

The Mission

In the company's own words: transform app quality into business outcomes. Stripped of the SaaS-deck phrasing, what they mean is something like this - the people who build mobile apps spend most of their time on the unglamorous, low-leverage work of finding out something is broken. Luciq's mission is to give that time back. The agents do the finding. The humans do the building.

There is a small irony here, of course. The original Instabug pitch, back in 2012, was that the user would do the finding - they'd shake their phone, and a bug report would land in a dashboard. Luciq's bet thirteen years later is the opposite: the user shouldn't have to find anything. The agent should have caught it before the user noticed.

Why It Matters Tomorrow

Mobile is not getting simpler. The number of frameworks is still climbing. The number of devices is still climbing. AI features are now shipping inside the apps themselves, which means a whole new category of failures - hallucinated responses, model-version drift, latency spikes from inference - that the previous generation of observability tools never had to think about. The agentic layer that Luciq is building for crashes will, plausibly, be the same layer that mobile teams use to manage their own in-app AI features in a year or two.

That is the long bet. Whether Luciq wins it depends on three things: whether the agents are good enough to be trusted unsupervised; whether the incumbents - Datadog, Sentry, Embrace, Firebase - move fast enough to catch up; and whether the category Luciq invented in September 2025 actually becomes a category, or quietly collapses back into "observability with some AI in it."

The team in San Francisco is betting on category. The check from Insight Partners is betting on category. The pull request the agent just opened, at 3 AM Pacific time, is betting on category.

Back at the start of this story, somewhere in the world, a Luciq agent was reading a stack trace before a human was. By now it has finished. The pull request is open. The on-call engineer is still drinking their first coffee. The user, who never knew anything was wrong, is opening the app to order dinner. The crash that was about to happen, didn't.

That is the product. That is the bet. That is, in the end, why thirteen years of bug reports were worth renaming.