Deploy OpenSEO

Open-source SEO suite: keywords, backlinks, rank tracking, audits, AI

Deploy OpenSEO

/var/lib/openseo

Bucket

Bucket

Just deployed

Deploy and Host OpenSEO on Railway

OpenSEO is an open-source SEO workspace and an alternative to Semrush and Ahrefs. It covers keyword research, domain overview, backlinks, rank tracking, site audits, Local SEO and AI visibility tracking, plus an AI assistant (SAM). You bring your own data provider keys and pay those providers directly.

About Hosting OpenSEO

This template runs OpenSEO's standalone edition (v0.1.29) as one service built from a public GitHub repo, plus a Railway Bucket. The service runs the OpenSEO runtime, the first-start setup and database migrations, the crawl gateway and Nginx. App data lives in the bucket; the secrets generated on first start and the runtime state live on a volume, so accounts and projects survive redeploys. Accounts use email and password: create the admin account right after deploy, because registration closes after the first account. SEO data needs a DataForSEO key or a treg token, which you can add as a variable at any time.

Common Use Cases

  • Keyword research, competitor domain overviews and backlink analysis for your own sites or clients
  • Daily rank tracking, Local SEO checks and technical site audits
  • Tracking how AI assistants mention your brand, and asking SAM to research and summarise SEO data

Dependencies for OpenSEO Hosting

  • Railway Bucket (S3 storage for OpenSEO's databases and files)
  • A DataForSEO API key or treg token for SEO data (optional at deploy, needed for research features)

Deployment Dependencies

Implementation Details

After deploy:

  1. Open the public URL and create the admin account straight away. The first visitor becomes the administrator and registration then closes. Invite teammates from the app.
  2. Set DATAFORSEO_API_KEY (base64 of login:password) or TREG_API_TOKEN on the OpenSEO service. OPENROUTER_API_KEY enables SAM. Google Search Console and Analytics need your own OAuth app (GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET) with the redirect URLs https://YOUR-DOMAIN/api/gsc/oauth/callback and https://YOUR-DOMAIN/api/ga4/oauth/callback. All of these are optional.
  3. With a custom domain, set BETTER_AUTH_URL to https://YOUR-DOMAIN.

Updates: the service builds from the template repo, which pins the official image by version and digest. When a new OpenSEO version is packaged there, Railway shows an "update available" notice; read the repo's CHANGELOG first. Migrations run on start and can't be undone, so back up the volume and the bucket before you update.

Why Deploy OpenSEO 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 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

More templates in this category

View Template
Plausible WordPress
Cookie-free WordPress stats from your own Plausible

onepush
0
View Template
Typesense Multilingual
Locale-aware multilingual search with Typesense

onepush
0
View Template
Formbricks
Surveys, NPS and in-app feedback on your own Postgres, Hub and Cube

Two Workspaces
3