How do I deploy Kubo on Railway?

You can deploy Kubo on Railway by clicking the "Deploy Now" button on this page. Railway will automatically set up all the necessary services and configurations for you.

What are the system requirements?

Railway handles all the infrastructure requirements. You only need a web browser to deploy and manage your application.

Is this template free to use?

Yes, this template is free to use within your existing Railway account.

Can I customize this template?

Yes, you can fully customize this template. After deployment, you will have full control of what you've deployed in your Railway project.

How do I get support for this template?

You can get support through our community forum: kubo-45b3d189, or click "Get template help" for this template for more assistance.

Kubo logo

Deploy and Host IPFS Kubo on Railway

Kubo is the reference Go implementation of IPFS, providing content-addressed storage, retrieval, and peer-to-peer data distribution. This template deploys a production-ready Kubo node on Railway with sensible defaults and an easy path to scaling.

IPFS Web UI status page

About Hosting IPFS Kubo

Kubo runs as a single service that exposes IPFS HTTP APIs and gateway endpoints while participating in the IPFS network for content discovery and distribution. It stores blocks locally, advertises content via libp2p, and can retrieve content from any peer that has it. Railway makes it simple to deploy Kubo without managing servers, while enabling vertical scaling and persistent storage for your node’s data.

Common Use Cases

Content-addressed storage for apps and files
Decentralized asset delivery (images, media, artifacts)
Immutable data snapshots and backups
P2P data exchange and content distribution

Dependencies for IPFS Kubo Hosting

The Railway template includes all required dependencies: the Kubo runtime and persistent storage for the IPFS repository. No additional databases are required.

Deployment Dependencies

None. The template includes everything needed to run Kubo.

Implementation Details

Architecture Components

This template deploys one service:

Kubo Node: IPFS daemon exposing the HTTP API and optional gateway

Node Configuration

Kubo maintains a local repository for blocks and metadata. It participates in the IPFS DHT for peer discovery and can pin content to keep it available. The template can be configured via environment variables and Kubo config flags to control gateway access, API exposure, and datastore size.

Service Configuration

API Endpoint: For adding, pinning, and retrieving content
Gateway Endpoint: For HTTP access to IPFS content
Scaling: Vertically scale the service for more CPU/RAM; use persistent storage for larger datasets

License Information

Kubo is open-source under the MIT license. See the Kubo repository for full license details.

Why Deploy IPFS Kubo on Railway?

By deploying IPFS Kubo on Railway, you can add decentralized storage and content distribution to your stack with minimal operational overhead.

Notes

Source repo: https://github.com/FournyP/kubo-railway-template
Docs: https://docs.ipfs.tech/how-to