Ceramic is a decentralized data network built on a protocol for mutable event streams anchored to Ethereum blockchain. It enables composable, verifiable data infrastructure for Web3 applications — supporting 400+ apps, 10 million streams, and 350 million events across the network.
Ceramic organizes data as cryptographically signed events chained into streams. Decentralized Identifiers (DIDs) serve as the identity layer, letting users control their own data without central authorities. Global event ordering is achieved by periodically anchoring Merkle tree roots to Ethereum via the Ceramic Anchor Service (CAS).
- Ceramic HTTP API — REST API for streams, events, interests, feed, peers, and node configuration (OpenAPI 3.0, v0.58.0)
POST /ceramic/events— Publish a new event to the networkGET /ceramic/events/{event_id}— Retrieve an event by CIDGET /ceramic/streams/{stream_id}— Get current stream statePOST /ceramic/interests— Register interest in a data model/streamGET /ceramic/feed/events— Poll the ordered event feed with resume token supportGET /ceramic/feed/resumeToken— Get current highwater mark for the event feedGET /ceramic/config/network— Get network infoGET /ceramic/liveness— Node health checkGET /ceramic/version— Node versionGET /ceramic/peers— List connected peersPOST /ceramic/peers— Connect to a peer
- Documentation: https://developers.ceramic.network/
- GitHub: https://github.com/ceramicnetwork
- Discord: https://chat.ceramic.network/
- Forum: https://forum.ceramic.network/
- Blog: https://blog.ceramic.network/
- Twitter: https://twitter.com/ceramicnetwork
Ceramic is a self-hosted protocol. Operators run their own ceramic-one Rust daemon (default port 5101) plus js-ceramic, Postgres, and an Ethereum RPC provider for anchoring. Estimated costs range from ~$106/month for small apps to ~$967/month for high-traffic deployments.
- Terms of Service: https://ceramic.network/terms-of-service
- Privacy Policy: https://ceramic.network/privacy-policy
Maintained by API Evangelist