Technical requirements to run Ceramic | Ceramic documentation

Overview

To understand the expected costs to integrate Ceramic into your architecture, it is helpful to first understand where Ceramic lives in the application architecture stack.

Ceramic is a decentralized data storage network made up of different components, and can replace or augment existing storage solutions.

When integrating with Ceramic, you will be running a few different services and components, each serving a specific purpose for running your application:

• ceramic-one - the Ceramic node written in Rust, responsible for storing data, providing HTTP API access, and coordinating with network participants
• EVM RPC node access - required for self-anchoring to EVM blockchains (optional, but recommended for production)

With self-anchoring support, you can run your own anchor service on any EVM-compatible blockchain instead of relying on external services. See Self-Anchoring for more details.

Hardware requirements

Depending on the expected throughput of your project, the suggested hardware requirements will differ. Below, you can find the estimated hardware requirements based on different levels of expected throughput.

Minimum (light throughput)