---
title: "Deploy Homar"
description: "Custom dashboard with 40+ integrations, auth, 20K+ icons, no YAML"
category: "Other"
url: https://railway.com/deploy/homar
---

# Deploy Homar

Custom dashboard with 40+ integrations, auth, 20K+ icons, no YAML

**[Deploy Homar on Railway](https://railway.com/template/homar)**

- **Category:** Other

## Template content

### Homarr

- **Image:** ghcr.io/homarr-labs/homarr:latest
- **Public domain:** Yes

## Documentation

# Deploy and Host Homarr on Railway

![1](https://raw.githubusercontent.com/homarr-labs/homarr/dev/docs/img/logo/2340450-2-title.png)

Homarr is an open-source, self-hosted dashboard that brings all your applications, services, and infrastructure into a single customizable homepage. With a drag-and-drop interface, powerful integrations, user management, authentication support, and real-time widgets, Homarr helps individuals and teams organize, monitor, and quickly access their self-hosted services from one central dashboard.

## About Hosting Homarr

Hosting Homarr on Railway provides a managed environment for running your personal dashboard without maintaining servers or container infrastructure yourself. Railway automatically deploys the application, provisions networking, manages HTTPS, and makes scaling straightforward as your dashboard grows. Homarr stores dashboard layouts, user accounts, permissions, and application settings, making persistent storage important for production deployments. It can also integrate with external authentication providers such as OIDC and LDAP, along with dozens of self-hosted services including media servers, monitoring platforms, and home automation tools. Railway's private networking allows Homarr to securely communicate with internal services while exposing only the dashboard through a public HTTPS endpoint.

![0](https://github.com/homarr-labs/homarr/raw/dev/docs/img/screenshot.png)

## Common Use Cases

* Create a centralized homepage for self-hosted applications such as Plex, Jellyfin, Sonarr, Radarr, Nextcloud, and Home Assistant.
* Build an operations dashboard for monitoring infrastructure, containers, virtualization platforms, and server health.
* Provide teams with a customizable portal that aggregates internal applications, documentation, productivity tools, and shared resources.

## Dependencies for Homarr Hosting

| Dependency              | Purpose                                                                |
| ----------------------- | ---------------------------------------------------------------------- |
| Railway Volume          | Persists dashboard configuration, user data, and application settings. |
| Redis (optional)        | Enables real-time widget updates and live features.                    |
| OIDC or LDAP (optional) | Provides enterprise authentication and single sign-on.                 |

### Deployment Dependencies

| Resource               | Link                                                                                                 |
| ---------------------- | ---------------------------------------------------------------------------------------------------- |
| Official Documentation | [https://homarr.dev/docs/category/installation-1/](https://homarr.dev/docs/category/installation-1/) |
| GitHub Repository      | [https://github.com/homarr-labs/homarr](https://github.com/homarr-labs/homarr)                       |
| Live Demo              | [https://demo.homarr.dev/](https://demo.homarr.dev/)                                                 |
| Community Discord      | [https://discord.com/invite/aCsmEV5RgA](https://discord.com/invite/aCsmEV5RgA)                       |

### Implementation Details

#### Docker

Homarr is designed to run in a Docker container. If this Railway template includes a Dockerfile, Railway automatically builds and deploys the application without requiring additional build configuration.

#### Public Networking

| Setting     | Value      |
| ----------- | ---------- |
| Proxy Type  | HTTP Proxy |
| Target Port | 7575*      |

> **Note:** Port **7575** is the commonly documented default for Homarr deployments. If this template specifies a different port, use the value defined by the template.

Generate a Railway domain from **Settings → Networking → Generate Domain** to make the dashboard publicly accessible.

#### Environment Variables

The exact environment variables depend on the Homarr version and enabled integrations.

| Variable                 | Required | Description                                                                                                    |
| ------------------------ | :------: | -------------------------------------------------------------------------------------------------------------- |
| `HOMARR_PORT`            |    No    | Port the application listens on if configurable.                                                               |
| `HOMARR_STORAGE_PATH`    |    No    | Path used for persistent application data when supported.                                                      |
| Authentication variables | Optional | Configure OIDC or LDAP authentication if enabled.                                                              |
| Integration credentials  | Optional | API tokens or connection details for supported applications such as Plex, Proxmox, Home Assistant, and others. |

Example:

```env
HOMARR_PORT=7575
HOMARR_STORAGE_PATH=/appdata
```

Refer to the official Homarr documentation for integration-specific configuration and authentication variables.

#### Persistent Storage

Homarr should use persistent storage to retain dashboard layouts, user accounts, preferences, and configuration.

Add a Railway Volume:

1. Open the Homarr service.
2. Navigate to **Settings → Volumes**.
3. Select **Add Volume**.
4. Mount the volume at the path documented by the template or container image.

If no mount path is specified by the project documentation, consult the official installation guide rather than choosing one arbitrarily.

#### Database

Homarr does not require an external database for a standard deployment unless explicitly configured by the selected version or authentication provider.

Redis is optional and can be added as a Railway service when using features that rely on real-time updates.

#### Build & Start

If deploying from the provided Dockerfile, Railway automatically builds and starts the application.

No custom build or start commands are required.

#### Accessing the Application

After deployment:

1. Generate a Railway public domain.
2. Open the generated URL in your browser.
3. Complete the initial setup or sign in.
4. Begin adding applications, widgets, and integrations through the web interface.
5. Configure optional authentication providers and service integrations as needed.

## Why Deploy Homarr on Railway?

Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.

By deploying Homarr on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.


## Similar templates

- [Rocky Linux](https://railway.com/deploy/rocky-linux) — [Jul'26] Hosted Rocky Linux 9 workspace with SSH and persistent storage. 🚀
- [Foundry Virtual Tabletop](https://railway.com/deploy/X5tR6G) — A Self-Hosted & Modern Roleplaying Platform
- [Letta Code Remote](https://railway.com/deploy/letta-code-remote) — Run a Letta Code agent 24/7. No inbound ports, just deploy.

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