Data & Storage · Integration
Astra
Add Astra to your product for your customers, and give your AI agents governed access to it.
Embed an Astra integration so your customers can read and write their own Astra databases from inside your product, and so your agents can query them under per-tenant governance. Schemas differ per customer and change without notice, so table and field mapping is configuration rather than code, and pagination and throttling on large reads are handled for you. fastn holds each customer's credentials and maintains the API upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers connect their own Astra database so queries run under their credentials.
Read rows and documents into your product, mapped to your own data model.
Write and update records from your product without a per-customer integration build.
Read schema at runtime so your product adapts when a customer's tables change.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent queries a table for the rows it needs before answering a question.
An agent inserts or updates a record within governed permissions, with the write logged.
An agent reacts to new data and runs the next step of a workflow.
Example prompt
Query the events table for records written in the last hour and summarise them by type.
Set up Astra in 4 steps
- 01Open the Astra connector from your fastn dashboard.
- 02Have each customer authenticate their own Astra database with a scoped token.
- 03Map the tables and fields your product reads and writes, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Astra integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an Astra integration without building it. Your customers connect their own Astra account inside your product and work their records, datasets and fields there, with no per-customer code on your side.
- Handle the part that actually costs time: schemas differ per customer and change without notice, and volumes can be large. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so an Astra update is not your on-call problem.
- One integration serves your product and your agents. The same governed Astra connection powers in-product features and gives AI agents scoped, audited access, so you read and write your customers' data where it already lives without wiring it twice.
Used by these teams
Compare with
PostgreSQL
AirtableWorks well with
NotionOften used alongside
Tools the same teams tend to run next to Astra, across other categories.
Anthropic Claude
OpenAI
Azure OpenAI
Hugging FaceAstra integration FAQ
How do I add an Astra integration to my product?
Enable the Astra connector in your fastn dashboard, then let each customer authenticate their own Astra account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Astra client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Astra account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Astra account and only ever sees their own records, datasets and fields. 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 Astra 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 queries a table for the rows it needs before answering a question.
Who maintains the Astra integration?
fastn does. When Astra 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.
Does the Astra integration adapt when a customer's schema changes?
Schema and field mapping is configuration per customer, so a change on their side is a mapping update rather than a code change and a release on yours.
How are large Astra reads handled?
Pagination and throttling are handled for you, and initial backfills are rate-limited so a large import does not exhaust a customer's API allowance.
What can I build with the Astra integration?
A common starting point: connect their own Astra database so queries run under their 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 Astra integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Astra does not change your per-connector cost. You can start free with 3 connected accounts.
Add Astra to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.