---
title: "Deploy Kubo"
description: "Deploy a Kubo server in railway"
category: "Storage"
url: https://railway.com/deploy/kubo
---

# Deploy Kubo

Deploy a Kubo server in railway

**[Deploy Kubo on Railway](https://railway.com/template/kubo)**

- **Creator:** fournyp's Projects
- **Category:** Storage

## Template content

### Kubo https://raw.githubusercontent.com/selfhosters/unRAID-CA-templates/master/templates/img/ipfs-kubo.png

- **Source:** FournyP/kubo-railway-template

## Documentation

![Kubo logo](https://user-images.githubusercontent.com/157609/250148884-d6d12db8-fdcf-4be3-8546-2550b69845d8.png)

# 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](https://raw.githubusercontent.com/ipfs/ipfs-webui/main/docs/screenshots/ipfs-webui-status.png)

## 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


## Similar templates

- [Garage S3 Storage](https://railway.com/deploy/garage-s3-storage) — Ultra-light S3 server: fast, open-source, plug-and-play.
- [Redis](https://railway.com/deploy/redis-1) — Self Host Latest Redis with Railway
- [EasyImg](https://railway.com/deploy/easyimg) — Simple self-hostable Nuxt.js personal image hosting system.

Open this page in a browser: https://railway.com/deploy/kubo