---
title: "Deploy postiz-app:v2.11.3"
description: "One Click deployment of Popular Open Source Social media scheduling tool."
category: "Automation"
url: https://railway.com/deploy/Rd76MM
---

# Deploy postiz-app:v2.11.3

One Click deployment of Popular Open Source Social media scheduling tool.

**[Deploy postiz-app:v2.11.3 on Railway](https://railway.com/template/Rd76MM)**

- **Creator:** My Workspace
- **Category:** Automation
- **Total deploys:** 715

## Template content

### Redis https://devicons.railway.app/i/redis.svg

- **Image:** redis:7

### gitroomhq/postiz-app:latest

- **Image:** ghcr.io/gitroomhq/postiz-app:v2.11.3

### Postgres https://devicons.railway.app/i/postgresql.svg

- **Image:** ghcr.io/railwayapp-templates/postgres-ssl:16

## Documentation

# Deploy and Host

[Postiz](https://postiz.com) is your ultimate social media scheduling tool. It offers everything you need to manage social posts, build an audience, capture leads, and grow your business — all from a single, streamlined platform.

---

## Recent Changes
- 3/Aug/25 - added new variables to template BACKEND_URL


## About Hosting

[Railway](https://railway.app) is a cloud infrastructure platform designed to simplify deployments. Hosting Postiz on Railway provides:

- Scalable deployments via containers
- Seamless integration of services (DB, cache, frontend/backend)
- CI/CD out-of-the-box
- Easy public domain generation

Postiz leverages a multi-container setup including frontend, backend, Redis, PostgreSQL, and public entry via port 5000.

---

## Why Deploy

By deploying Postiz on Railway, you benefit from:

- Centralized management of your social scheduling tools
- Automation of post scheduling and audience engagement
- Full control of infrastructure and environment variables
- A fast and reliable cloud platform with built-in observability
- Easy port and service mapping for multi-container apps

---

## Common Use Cases

| Use Case             | Description                                                   |
|----------------------|---------------------------------------------------------------|
| ✅ Small Businesses   | Schedule & track content from one tool                        |
| ✅ Marketing Teams    | Manage campaigns and monitor performance across platforms     |
| ✅ Agencies           | Handle multiple clients and brands with separate workflows    |
| ✅ Developers         | Customize and deploy on your own cloud infrastructure         |

---

## Dependencies for Running Postiz

Postiz requires several services to be deployed in parallel. These can be hosted using Docker or Railway-provided services.

### Deployment Dependencies

| Service        | Port    | Description                                  |
|----------------|---------|----------------------------------------------|
| Frontend       | 4200    | Angular-based UI frontend                    |
| Backend API    | 3000    | RESTful API service (Node.js or similar)     |
| PostgreSQL     | 5432    | Primary relational database                  |
| Redis          | 6379    | In-memory cache/session management           |
| Entry Point    | 5000    | Public access port for Postiz container      |

> ⚠️ Be sure to expose port **5000** as the public entry in Railway after deployment.

---

## Network Ports Summary

| Port     | Usage                       |
|----------|-----------------------------|
| 5000/tcp | 🔗 Public entry for Postiz   |
| 4200/tcp | 🌐 Frontend (UI)             |
| 3000/tcp | ⚙️ Backend API               |
| 5432/tcp | 🗄️ PostgreSQL database       |
| 6379/tcp | 🧠 Redis cache               |

> ⚠️ Note: Public Redis/PostgreSQL access may incur **egress fees** on Railway.

---

## Setup Email Notifications

Email support can be configured using any SMTP-compatible provider.

📄 Refer to: [Email Configuration Docs](https://docs.postiz.com/configuration/emails)

You’ll need to define these environment variables:
- `EMAIL_HOST`
- `EMAIL_PORT`
- `EMAIL_USER`
- `EMAIL_PASS`
- `EMAIL_FROM`

---

## Social Media Integrations

Postiz supports multiple providers (Facebook, LinkedIn, Instagram, X, etc.).

📄 See: [Provider Integration Docs](https://docs.postiz.com/providers)

Add tokens and credentials as Railway environment variables to activate social sync features.

---

## Important: Post Deployment Port Mapping

After deploying Postiz on Railway, you **must manually set the public access port to `5000`**. This is crucial because:

- Port `5000` is the single public entry point for the Postiz application.
- Without selecting it, your deployment won't be reachable via the generated Railway domain.

#### ✅ Steps:
1. Go to your deployed service in the Railway dashboard.
2. Locate the **"Domains"** tab or the service’s runtime view.
3. Find the **“Select Port”** dropdown.
4. Choose port **`5000`** as the **public-facing port**.
5. Save or redeploy if required.

```
Example:
Domain → https://your-postiz-app.up.railway.app
Port → 5000 (public entry)
```

> ⚠️ Failure to expose port `5000` publicly will result in your Postiz app being inaccessible.

---

## ✅ Final Deployment Notes

- After deploying, Railway generates a public domain — ensure it routes to **port 5000**
- Store secrets and environment variables securely using Railway's "Variables" tab
- Consult Postiz [docs](https://docs.postiz.com) for further configuration

---

Need help or support?  
📬 [Postiz Support](https://postiz.com) | 📖 [Official Docs](https://docs.postiz.com)


## Similar templates

- [N8N Main + Worker](https://railway.com/deploy/n8n-main-worker) — Deploy and Host N8N with Inactive worker.
- [Evolution API with n8n](https://railway.com/deploy/evolution-api-with-n8n) — [Jul'26] WhatsApp automation platform using Evolution API, n8n & PostgreSQL
- [Postgres Backup](https://railway.com/deploy/postgres-s3-backups) — Cron-based PostgreSQL backup to bucket storage

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