
Deploy OpenProject | (Just Updated) Open-Source Jira and Asana Alternative, Admin Login Pre-Created, Sign-up Closed
OpenProject project management software, Jira and Asana alternative
openproject
Just deployed
/var/openproject/assets
database
Just deployed
/var/lib/postgresql
Deploy and Host OpenProject on Railway
Built for an LLM agent to deploy and use. The deploy form has no fields to fill: the admin password, the API token, the secret key and the database password are generated, the admin account exists before the site is reachable, and self-registration is closed. OpenProject is open-source project management software with work packages, Gantt charts, boards, time tracking, wikis, meetings and team planners, a self-hosted alternative to Jira, Asana and Monday.
About Hosting OpenProject
This template runs two services: openproject, the official OpenProject 17.9.8 slim image pinned by digest in a thin wrapper, which owns the one public domain on port 8080 with an HTTP healthcheck at /health_checks/default and a volume at /var/openproject/assets for attachments and caches; and database, PostgreSQL 17 with a volume at /var/lib/postgresql.
What the wrapper fixes. Stock OpenProject needs four containers from one image (web, worker, cron, one-shot seeder) sharing an assets volume, which Railway cannot attach to more than one service, and it leaves self-registration open with the admin password set to admin and a forced change on first login. The wrapper runs the migrations and seeder, creates the admin account with the generated ADMIN_PASSWORD, turns self-registration off, creates an admin API token from API_TOKEN, and runs the web server and the background worker side by side in one container. Redeploys keep the admin, the projects and every attachment.
Using it. Open your domain and sign in as admin with ADMIN_PASSWORD. An agent uses the API instead: send HTTP basic auth with the user name apikey and API_TOKEN as the password to /api/v3. E-mail delivery, the real-time collaborative editing server and the document converters are off; the first start migrates the database and takes about two minutes.
Agent contract
- Public URL:
https://RAILWAY_PUBLIC_DOMAIN(the generated domain of theopenprojectservice) - Private URL:
http://openproject.railway.internal:8080 - Credentials: the variables
ADMIN_PASSWORD(web login, user nameadmin) andAPI_TOKEN(API) on theopenprojectservice (plain text);ADMIN_EMAILis the admin e-mail address - Auth: the API takes HTTP basic auth with the user name
apikeyandAPI_TOKENas the password (curl -u "apikey:$API_TOKEN"); API routes answer 401 without it - Health:
GET /health_checks/defaultreturns 200 without credentials
#!/bin/sh
# needs: RAILWAY_PUBLIC_DOMAIN, API_TOKEN (variables of the openproject service); also curl, jq.
R="https://$RAILWAY_PUBLIC_DOMAIN"; H="content-type: application/json"
n=0; until [ "$(curl -s -o /dev/null -w '%{http_code}' "$R/health_checks/default")" = 200 ]; do n=$((n+1)); [ "$n" -le 120 ] || break; sleep 5; done
curl -s -o /dev/null -w "health: %{http_code}\n" "$R/health_checks/default"
# sign-up is closed: the register page sends a visitor to the login page, and creating a user through the API needs the admin token
curl -s -o /dev/null -w "register page: %{http_code} %{redirect_url}\n" "$R/account/register"
curl -s -o /dev/null -w "public signup: %{http_code}\n" -H "$H" -d '{"login":"stranger","email":"stranger@example.com","password":"not-the-real-one-1","firstName":"X","lastName":"Y"}' "$R/api/v3/users"
# the generated token is the admin account
curl -s -u "apikey:$API_TOKEN" "$R/api/v3/users/me" | jq -r '"whoami: \(.login) admin=\(.admin)"'
BODY="{\"name\":\"Agent $$\",\"identifier\":\"agent-$$\"}"
# write-auth: POST /api/v3/projects needs the API token; without it, or with a wrong one, the answer is 401
curl -s -o /dev/null -w "read with key: %{http_code}\n" -u "apikey:$API_TOKEN" "$R/api/v3/projects"
curl -s -o /dev/null -w "write with key: %{http_code}\n" -H "$H" -u "apikey:$API_TOKEN" -d "$BODY" "$R/api/v3/projects"
curl -s -o /dev/null -w "write without key: %{http_code}\n" -H "$H" -d "$BODY" "$R/api/v3/projects"
curl -s -o /dev/null -w "write wrong key: %{http_code}\n" -H "$H" -u "apikey:not-a-real-token" -d "$BODY" "$R/api/v3/projects"
Expected output against a fresh deploy:
health: 200
register page: 302 https://RAILWAY_PUBLIC_DOMAIN/login
public signup: 401
whoami: admin admin=true
read with key: 200
write with key: 201
write without key: 401
write wrong key: 401
The refusals are the contract: a request without the token is refused (write without key: 401), a stranger cannot register (public signup: 401 through the API, and the register page sends a visitor to the login page) and a wrong token is refused (write wrong key: 401). With self-registration open the register page would answer 200 with a form, not 302.
Why Deploy OpenProject 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 OpenProject 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.
- Agent-ready - no deployer fields, a contract block, and one script that proves the app is healthy, strangers cannot register, the generated token is the admin and the API refuses writes without it.
- Admin included - the admin account has a generated password before the site is reachable, so nobody can claim your workspace with the default
adminpassword. - One container - web server, background worker and seeder run together, no shared-volume juggling.
- Data survives redeploys - projects in PostgreSQL on a volume, attachments on the assets volume.
- Pinned - OpenProject and PostgreSQL are pinned by digest, and the wrapper by tag and digest.
Common Use Cases
- Team project management - work packages, Gantt charts, boards and roadmaps without a Jira or Asana subscription.
- Agile and Scrum teams - backlogs, sprints, boards and burndown charts.
- Time and cost tracking - logged hours and budgets per project.
- Project management driven by an AI agent - give an agent the API token to create projects and work packages through the API.
Dependencies for OpenProject Hosting
- The openproject service and a PostgreSQL service, each with its volume, created by the template.
Deployment Dependencies
Template Content
openproject
ghcr.io/bon5co/openproject-railway:17.9.8database
postgres:17