---
title: "Deploy una-neo-template"
description: "UNA/NEO community site and API"
category: "CMS"
url: https://railway.com/deploy/una-neo-template-1
---

# Deploy una-neo-template

UNA/NEO community site and API

**[Deploy una-neo-template on Railway](https://railway.com/template/una-neo-template-1)**

Machine-readable deploy manifest (JSON, validated by TemplateCI): https://railway.com/deploy/una-neo-template-1/manifest.json

- **Creator:** Yasko Studio
- **Category:** CMS

## Template content

### una

- **Image:** unaio/una:latest
- **Public domain:** Yes

### neo

- **Image:** unaio/neo:latest
- **Public domain:** Yes

### phpmyadmin

- **Image:** phpmyadmin:5.2.3
- **Start command:** `bash -c 'a2dismod -f mpm_event mpm_worker || true; exec /docker-entrypoint.sh apache2-foreground'`
- **Public domain:** Yes

### jot

- **Image:** unaio/jot-server:latest

### mail

- **Image:** namshi/smtp

### db

- **Image:** mariadb:13.0.2

## Documentation

# Deploy and Host UNA/NEO on Railway

UNA is a community site, and NEO is its front end. This template runs both with MariaDB, plus optional phpMyAdmin, jot, and mail.

## About Hosting UNA/NEO

The default services are `db`, `una`, and `neo`. The marketplace deploy includes every service. Remove a service you do not want before you deploy.

`una` reaches MariaDB on the private network and keeps its files on a `/var/www` volume. Each service has its own domain, so UNA is not mounted under a `/una` path.

You will be asked for `unaSiteEmail`, `unaAdminEmail`, `unaDbPwd`, `unaMysqlRootPassword`, `neoUnaApiKey`, `neoUnaUrl`, `logo`, `splash_text_component`, `global_css_component`, and `soketi_secret`. `logo`, `splash_text_component`, and `global_css_component` belong to `neo`.

## Why Deploy UNA/NEO on Railway

Railway gives each service a private network, a volume, and HTTPS on the public services. Image tags that are semantic versions (`1.2.3` or `v1.2.3`) move to newer minor and patch releases after Railway detects them. Detection can take a few hours. Workspace admins are notified when a service updates.

These images are not plain semantic versions, so they follow a new digest of the same tag instead of a new minor: `unaio/una:latest`, `unaio/neo:latest`, and `namshi/smtp`.

A MariaDB minor bump (`13.0.2` to a later `13.1`) can be incompatible. Skip that version on the service if a release misbehaves.

## Common Use Cases

- Host a UNA community site with the NEO front end
- Add phpMyAdmin when you need to inspect MariaDB
- Add jot or the mail relay only for the stacks that use them

## Dependencies for UNA/NEO Hosting

- MariaDB 13 for the UNA database
- The published `unaio/una` and `unaio/neo` images
- A volume for database files and for each UNA web root

### Deployment Dependencies

- [UNA](https://una.io/)
- [MariaDB](https://mariadb.org/)
- [phpMyAdmin](https://www.phpmyadmin.net/)


## Similar templates

- [Libredesk - Complete Setup](https://railway.com/deploy/libredesk-complete-setup) — Complete self-hosted omnichannel customer support desk.
- [Paperless-ngx](https://railway.com/deploy/paperless-ngx-3) — Paperless-ngx — document management with OCR and full-text search
- [Instatic CMS - Postgres](https://railway.com/deploy/instatic-cms-postgres) — Design, build and manage powerful static sites from state-of-the-art CMS

Open this page in a browser: https://railway.com/deploy/una-neo-template-1