AI does the work. Your people keep the decisions.
FixControl is a governance layer that runs on top of the tools you already use. AI classifies, drafts, and proposes; policy and sandbox verification check the work; someone on your team approves anything that reaches your customers, a repository, or production. Every decision is recorded.
How FixControl works
FixControl brings the right information together per project, deploys specialized agents to prepare work, and checks what may happen next.
Read the video transcript (in Dutch)
AI kent uw organisatie niet vanzelf
AI kan veel, maar weet niet automatisch wat er binnen uw organisatie speelt.
Informatie staat verspreid over tickets, code, gesprekken en documenten.
De juiste informatie per project
FixControl koppelt per project alleen de bronnen die daarbij horen.
Gespecialiseerde AI-agents bereiden werk voor
Gespecialiseerde AI-agents onderzoeken het probleem, analyseren relevante code en documentatie, en bereiden een antwoord, analyse of wijzigingsvoorstel voor.
Controle vóór actie
Daarna controleert FixControl welke regels gelden, of tests zijn geslaagd, welk risico is vastgesteld, en wie toestemming moet geven.
Een medewerker beslist
Een medewerker ziet het voorstel en de controles, en kan goedkeuren, afwijzen of een aanpassing vragen.
Uw systemen blijven de bron
Tickets, code en gesprekken blijven in de bestaande systemen.
Waar ingesteld worden goedkeuringen gedaan via Slack of Teams.
Pas na goedkeuring een pull request
Pas na de vereiste goedkeuring wordt de wijziging als pull request voorbereid.
Zo helpt FixControl u verder
Eerst de juiste informatie. Daarna een voorstel. Pas na controle een actie. Zo helpt FixControl u verder.
- Relevant sources per project
- Specialized agents per task
- Rules and checks before execution
- A human decision where needed
- A recorded decision
Four pieces, one control plane
Everything below is shipped and in the product today. Each piece feeds the next: context informs proposals, proposals carry evidence, decisions land in the ledger.
Support intelligence
Understand incidents using your documentation, past tickets and operational context. Ask about existing tickets in authenticated Slack, Teams or the in-app assistant instead of filing a new one.
Operational governance
An 8-domain policy engine sets risk tiers, approvers and limits per scope. AI operates inside those policies; consequential actions stop at approval gates.
Evidence engine
Every proposal carries the tickets, code and documentation it rests on, plus sandbox verification results — so an approver decides on evidence, not on trust.
Mission timeline
One replayable timeline per operation, from intake to delivery, separate from raw logs. Each decision links back to the evidence it was made on.
What it looks like
Real screenshots from the product on demo data — no mockups. These are the surfaces your team works in every day.
What is shipped, what is configured, what is planned
We label maturity rather than blur it. If something below says preview or roadmap, it is not sold as shipped.
In the product today
- Support → engineering workflow: intake, triage, proposed change, sandbox verification, approval gates, delivery as a pull or merge request
- Governed customer replies: AI drafts, someone on your team approves what is sent to Freshdesk, Odoo and TOPdesk — and to Jira Service Management where a customer-reply capability is configured and healthy. Direct e-mail to your customers is four-eyes approved: the requester never approves their own message, and any edit invalidates the approval
- Replies in your house style: signatures, reply templates and a tone policy, scoped per mailbox or user — off by default, you decide where they apply
- Ticket-question answering in authenticated Slack, Teams and the in-app assistant
- Ticket and customer management from chat: close, reopen or reprioritise tickets, assign colleagues, link customers — every change behind an explicit confirmation
- Customer management with governed communication: your customers linked to tickets and projects, and every direct e-mail to a customer staged for approval by a second person on your team
- Project roles and memberships: project work sits behind explicit membership and per-role permissions — deny-by-default, rolled out surface by surface
- Optional LLM-first chat understanding, per project: the model interprets the request — one message may ask for several things and lands on a single confirmation card with numbered steps; execution still waits behind that card and the approvals behind it
- Multiple support mailboxes per organisation (Gmail and Office 365), each linkable to its own project
- Sandbox verification for PHP stacks too — Laravel, WordPress, Symfony and Magento 2 — with a real database sidecar
- Approval ledger and hash-chained audit log with signed export
- OIDC SSO, SCIM 2.0 provisioning, built-in TOTP 2FA, tenant isolation via Postgres row-level security
Active only where you set it up
- Argo Rollouts deployment gates: an approval resumes a paused rollout; nothing promotes without a recorded decision
- CI/CD deployment gates (pilot): a pause your pipeline already holds — a GitHub Actions environment review, a GitLab deployment approval or manual job, a Jenkins input step — opens a FixControl approval, and the verdict executes through the host's own primitive
- FC Agent for private infrastructure (pilot): an outbound-only service in your own environment, so private Kubernetes, Argo, Jenkins and GitLab connect without being publicly exposed
- Jira Service Management customer-visible replies, per configured request type
- Jira reply mirroring and resolve-status push, opt-in per project
- Read-only database diagnostics (PostgreSQL), allowlisted and approval-gated
- Where configured, a proposed change is tested next to the database, cache and background services the application needs — started fresh for that one run, without internet access and without access to your source code, and cleaned up afterwards. Every passed run records the exact versions it passed against
Early, labelled as early
- DevOps observe-and-govern: pipeline and deployment event ingest with compliance export
Planned — not shipped
- SAML SSO (OIDC and SCIM are the shipped identity integrations; SAML is on the roadmap)
- Deployment execution beyond a recorded verdict on an existing pause — FixControl does not start, create or roll back deployments
- AI-assisted incident response
Built for teams that want AI with control
FixControl connects to sensitive operational systems, so every rollout gets guided onboarding: a clear scope, governance validation, and connection tests that prove each integration works before you rely on it — set up together with your team. Here's who gets the most out of it.
Support and engineering teams
Organizations evaluating governed AI workflows across a helpdesk, a tracker, chat and a code host — Freshdesk, Jira, Odoo or TOPdesk, Slack or Microsoft Teams, GitHub or GitLab.
Rollouts start with a pilot
A pilot defines the first workflows, integrations, approval gates and success criteria. After validation, teams expand usage across seats, integrations, action volume and additional governed workflows.
Not a replacement for your team
FixControl does not remove humans from the loop — it puts them at the decision points. Approvers remain responsible for what they approve.
What the AI may do on its own — and what it may not
Without approval, the AI classifies, summarizes, drafts, proposes, analyzes and prepares changes. Customer-visible replies, tracker comments that leave your own organization, pull requests and deployment promotions wait for an approval. And we do not promise hallucination-free AI — we put evidence and a person in front of every consequential action.
See a governed operation run end to end
A 15-minute walkthrough on demo data — no production systems required. Pilots start with one integration and clear boundaries.