SOC 2 Type II audit in progress · EU, US and India data residency · a DPA you can sign
Trust Center →Agents
Three agents, one ticket.
FlowTux is not one model answering questions. Each stage of a ticket has a named agent with its own job and its own limits, and the same three run on every channel — Slack, email, WhatsApp and your error trackers. Across our published customers, 50% of tickets finish without a person.
Repo Agent
Reads the linked repository for the likely cause and attaches the probable files — the step most helpdesks skip entirely.
Reads GitHub · GitLabTriage Agent
Sets category, priority and owner from real impact — not from the words the reporter happened to choose.
Writes Jira · PagerDutyResolution Agent
Runs the fix if it is on your allow-list, verifies it, and closes the ticket with the action written to the audit log.
Gated by your allow-list
Only one of them can change anything.
The Repo and Triage agents read and annotate; they never act. The Resolution Agent is the only one that runs a fix, and it is gated by an allow-list you control — it starts narrow, widens as the audit log earns your trust, and fails closed on anything outside it.