● The AI maintenance engineerBuilt in Brussels

Every request your product gets, investigated and answered.

Deflekt listens to your customers, your errors and your own data. It investigates in your code and in production, then hands your team the answer: a reply, a console command, or a fix tested side by side and ready to merge.

HUMAN
APPROVED
Deflekt never acts on production alone. Every reply, command and fix waits for someone on your team to approve it.
Case #5172, as Deflekt handled it. Captions included.
§ 1 · The maintenance tax

Shipping is half the job. The other half lands in your inbox.

Most of a product's cost comes after launch. It arrives from four directions, and today every one of them ends up on a developer's desk.

i.

Customer tickets

In every language, with screenshots, often about something that broke for a single account.The export is empty again.

ii.

Errors and alerts

Stack traces with no customer attached, piling up until someone finds the time to look.NoMethodError, 340 events.

iii.

Silent data bugs

A feature stops writing, a column goes empty. No error, no ticket, until a customer notices weeks later.Nobody reports what nobody sees.

iv.

Questions and requests

Sales, support and ops asking how the product behaves, or for a small change, in a Slack thread.Do we already send a reminder before the due date?

Each one costs a developer an hour of context switching. Deflekt takes the hour.

§ 2 · Anatomy of a case

Listen. Investigate. Act. Prove. Remember.

Follow one case from the first message to the merged fix. Deflekt does this hundreds of times a week, and never gets tired of the queue.

08:42 · 01 Listen

Every signal, one queue.

Tickets, issues, errors and questions arrive as they happen, through webhooks or a click in your browser. Duplicates are grouped, so twelve reports of one bug become one investigation.

  • Help desks, issue trackers, error monitoring
  • Browser extension on any ticket, issue or pull request
  • Manual requests with attachments, from anyone
Incominglast hour
FreshdeskTwee keer afgeschreven deze maandUrgent
ZendeskDouble prélèvement sur ma carteGrouped
SentryTimeout in PaymentWebhook×212
SlackCan we add the VAT number to exports?Request
Data Watchcharges per renewal rose to 2Anomaly
08:43 · 02 Investigate

Reads the code. Checks the data.

Deflekt does what your best engineer would do before answering: search the codebase, query production read only, look at recent pull requests, the error tracker and the customer's whole history. Then it sets a priority from evidence, not from who shouted loudest.

  • Read only access to databases, payments and email logs
  • Screenshots, PDFs, CSVs and logs understood
  • Data loss, money and blocked customers first
Investigationcase #5172
# who is asking
Van Damme Bouw · customer since 2021 · plan Pro
# payments, read only
renewals charged more than once since Oct 31
→ 38 subscriptions · €4,218.40 · 1 complaint
# code and history
payment_webhook.rb:27 lost its idempotency key in PR #2214
# verdict
bug · urgent · money taken wrongly, 37 unaware
08:47 · 03 Act

The right answer, in the right form.

Not every ticket needs a fix. Deflekt picks what does the job: a reply in the customer's language and your tone, an internal note, a precise console command, or a pull request across every repository the fix touches. When one complaint hides thirty seven silent ones, it prepares the answer for all of them.

  • Replies in any language, the way your team writes
  • Ready to run scripts: refunds, data repairs, unblocks
  • Fixes across backend, frontend and mobile
Suggested replyHigh confidence
Dag Pieter,

U heeft gelijk: uw abonnement werd op 31 oktober twee keer afgeschreven, door een fout aan onze kant. Het dubbele bedrag wordt u terugbetaald en staat binnen drie werkdagen op uw rekening. Onze excuses.
Drafted in your team's voice
+ refund script, 38 payments+ email to the 37 others
08:51 · 04 Prove

A fix you can trust before you read it.

Generating a fix is the easy part now. Deflekt runs two environments on the same data, one with the bug and one with the fix, and records both in a real browser. The recording plays inside the pull request. Reviewer comments and failing CI are handled in further rounds.

  • Side by side environments, recorded
  • Your test suite runs before anyone reviews
  • Review comments and CI failures addressed
