---
title: "Deploy cloud-cost-optimization-hub"
description: "Multi-cloud cost observability and optimization dashboard."
category: "Analytics"
url: https://railway.com/deploy/cloud-cost-optimization-hub
---

# Deploy cloud-cost-optimization-hub

Multi-cloud cost observability and optimization dashboard.

**[Deploy cloud-cost-optimization-hub on Railway](https://railway.com/template/cloud-cost-optimization-hub)**

- **Creator:** kmaki's Projects
- **Category:** Analytics

## Template content

### frontend

- **Image:** xiaosong233/cloud-cost-optimization-hub-frontend-railway:latest
- **Public domain:** Yes

### backend

- **Image:** xiaosong233/cloud-cost-optimization-hub-backend-railway:latest

### database

- **Image:** postgres:15.14-alpine

## Documentation

# Deploy and Host Cloud Cost Optimization Hub on Railway
Ccoh is a multi-cloud cost observability and optimization dashboard.

## About Hosting Cloud Cost Optimization Hub on Railway
Railway runs the Next.js dashboard, private Go API, and PostgreSQL database as Docker services. Only the frontend is public; API traffic is proxied over Railway's private network.

## Tech Stack
- Next.js 15, TypeScript, and Tailwind CSS frontend
- Go and Gin REST API
- PostgreSQL 15 database
- Docker containers and Railway private networking

## Why Deploy Cloud Cost Optimization Hub on Railway
Railway provides one-click Docker deployment, managed public routing, private service discovery, generated secrets, and persistent storage for a compact multi-cloud cost dashboard.

## Common Use Cases
Use the hub to explore multi-cloud cost visibility, register cloud accounts, review cost summaries, and evaluate optimization recommendations across AWS, GCP, and Azure.

## Deployment Notes
The frontend listens on port 3000 and proxies `/api/*` to the private backend on port 8080. Register the first account at `/register`; the upstream project has no default credentials. PostgreSQL data persists at `/var/lib/postgresql/data`, with `PGDATA` set to a subdirectory for Railway volume compatibility. The backend waits for PostgreSQL and applies migrations from its image entrypoint. Cloud provider credentials are added in the application after login.

## Dependencies for Cloud Cost Optimization Hub on Railway
The public frontend depends on the private backend, and the backend depends on PostgreSQL for accounts, cost records, alerts, and recommendations.

### Deployment Dependencies

| Service | Image | Port | Volume |
|---------|-------|------|--------|
| frontend | xiaosong233/cloud-cost-optimization-hub-frontend-railway:latest | 3000 | - |
| backend | xiaosong233/cloud-cost-optimization-hub-backend-railway:latest | 8080 | - |
| database | postgres:15.14-alpine | 5432 | /var/lib/postgresql/data |

## Similar templates

- [Betterlytics](https://railway.com/deploy/betterlytics) — Betterlytics is a cookieless analytics platform GDPR-compliant.
- [Finance Tracker](https://railway.com/deploy/finance-tracker-1) — Private multi-user household finance ledger with budgets and CSV import.
- [Matomo Analytics + MariaDB](https://railway.com/deploy/matomo-analytics-mariadb) — Privacy-friendly analytics with MariaDB and persistent volumes.

Open this page in a browser: https://railway.com/deploy/cloud-cost-optimization-hub