Deploy and Host bisibility on Railway

bisibility is a self-hosted, open-source SEO platform (AGPL-3.0) for researching keywords, inspecting backlinks, and tracking Google rankings. This template deploys the complete scheduled-check stack with the web/API, worker, application PostgreSQL, Redis, Temporal Server, Temporal PostgreSQL, and idempotent bootstrap jobs.

About Hosting

Railway keeps every service on private networking and exposes only the web application. Both PostgreSQL services use independent persistent volumes. The application and worker are pinned to the same immutable bisibility release, while Temporal Server is pinned independently.

Before serving users, configure EMAIL_FROM and RESEND_API_KEY, connect a SERP provider, and complete the production checklist.

Why Deploy bisibility on Railway?

The template generates deployment secrets, initializes both Temporal schemas and the deployment namespace, applies application migrations, and starts the matching worker automatically. Temporal Cloud is not required.

Common Use Cases

Research keywords and inspect backlinks through your own SERP provider account.
Track keyword positions with manual and scheduled checks.
Keep rank history and provider credentials inside your own Railway project.
Run the bisibility API, CLI, MCP, webhooks, and Temporal-backed automation.

Dependencies for bisibility Hosting

A verified transactional email sender and Resend API key for sign-in codes.
A supported SERP provider connected after deployment.
Railway resources for six persistent roles and three completed bootstrap jobs.

Deployment Dependencies

bisibility web and worker images pinned to the same release.
PostgreSQL 18 for application data and separate Temporal persistence.
Redis 8 for rate limits, idempotency, notifications, and worker liveness.
Temporal Server and admin tools pinned to 1.31.2.

Full setup, upgrade, backup, and rollback steps: https://bisibility.com/docs/self-hosting#railway