Self-Managed Feeds
Self-managed feeds are Data Feeds where values are written onchain by a third party (typically the chain or its designated operator), not by Chainlink node operators publishing through Chainlink Labs–managed oracle infrastructure.
At a high level, a Chainlink Runtime Environment (CRE) workflow reads from Chainlink Data Streams and writes updates to a proxy contract so consumers can read answers using the same familiar Data Feeds interfaces. Chainlink Labs does not manage the onchain publication path, monitoring, or service levels for these deployments. The chain (or its operator) is responsible for running the workflow, maintaining contracts, and supporting integrators.
As of March 2026, Jovay and Pharos offer self-managed feed deployments. Contract addresses for these feeds are not listed in Chainlink public documentation; obtain deployed proxy addresses directly from those networks or their operators:
Responsibilities & guarantees
Data quality
Data for assets are delivered through Chainlink Data Streams. Data Streams provides the offchain data for the self-managed feeds; however, it is the third party’s obligation to read, transform, or write the correct values onchain on schedule.
Monitoring & service levels
These onchain feeds are not managed or monitored by Chainlink Labs.
Specifically:
- Chainlink Labs does not provide monitoring for:
- Heartbeat compliance
- Deviation compliance
- End-to-end latency of writing prices onchain
- Whether the correct data was written onchain
- No service level agreements (SLAs) are provided for self-managed feed publication.
- No onchain monitoring specific to these feeds is provided by Chainlink Labs.
Feed visibility
- Proxy addresses for self-managed feeds do not appear on official Chainlink public documentation sites (including feed address catalogs).
- Integrators must obtain deployed contract addresses directly from the operators of the self-managed feeds on each chain.