---
title: "Deploy FossFLOW"
description: "Deploy and Host FossFLOW with Railway"
category: "Other"
url: https://railway.com/deploy/fossflow
---

# Deploy FossFLOW

Deploy and Host FossFLOW with Railway

**[Deploy FossFLOW on Railway](https://railway.com/template/fossflow)**

- **Creator:** Tom
- **Category:** Other
- **Total deploys:** 6

## Template content

### FossFLOW https://raw.githubusercontent.com/Abrar74774/FossFLOW/d04d0a382facb4c1006e91e84636343b4fa22fca/packages/fossflow-app/public/logo512.png

- **Image:** stnsmith/fossflow@sha256:a35375ed305947675fe3506eace79d51ac20e056031fe85a64cac84e3e813106
- **Public domain:** Yes

## Documentation

# Deploy and Host FossFLOW on Railway

FossFLOW is an open-source isometric diagramming application built as a PWA on top of React and the FossFLOW (Isoflow-derived) rendering engine. It runs entirely in the browser, supports offline operation, and provides a full tooling environment for constructing 3D-style infrastructure diagrams, complete with autosave, icon import, and connector logic.

## About Hosting FossFLOW

Deploying FossFLOW involves hosting a static frontend plus an optional server-side storage layer. The application itself is compiled to a static bundle, but the container image also exposes storage functionality when enabled, allowing diagrams to persist across devices. Railway’s container deployment model maps cleanly to FossFLOW’s architecture: you run the published Docker image, expose port 80, and optionally mount persistent storage. No external database is required. Configuration is handled via environment variables, primarily toggling server-side storage and defining filesystem paths.

## Common Use Cases

* Running a self-hosted isometric diagramming tool for teams
* Providing persistent, multi-device access to diagrams via server storage
* Embedding FossFLOW within an internal engineering or documentation workflow

## Dependencies for FossFLOW Hosting

* Docker-compatible runtime (Railway handles this automatically)
* Persistent filesystem mount (optional, for server-side diagram storage)

### Deployment Dependencies

* FossFLOW Docker Hub image:
  [https://hub.docker.com/r/stnsmith/fossflow](https://hub.docker.com/r/stnsmith/fossflow)
* Repository and documentation:
  [https://github.com/stan-smith/FossFLOW](https://github.com/stan-smith/FossFLOW)

### Implementation Details 

Use the official image and enable server storage as needed:

```
docker run -p 80:80 \
  -v /data/diagrams:/data/diagrams \
  -e ENABLE_SERVER_STORAGE=true \
  stnsmith/fossflow@sha256:a35375ed305947675fe3506eace79d51ac20e056031fe85a64cac84e3e813106
```

Railway equivalents:

* Set `ENABLE_SERVER_STORAGE=true` in Railway environment variables
* Add a persistent volume mounted at `/data/diagrams`
* Expose port `80`

## Why Deploy FossFLOW 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 FossFLOW 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) — 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/fossflow