What teams across fintech, dev tools, and infra are actually shipping
A look at the real work cyql handles every day — and the patterns that keep showing up across industries.
By The cyql team
A year in, we can see the shape of the work teams bring to cyql. It is not the glamorous stuff. It is the backlog that accumulates because nobody ever has a clean sprint for it.
Fintech teams use cyql for compliance-driven migrations — schema changes, field renames, audit-log additions — the kind of work that is well-defined but touches dozens of files and needs careful review. They set an approval gate on the plan, let the agents do the mechanical work, and spend their time on the diff instead of the typing.
Dev tools companies run cyql on their own internal infrastructure: keeping SDKs in sync with API changes, upgrading test harnesses, enforcing new linting rules across a monorepo. The work is repetitive and exactly specified, which is where agents shine.
Infrastructure teams lean on cyql for Terraform and Kubernetes work — adding new environments, rotating credentials, updating node pool configs. The isolation model matters here: an agent that can only touch what it needs to touch, for as long as the task takes, is a different kind of trust than a long-lived automation with standing access.
The through-line is follow-through. Not intelligence — follow-through. Every team has a list of things they know they should do and never get to. cyql is the team member that actually gets to them.