SOC 2 Type II audit in progress · EU, US and India data residency · a DPA you can sign
Trust Center →How it works
One ticket, from the message to the fix.
FlowTux takes a request the moment it is made and runs it all the way down — deduped, read, triaged and closed — stopping only at the single question that needs a person. Across our first three customers, 50% never need one.
- Fails closed
- Nothing closes unverified
- Every action logged
“VPN won’t connect since this morning — anyone else?”
✓ 12:04 · restored vpn-gateway · verified · closed · logged
The request lands where it was made.
Someone reports a problem in the tool they already had open. No portal to visit, no form to fill in — which is what stops requests leaking into DMs.
Duplicates collapse into one ticket.
One outage gets reported by eight people in slightly different words. They fold into a single ticket, so the queue shows one incident with one owner instead of eight.
It reads the codebase, not just the error.
For anything code-adjacent, the linked repository is searched for the likely cause and the probable files are attached. This is the step most helpdesks skip entirely.
Category, priority and owner are set.
Priority comes from real impact rather than the words the reporter chose. The ticket reaches the queue already sorted and assigned, before a person has opened it.
Did you approve this kind of work?
You decide what FlowTux may act on by itself. The list starts narrow and widens as the audit log earns your trust. Anything not on it goes to a person — the gate fails closed.
Fixed, verified, and written down.
The fix runs, gets checked, and the ticket closes with the action written to the audit log. Nothing closes that could not be verified. The requester has an answer before they switch tabs.
“VPN won’t connect since this morning — anyone else?”
✓ 12:04 · restored vpn-gateway · verified · closed · logged
Never, however wide the list opens
Four things it will not do.
- Act on a system you have not approved
- Make a judgement call about a person
- Run a command that is not on the list
- Close anything it could not verify
Watch it happen on one of your tickets.
Fifteen minutes. We take a real ticket from your queue and run it down this exact path, start to close. No slides.
Teams sit between 41–58% depending on how wide they open the allow-list — that spread is the list, not the AI.