Data & Storage · Integration
Redis
Add Redis to your product for your customers, and give your AI agents governed access to it.
Redis holds working state rather than a system of record, and an embedded Redis integration is how your product uses a customer's own instance for that state instead of you running one per tenant. The data model is keys and the structures behind them, so strings, hashes, lists, sets, sorted sets and streams, addressed by key name and never queried with SQL. Volatility is the defining fact and the thing most integrations get wrong. A key can carry a TTL and expire, and under memory pressure an eviction policy can remove a key nobody expected to lose, so every read your product makes has to tolerate the key simply not being there. fastn holds the connection credentials per tenant and keeps the command surface current.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer supply their own instance so your product caches per-tenant working state in memory they already pay for.
Use a sorted set to maintain a leaderboard or recency ranking your product renders, updated as events arrive.
Consume a stream so work published by the customer's own services is picked up by your product in order.
Set TTLs deliberately and treat a missing key as a normal outcome rather than an error to page on.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads a key or a hash field to check current state before it decides what to do.
An agent writes a value with an expiry it has been permitted to set, and the key it touched is logged.
An agent reads from a stream to see what has happened recently, scoped to that tenant's instance.
Example prompt
Check the cached session hash for this user and tell me how long before it expires.
Set up Redis in 4 steps
- 01Enable the Redis connector from your fastn dashboard.
- 02Have each customer authorise their own Redis instance, so commands run under their credentials rather than a shared connection.
- 03Map the keys, hashes, sorted sets and streams your product touches, and decide what a missing or expired key should mean.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Redis integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Redis integration without building it. Your customers connect their own Redis 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 a Redis update is not your on-call problem.
- One integration serves your product and your agents. The same governed Redis 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
Couchbase Capella
MongoDB
PostgreSQLOften used alongside
Tools the same teams tend to run next to Redis, across other categories.
Anthropic Claude
OpenAI
Azure OpenAI
Hugging FaceRedis integration FAQ
How do I add a Redis integration to my product?
Enable the Redis connector in your fastn dashboard, then let each customer authenticate their own Redis account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Redis client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Redis account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Redis 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 Redis 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 reads a key or a hash field to check current state before it decides what to do.
Who maintains the Redis integration?
fastn does. When Redis 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 Redis 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 Redis 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 Redis integration?
A common starting point: let a customer supply their own instance so your product caches per-tenant working state in memory they already pay for. 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 Redis integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Redis does not change your per-connector cost. You can start free with 3 connected accounts.
Add Redis to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.