---
title: "Deploy SiYuan"
description: "Self-host SiYuan with secure access, persistent notes, and tested recovery."
category: "Other"
url: https://railway.com/deploy/siyuan-1
---

# Deploy SiYuan

Self-host SiYuan with secure access, persistent notes, and tested recovery.

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

- **Creator:** l4time's Projects
- **Category:** Other

## Template content

### siyuan

- **Source:** https://github.com/l4time/railway-siyuan-template
- **Health check:** /healthz
- **Public domain:** Yes

## Documentation

# Deploy and Host

Run SiYuan `v3.8.2` as one authenticated Railway service with a persistent
workspace, immutable image pins, non-root steady processes, and true
boot-progress readiness.

## About Hosting

Wait for deployment health, open the Railway domain, and enter the generated
access code from Railway Variables. Create a synthetic notebook, note, asset,
and search before importing important data.

## Common Use Cases

- Run an authenticated SiYuan workspace.
- Create notebooks, notes, assets, and searches with persistent workspace data.
- Verify recovery in a fresh volume before importing important data.

## Dependencies for

### Deployment Dependencies

- One public application service.
- One volume at `/siyuan/workspace`.
- One generated access code with bypass disabled.
- HTTPS target port `8080` and `/healthz`.
- One replica and Serverless disabled.
- Exact upstream and build-image digests.

## Why Deploy

The deployment keeps SiYuan in one authenticated service with a persistent
workspace, immutable image pins, non-root steady processes, and boot-progress
readiness.

### Persistence and recovery

Back up the complete stopped `/siyuan/workspace` tree, including configuration
and repository-key material. Restore the complete archive to a fresh volume
with UID/GID 1000 and verify auth, notes, assets, search, and repository access.
Partial or live copies are not claimed as complete backups.

### Support

Template issues cover package pins, Railway wiring, readiness, authentication,
volume ownership, and documentation. SiYuan application issues belong
upstream; Railway account, billing, domain, and volume incidents belong to
Railway support. Never post access codes, repository keys, cookies, notes,
assets, archives, private URLs, or unredacted logs.


## Similar templates

- [Rocky Linux](https://railway.com/deploy/rocky-linux) — 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/siyuan-1