IT Operations · Integration
Lucidity
Add Lucidity to your product for your customers, and give your AI agents governed access to it.
Embed a Lucidity integration so cloud block storage utilisation and spend appear alongside the infrastructure your product already shows, without you building against three cloud providers yourself. Lucidity manages and right-sizes block storage across AWS, Azure and Google Cloud, so one connection covers customers on any of them. Each customer connects their own account, reads are scoped per tenant, and alerts arrive through event triggers rather than polling and are deduplicated so a noisy volume does not create a queue of identical records. fastn owns the credentials, retries and API upkeep, and the same governed connection serves your AI agents.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers connect their own Lucidity account so disk utilisation and storage spend appear next to the infrastructure your product shows.
Read volume level utilisation per tenant so your product can flag a disk heading for full before an application notices.
React to a Lucidity alert with an event trigger so a ticket or change request opens without anyone watching a dashboard.
Cover customers on AWS, Azure and Google Cloud through one connection instead of three integrations of your own.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent explains why a customer's storage bill moved by reading their own utilisation data.
An agent reports which volumes are over-provisioned for one tenant, with each read audited.
An agent triages a storage alert and gathers the context a human needs before approving a change.
Example prompt
Which volumes in this account are over-provisioned in Lucidity, and what would right-sizing save?
Set up Lucidity in 4 steps
- 01Enable the Lucidity connector in your fastn dashboard.
- 02Have each customer authorise their own Lucidity account so calls run under their credentials.
- 03Map the utilisation and cost fields your product surfaces, then enable the alert triggers you need.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Lucidity integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Lucidity integration without building it. Your customers connect their own Lucidity account inside your product and work their incidents, alerts and on-call schedules there, with no per-customer code on your side.
- Handle the part that actually costs time: alerting is latency-critical and noisy, so filtering and deduplication matter. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Lucidity update is not your on-call problem.
- One integration serves your product and your agents. The same governed Lucidity connection powers in-product features and gives AI agents scoped, audited access, so you route operational signal to the people and systems that act on it without wiring it twice.
Used by these teams
Compare with
AWS CloudWatch
Azure Monitor
DatadogOften used alongside
Tools the same teams tend to run next to Lucidity, across other categories.
AppViewXLucidity integration FAQ
How do I add a Lucidity integration to my product?
Enable the Lucidity connector in your fastn dashboard, then let each customer authenticate their own Lucidity account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Lucidity client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Lucidity account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Lucidity account and only ever sees their own incidents, alerts and on-call schedules. 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 Lucidity 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 explains why a customer's storage bill moved by reading their own utilisation data.
Who maintains the Lucidity integration?
fastn does. When Lucidity 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.
How fast does a Lucidity alert reach my product?
Alerts arrive through event triggers rather than polling, so your product reacts in near real time instead of on a schedule.
Can duplicate or flapping alerts be suppressed?
Yes. Events are deduplicated per incident, so a flapping check does not create a queue of identical records for your users to sift through.
What can I build with the Lucidity integration?
A common starting point: connect their own Lucidity account so disk utilisation and storage spend appear next to the infrastructure your product shows. 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 Lucidity integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Lucidity does not change your per-connector cost. You can start free with 3 connected accounts.
Add Lucidity to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.