> For the complete documentation index, see [llms.txt](https://docs.flowiseai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flowiseai.com/configuration/deployment/railway.md).

# Railway

***

1. Click the following prebuilt [template](https://railway.app/template/pn4G8S?referralCode=WVNPD9)
2. Click Deploy Now

<figure><img src="/files/t4432H7kSoD5sf0zy4QD" alt=""><figcaption></figcaption></figure>

3. Change to your preferred repository name and click Deploy

<figure><img src="/files/HXQXonlCz7RyJ0oSM09m" alt="" width="375"><figcaption></figcaption></figure>

4. If succeeds, you should be able to see a deployed URL

<figure><img src="/files/Suj1AwaFEvaPU2faD72V" alt=""><figcaption></figcaption></figure>

5. To add authorization, navigate to Variables tab and add:

* FLOWISE\_USERNAME
* FLOWISE\_PASSWORD

<figure><img src="/files/UXxUOLHQToNu7Dzmi88k" alt=""><figcaption></figcaption></figure>

6. There are list of env variables you can configure. Refer to [Environment Variables](/configuration/environment-variables.md)

That's it! You now have a deployed Flowise on Railway [🎉](https://emojipedia.org/party-popper/)[🎉](https://emojipedia.org/party-popper/)

## Persistent Volume

The default filesystem for services running on Railway is ephemeral. Flowise data isn’t persisted across deploys and restarts. To solve this issue, we can use [Railway Volume](https://docs.railway.app/reference/volumes).

To ease the steps, we have a Railway template with volume mounted: <https://railway.app/template/nEGbjR>

Just click Deploy and fill in the Env Variables like below:

* DATABASE\_PATH - `/opt/railway/.flowise`
* APIKEY\_PATH - `/opt/railway/.flowise`
* LOG\_PATH - `/opt/railway/.flowise/logs`
* SECRETKEY\_PATH - `/opt/railway/.flowise`
* BLOB\_STORAGE\_PATH - `/opt/railway/.flowise/storage`

<figure><img src="/files/jT3KK9x2dkVipoXOXQwE" alt="" width="420"><figcaption></figcaption></figure>

Now try creating a flow and save it in Flowise. Then try restarting service or redeploy, you should still be able to see the flow you have saved previously.