When it comes to running Ceramic nodes for HireNodes, optimizing resource utilization is crucial for achieving optimal performance and reliability. One key aspect of this optimization is the decision of whether to use the bundled option or to break the IPFS (InterPlanetary File System) out into a separate container. In this article, we will explore why separating IPFS into a separate container is of utmost importance and how it contributes to maximizing resource efficiency.

Understanding Ceramic and IPFS:

Before delving into the significance of separating IPFS, let’s briefly touch upon the concepts of Ceramic and IPFS.

Ceramic is a decentralized protocol built on top of IPFS that enables the creation, management, and sharing of immutable and verifiable data across various applications. It provides a reliable infrastructure for developers to build decentralized applications (dApps) with robust data integrity and interoperability.

IPFS, on the other hand, is a peer-to-peer distributed file system that allows content-addressed storage and retrieval of data across a decentralized network. It serves as the underlying layer for Ceramic, providing the storage and distribution mechanisms necessary for its operation.

The Importance of Separating IPFS:

  1. Isolation and Modularity: By separating IPFS into a separate container, you establish isolation and modularity within your infrastructure. Each component operates independently, reducing potential conflicts and enhancing the overall stability of your system. Separation allows you to upgrade or modify the IPFS container without impacting other components of your Ceramic node setup.
  2. Resource Utilization: Resource utilization is a critical aspect of any infrastructure. When IPFS is bundled within the same container as the Ceramic node, it competes for system resources such as CPU, memory, and disk space. This competition can lead to resource contention, resulting in performance degradation and inefficiencies. By running IPFS in a separate container, you can allocate resources specifically tailored to its needs, optimizing its performance and preventing resource conflicts with the Ceramic node.
  3. Scalability and Flexibility: Separating IPFS into its own container provides enhanced scalability and flexibility. As your Ceramic node network grows, you can easily scale the IPFS container independently from the Ceramic node containers. This scalability ensures that you can accommodate increasing storage demands and higher network loads without impacting the overall system performance.
  4. Fault Isolation: In the event of a failure or issue within IPFS, having it separated into a distinct container allows for better fault isolation. If IPFS encounters a problem, it won’t affect the availability or functionality of the Ceramic node. This isolation ensures that the Ceramic node can continue operating without disruption, mitigating potential downtime and ensuring a seamless experience for users.


When running Ceramic nodes for HireNodes, optimizing resource utilization is paramount. Separating IPFS into a separate container provides numerous benefits, including isolation and modularity, improved resource utilization, scalability, flexibility, and fault isolation. By taking this approach, you can ensure that your Ceramic nodes perform optimally and maintain a high level of reliability and efficiency.

This is why HireNodes always runs IPFS separate from the rest of the Ceramic stack even when working on TestNet.