Developer Tools · Integration
OpenStack
Add OpenStack to your product for your customers, and give your AI agents governed access to it.
Embed an OpenStack integration so your product can see and act on the infrastructure a customer runs in their own private cloud rather than only the public clouds. OpenStack is the open-source platform behind a great many private and telco clouds, and the resources operators work with are compute instances, block storage volumes, networks and floating IPs, object storage containers and the projects and quotas that bound them. Each customer supplies their own identity endpoint, project and credentials, so every call runs under their own account and stays inside their cloud. fastn owns the credential storage, token refresh, retries, pagination and API upkeep, and the same governed connection is what your AI agents use.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own OpenStack cloud so your product can inventory their instances, volumes and networks with no per-customer code.
Start, stop or resize an instance from your product within the permissions the customer granted, rather than sending them to a console.
Read project quotas and usage per tenant so your product can show what capacity is left before it schedules more work.
Support customers on different OpenStack distributions and releases as per-tenant configuration instead of a branch in your code.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent lists the instances and volumes behind a problem before anyone opens a console, reading only that customer's cloud.
An agent restarts a failed instance within scoped permissions, with the action attributed and audited.
An agent reports which projects are close to their quota so a team can act before a deploy fails.
Example prompt
Which instances in our OpenStack project are stopped but still holding attached volumes?
Set up OpenStack in 4 steps
- 01Enable the OpenStack connector in your fastn dashboard.
- 02Have each customer supply their identity endpoint, project and credentials so calls run inside their own cloud.
- 03Map the instance, volume, network and project fields your product uses, per customer.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the OpenStack integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an OpenStack integration without building it. Your customers connect their own OpenStack 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 an OpenStack update is not your on-call problem.
- One integration serves your product and your agents. The same governed OpenStack 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
Amazon EC2
Azure Virtual MachinesWorks well with
AnsibleOften used alongside
Tools the same teams tend to run next to OpenStack, across other categories.
Slack
Snowflake
Airtable
PostgreSQLOpenStack integration FAQ
How do I add an OpenStack integration to my product?
Enable the OpenStack connector in your fastn dashboard, then let each customer authenticate their own OpenStack account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no OpenStack client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own OpenStack account?
Yes. Every connection is scoped to the individual customer, so each authorises their own OpenStack 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 OpenStack 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 the instances and volumes behind a problem before anyone opens a console, reading only that customer's cloud.
Who maintains the OpenStack integration?
fastn does. When OpenStack 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 OpenStack 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 OpenStack?
Yes, within scoped permissions, and every action is audited so an agent's changes are attributable.
What can I build with the OpenStack integration?
A common starting point: let each customer connect their own OpenStack cloud so your product can inventory their instances, volumes and networks with no per-customer code. 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 OpenStack integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding OpenStack does not change your per-connector cost. You can start free with 3 connected accounts.
Add OpenStack to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.