PR #2231QA recording
Beforemain
2×
charged, webhook replayed
Afterfix
1×
charged, webhook replayed
tests passingrecorded2 review rounds
Later · 05 Remember

The knowledge stays when people leave.

Every case becomes context for the next one. Deflekt learns why that workaround exists in the billing code, who each customer is, and which answers your team corrected. It knows when to look again, and closes tickets once the customer has gone quiet.

  • Product memory built from every resolved case
  • A file per customer and contact
  • Follow ups with a date and a reason
Memorybilling
Learned from #5172code

The payment provider retries webhooks up to ten times. Every payment handler must be idempotent.

Customer filepeople

Van Damme Bouw: refunded on Nov 2. Mention it if they write again.

Follow upNov 5

The 38 refunds should have settled by then. Check, then close.

§ 3 · Watch

Catches what nobody reports.

The worst problems never reach your help desk. Deflekt watches for them and opens the case before a customer has to.

exports.rows_written / day30d
▲ stopped writing 2 days ago · no error raised

Data Watch

Nightly probes of your own database. A feature that stops writing, a column that suddenly goes empty, a status nobody has seen before. The data shows the bug first.

Silent data bugs →
RegulatorElectronic invoicing mandatory from Jan 1Affects you
StripeAPI version deprecatedCheck
Bank APIChangelog silent for 90 daysStale

Regulatory and partner watch

The worst tickets were announced in public months before they arrived. Deflekt reads regulator feeds and partner changelogs in any language, judges each item against your product, and learns from what you dismiss.

Regulatory changes →
SentryTimeoutError in BankSyncJobRising
Linked3 tickets about missing transactionsSame cause
DeflektCase opened, fix proposedPR ready

Errors with a story

Errors are linked to the customers they hurt and the tickets they cause. A rising error becomes one case with a fix, instead of a dashboard nobody opens.

Deflekt for Sentry →
§ 4 · Any request, from anyone

Your whole company can ask it.

Sales, support and ops get answers from the code and the data, with the source cited, without interrupting an engineer.

Feature requests are checked against what already exists, scoped in the code, and turned into a clear spec. Small ones come with a pull request.†

Works with the coding agents you already use.

Deflekt doesn't replace your IDE or your coding agent. It decides what is worth building, hands the agent the full context, and checks the result.

Claude Code / Codex / Cursor / any MCP client
Deflekt vs coding agents →

† And when you say go, it builds the whole feature: code across your repositories, tests, recorded QA, a pull request ready to review. We just think deciding what to build is the harder part.

Sarah · Sales
Do we already send a reminder before an invoice is due? A prospect is asking.
Deflekt
Yes, 3 days before the due date, but only when the customer turned reminders on. 41% of active accounts have.due_date_reminder_job.rb:12
Tom · Support
Could customers choose 7 days instead?
Deflekt
The delay is hardcoded. Making it a setting touches 3 files and one migration. Spec written, pull request ready for review.spec #212 · PR #1851
§ 5 · Daily briefing

Start the day knowing what matters.

Not a list of tickets. A front page: the pattern behind the queue, what is ready to ship, what needs a decision, and the one thing to do first.

The Morning Brief
Lead story

One complaint, thirty eight victims.

A single customer wrote in about a double charge. Deflekt found thirty eight subscriptions charged twice since Thursday's deploy, €4,218 in total. The fix is written, tested and recorded side by side. Approve the refund script first, merge pull request 2231, then send the email already drafted for the thirty seven customers who have not noticed yet. Everything else today can wait an hour.

Ready to ship

Twenty minutes of approvals

  • 14 replies ready to send
  • 3 fixes with passing tests and recordings
  • 2 commands to unblock single accounts
Needs a decision

Two calls for the team

  • Export with VAT number, asked by 4 customers
  • Jan 1 regulation changes invoice numbering
