Developer Tools · Integration
Quali Torque
Add Quali Torque to your product for your customers, and give your AI agents governed access to it.
Torque, from Quali, treats a whole environment as the unit rather than a single resource. A blueprint written as code in the customer's own repository describes the infrastructure, the applications and the dependencies that have to come up together, and launching it produces an environment in a space, owned by somebody, tagged, costed and usually given a lease that ends it automatically. An embedded Quali Torque integration launches environments from the blueprints a customer already publishes to their catalog, reads what is currently running and who owns it, extends or terminates a lease, and reads the cost attributed to each one. Environments are slow and expensive compared with an API call, so a launch is asynchronous and a product that waits synchronously on one will time out. Each customer's credentials stay with fastn, bound to them alone, and the connector absorbs platform changes.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Torque account so your product can provision an environment without owning their cloud credentials.
Launch an environment from a blueprint the customer already published, with the inputs your product supplies rather than a fixed template.
Poll a launch to completion instead of blocking on it, because standing up infrastructure takes minutes rather than milliseconds.
Extend or end a lease from your product so environments that are still needed survive and the rest stop costing money.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent lists which environments are running, who owns each and when its lease expires.
An agent launches or terminates an environment within scoped permissions, with the blueprint and space it used recorded.
An agent explains which running environments are driving cost and which have been idle since they were created.
Example prompt
Which environments are still running past their lease, who owns them, and what are they costing us?
Set up Quali Torque in 4 steps
- 01Enable the Quali Torque connector in your fastn dashboard.
- 02Have each customer supply credentials for their own account and confirm which spaces your product may launch into.
- 03Map the blueprints and inputs your product uses, then decide how launches are polled and how leases are set.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Quali Torque integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Quali Torque integration without building it. Your customers connect their own Quali Torque account inside your product and work their services, builds and deployments there, with no per-customer code on your side.
- Handle the part that actually costs time: these systems emit a lot of webhooks, and replay after downtime has to be handled. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Quali Torque update is not your on-call problem.
- One integration serves your product and your agents. The same governed Quali Torque connection powers in-product features and gives AI agents scoped, audited access, so you connect engineering activity to the rest of the business without wiring it twice.
Used by these teams
Compare with
Octopus Deploy
Jenkins
GitHubOften used alongside
Tools the same teams tend to run next to Quali Torque, across other categories.
Slack
Snowflake
Airtable
PostgreSQLQuali Torque integration FAQ
How do I add a Quali Torque integration to my product?
Enable the Quali Torque connector in your fastn dashboard, then let each customer authenticate their own Quali Torque account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Quali Torque client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Quali Torque account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Quali Torque account and only ever sees their own services, builds and deployments. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Quali Torque integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent lists which environments are running, who owns each and when its lease expires.
Who maintains the Quali Torque integration?
fastn does. When Quali Torque changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can I react to Quali Torque events in real time?
Yes, through event triggers. Events are delivered per tenant and can be replayed after an outage, so a webhook missed during downtime is not silently lost.
Can an agent open or update items in Quali Torque?
Yes, within scoped permissions, and every action is audited so an agent's changes are attributable.
What can I build with the Quali Torque integration?
A common starting point: let each customer connect their own Torque account so your product can provision an environment without owning their cloud credentials. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Quali Torque integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Quali Torque does not change your per-connector cost. You can start free with 3 connected accounts.
Add Quali Torque to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.