Deploy OpenSEO (Self-Hosted)
Self-host OpenSEO with accounts, a prebuilt image, and bucket storage.
Just deployed
/data
Bucket
Bucket
Just deployed
Deploy and Host OpenSEO (Self-Hosted) on Railway
OpenSEO is an open-source SEO platform for keyword research, rank tracking, backlink and competitor analysis, site audits, and AI visibility. It includes an MCP server so AI agents can work with your SEO data. This template runs an OpenSEO workspace on Railway with email and password accounts, a Railway Bucket for its data, and a public HTTPS domain.
About Hosting OpenSEO (Self-Hosted)
Hosting OpenSEO (Self-Hosted) on Railway gives you a straightforward way to run your own SEO workspace without building the deployment from scratch. This template runs OpenSEO's Docker edition in one service: its runtime keeps the database and files in a Railway Bucket, a volume at /data holds the secrets generated on the first start, and Railway configures the public domain and healthcheck. The image is prebuilt, so Railway starts it without a build. It is a practical starting point for people who want to keep projects, keyword lists, audits, and rank history on their own infrastructure.
Common Use Cases
- Running an SEO workspace for yourself or your team with your own DataForSEO account.
- Managing keyword research, site audits, and rank tracking from one application.
- Connecting Claude Code, Codex, or another AI agent to OpenSEO's MCP tools.
Dependencies for OpenSEO (Self-Hosted) Hosting
- A Railway Bucket for the database and files, created by the template.
- Persistent storage mounted at
/data. - Public HTTPS domain for browser and MCP access.
- A DataForSEO account for features that query live SEO data.
Deployment Dependencies
- https://openseo.so
- https://github.com/every-app/open-seo/blob/main/docs/SELF_HOSTING_DOCKER.md
- https://github.com/every-app/open-seo/blob/main/docs/DATAFORSEO_API_KEY.md
Implementation Details
This template uses an image based on the official OpenSEO Docker edition, with Caddy in front. No separate database or cache service is required.
Set ADMIN_EMAIL when deploying. The administrator account is created with that email and the generated ADMIN_PASSWORD before the domain opens; reveal the password in the OpenSEO service's Variables tab and sign in at the public domain. Public registration is closed: invite teammates from Team settings, and each one creates an account from the invitation link.
DATAFORSEO_API_KEY is optional when deploying. Set it to the base64 encoding of your DataForSEO API login and API password in login:password format to enable live SEO data. Data queries are billed by DataForSEO. Site audits can run before this credential is configured.
For MCP access, use the service's HTTPS URL followed by /mcp and sign in with your OpenSEO account, or send an API key created in Settings. Back up both the bucket and the /data volume. Additional integration setup and image details are documented in the template repository.
Why Deploy OpenSEO (Self-Hosted) 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 OpenSEO (Self-Hosted) 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.
Template Content
ADMIN_EMAIL
Email of the OpenSEO administrator account, created on the first start. Invite teammates later from Team settings.
Bucket
Bucket