DashboardEvery case, its status and its proposed answer
Browser extensionThe analysis next to the ticket you are reading
Pull requestsFixes, recordings and review rounds
MCPAsk Deflekt from your own AI tools
§ 6 · Integrations

Plugs into the stack you already run.

Deflekt reads where requests arrive, where your code lives and where your data sits.

Help desks
Freshdesk /Zendesk /Intercom /Help Scout /HubSpot /Front /Email
Issue trackers
Jira /Linear /GitHub Issues /GitLab Issues /Gitea Issues /Asana
Errors
Sentry /Rollbar /Bugsnag /Datadog /New Relic /Honeybadger
Code and CI
GitHub /GitLab /Gitea /Bitbucket /Azure DevOps /GitHub Actions /GitLab CI
Data, read only
PostgreSQL /MySQL /Metabase /BigQuery /Snowflake /Stripe /Mollie /Postmark /SendGrid
Team
Slack /Microsoft Teams /Notion /Confluence /Claude Code /Codex /MCP
Using something else? Tell us, it will be connected before you start.Ask for a connector →
§ 7 · House rules

Your code stays yours.

Deflekt touches your codebase and your customers' data. It is built so you never have to take that on faith.

Rule 01

Humans approve, always.

Replies are drafts, fixes are pull requests, commands are suggestions. Nothing reaches a customer or production without your team.

Rule 02

Production is read only.

Database and third party access is read only, with credentials encrypted at rest and scoped per project.

Rule 03

Customer text is data.

Ticket content is treated as untrusted input, never as instructions, so a crafted message cannot steer the agent.

Deflekt hub
Dashboard, briefing, memoryHosted by us, or on your infrastructure
jobs and results →
← never source code
Your network
Workers: code, tests, QAYour source code never leaves it.
§ 8 · In production
“I used to spend three hours a day on support, in a language I don't speak. Now it's fifteen minutes of approving what Deflekt prepared.”
Ihcène Medjber, founder · running Deflekt daily on a Belgian SaaS with thousands of users
3h → 15mdaily time spent on the queue
~2 minfrom ticket to full investigation
NL FR ENreplies drafted in the customer's language
Mar 2026in daily production since
§ 9 · Questions
How is this different from Cursor, Claude Code or Devin?

Those tools help a developer who already sat down to build something. Deflekt works before that moment: it receives requests from people who don't code, investigates them in your code and data, and decides whether the answer is a reply, a command or a change. When code is needed it can use the same agents, and it adds what they lack: customer context, production data, proof and memory. Full comparison.

How is it different from AI support agents like Intercom Fin?

Support agents answer from your help center and close conversations. Deflekt goes into the code and the data to find the real cause, and fixes bugs instead of explaining them. It works alongside your support team and your help desk. Full comparison.

Does it change anything in production on its own?

No. Deflekt reads production, it never writes to it. Fixes go through pull requests, your tests and your review. Console commands are prepared for a human to run.

Where does my code run?

Workers that read code, run tests and record QA run on your infrastructure. The hub only stores analyses and results. A fully self hosted setup is available.

Which languages and stacks does it support?

Any language your customers write in, and any stack your engineers work in. It runs daily on Rails, React and React Native codebases, with tickets in Dutch, French and English.

Can it build features, not just fix bugs?

Yes. Once a request is scoped and your team approves the spec, Deflekt implements it the same way it ships fixes: across every repository involved, with tests, a recorded before and after, and review rounds on the pull request. It is simply not where we think most of the value is.

How much does it cost?

We are onboarding a small group of design partners: we set Deflekt up on your stack and tune it with you. Pricing depends on the size of your team and is discussed on the first call.

§ 10 · Who builds it

Ihcène Medjber

Founder
Lead backend engineer
MSc Computational Biology

Fifteen years building SaaS products, at Silverfin and Cowboy and as CTO of Cureety. Deflekt started as a script to survive a support queue in a language I don't speak, and grew into the engineer every small product team is missing.

Give your engineers their roadmap back.