For apps with real users
Fix the bugs you'd never have heard about.
Cirlo finds the cause, your coding agent builds the fix, and everyone who reported it hears back.
No credit card needed
Cirlo · Demo app
“The PDF export doesn't work. It just keeps loading.”
The export stops after 30 seconds on larger files.The export stops after 30 seconds on larger files.
Fix
Raise the time limit and show progress.Raise the time limit and show progress.
Works with what you already use.
- Lovable
- Bolt
- Replit
- Sentry
- Gmail, Outlook, Proton Mail
- Slack
- Discord
- GitHub
- Claude Code
- Cursor
- Codex
- Vercel
- Netlify
- + more
From bug to fix
The moment a bug shows up, Cirlo takes over.
Reported
Everything lands in one place
Reports from your app, your inbox, Slack, Discord and Sentry. Grouped and sorted by affected users.
Inbox, sorted by affected users
- Publishing fails without a plan14 affected · +3 today · Reports
- PDF export hits a time limit10 affected · +1 today · Reports · Sentry
- Crash when opening settings6 affected · Sentry, unreported
- Password reset email arrives twice2 affected · Slack
Cause found
The cause, with evidence
Cirlo knows what happened before the bug and checks it against Sentry and similar reports.
Cirlo · Demo app
“I can't publish my project. The button doesn't respond.”
Publishing fails when the project has no plan assigned yet.
- Click pathClick on Publish, request fails
- Sentrysame error, 41 events in 7 days
- Reports14 users, 3 of them paying
Fix handed over
One click, your agent builds the fix
The task goes to Lovable, Cursor, Claude Code or Codex. No code changes without your approval.
Task for your agent
Publishing fails when no plan is set yet. Fall back to the default plan, catch the error and add a test.
Once the fix is in, all 14 reporters hear about it.
Why not build it yourself
Sentry plus Codex, or Cirlo.
Your agent writes the code either way. The difference is what happens before and after.
Context, not surveillance.
Cirlo sees what happened before a bug, without keystrokes and without continuous recording. The feedback button is smaller than a photo.
- No replays
- No videos
- No keystrokes
- No form values
Automatic follow-up
The bug is done. So is the follow-up.
Every reporter hears about it personally, in their own language. Only once the fix is really live. And if the bug comes back, the issue reopens.
Everyone gets told
One fix. Every reporter informed.
Status without asking
A personal link shows where things stand.
Not fixed yet?
A reply reopens the issue.
Issue · PDF export
PDF export fails on large files
Update is live- SandraGerman✓ notified
- AlexEnglish✓ notified
- MarieFrench✓ notified
- + 7 more users notified
To Marie
FrenchBonjour Marie, le problème que tu as signalé est corrigé dans la mise à jour qui vient d'être publiée.
Pricing
Start free. Fix more bugs for CHF 29.
Fixed prices. No AI tokens. Spam never counts.
Free
CHF 0
For your first apps.
- 3 projects
- 100 reports per month
- 5 analyzed issues per month
- Widget, support email, Slack, Discord, Sentry
- Tasks for Lovable, Cursor, Claude Code, Codex
- Status links and follow-ups
- Daily summary
Pro
RecommendedCHF 29 / month
For products that grow.
- Unlimited projects
- 1,000 reports per month
- 50 analyzed issues per month
- Deeper analysis of complex bugs
Pro can't be booked yet during the free launch. A short email is enough, we'll get in touch when it opens.
Your own tool builds the fix. Cirlo never changes code without your approval.
An analyzed issue is the cause plus the finished task. Spam and reports that can't be reproduced don't count.
FAQ
The key questions. Answered briefly.
I build with Lovable, Bolt or Replit. Does that work?
Yes. You paste a text into your app's chat, and it has a feedback button. For every issue you get a finished task for the same chat, in Lovable with one click.
Once the bug is gone, you mark the issue as fixed and every reporter hears about it. You don't need Sentry or GitHub for that.
Does Cirlo fix bugs automatically?
Cirlo finds the cause and writes the task. Your own tool builds the fix: Lovable, Cursor, Claude Code or Codex. With GitHub, Cirlo files the task straight with your agent.
Cirlo notices when the fix is in and only then tells the reporters. For App Store apps the message says "coming with the next update".
Can't I just ask Codex or Claude Code?
Yes, for every bug you know about. Cirlo is for the others: reports sitting in your inbox, crashes nobody reported, and fixes that come back after the deploy.
And you can still hand every task to your own agent.
Who writes to my users?
You do. The message carries your name and replies come back to you. Unless you change it, nothing goes out before you approve it.
My users report bugs in Slack or Discord. Does that work?
Yes. You connect the one channel where people report. Every message there becomes a report, nobody has to learn a command or mention Cirlo.
And since Slack and Discord don't provide an email address, Cirlo replies in the same thread once the bug is fixed.
Do I need Sentry or GitHub?
No. The feedback button or support email are enough. With Sentry, Cirlo also finds crashes nobody reported. With GitHub, it notices by itself when the fix is in.
Does Cirlo change code without my approval?
No. No change goes in before you approve it.
What happens if Cirlo can't find a cause?
The issue says so openly and shows what was checked. You can pass it on or have it analyzed again later.
What do my users see?
The feedback button, their status link and messages about their own report. Diagnoses, code and other reporters stay hidden.
What happens to ideas, questions and praise?
Cirlo separates them from the bugs and collects them on their own page. If several people ask for the same thing, you'll see it.
Your app will have bugs. You don't have to give them your day.
Cirlo collects them, finds the cause and hands your agent the task.
No credit card · Set up in minutes