Deploy Typebot Builder and Viewer Stack

Deploy and Host Typebot Builder and Viewer Stack on Railway

Chatbot builder and viewer with Postgres, Valkey and S3-compatible files.

About Hosting Typebot Builder and Viewer Stack

This deployment fork provisions Valkey, MinIO, Console, Postgres, Builder, Viewer, MinIO Bucket Creator. Application domains and any authored TCP endpoints are generated for each new deployment. Database and queue services are private by default.

Why Deploy Typebot Builder and Viewer Stack on Railway

• New setup and maintenance documentation with attribution to the original template.
• Public container sources are locked by image digest and public Git repositories by commit SHA.
• Database and queue services use private networking; external database access is an explicit deployer choice.
• Resolved the missing MinIO endpoint reference.
• Replaced an unavailable mc image with a checksum-verified official CLI download; bucket creation is idempotent and public assets are read-only.

Common Use Cases

• Build a conversational contact or onboarding flow.
• Publish interactive chatbots.
• Store bot responses and uploaded assets.

Dependencies for Typebot Builder and Viewer Stack

• A Railway account with capacity for 7 service definitions and the authored storage.
• Your own external accounts and credentials when an integration or model provider is needed. No paid provider subscription is included.
• Required inputs at deployment: Builder.SMTP_HOST, Builder.SMTP_PASSWORD, Builder.SMTP_USERNAME.

First Launch

Before deploy, supply Builder.SMTP_HOST, SMTP_USERNAME and SMTP_PASSWORD for your own mail provider. Wait for the builder, viewer, databases and MinIO. The initializer creates the bucket and exits. Sign in through the Builder domain, create a bot, then publish it to the Viewer.

Included Services and Storage

Operations

Builder and Viewer share the encryption secret, database and bucket. Back up PostgreSQL and MinIO. The public assets prefix permits anonymous downloads only; writes require S3 credentials. This is a multi-service stack with mail-provider configuration required.

Railway bills the deployer for actual services, storage and network use. Back up persistent data before source/version changes. This publication was checked against Railway's configuration schema and upstream source/registry availability; a full runtime deployment test has not been performed.

Attribution and Source

Based on Typebot by Brody's Projects. It appeared at position 13 in Railway's backend Popular/browse results captured on 2026-10-18, with 4,100 deployments reported for the original. That count belongs to the original, not this new fork.

The original software and repositories remain owned by their upstream authors and retain their licenses. This is a deployment configuration fork with new documentation, not a claim of software authorship or official vendor affiliation.

Application source: railwayapp-templates/minio · railwayapp-templates/minio-console. Fork/eject the repository before making your own code changes.

For template wiring issues, use this template's discussion link and share redacted logs. Never post passwords, API keys or login tokens.

Deploy this recipe

Review the required inputs and hosting resource costs before deploying.

Related deployment recipes

• n8n with PostgreSQL & Durable Storage — Workflow automation with private Postgres, durable files and webhook URLs.
• NocoDB with PostgreSQL, Redis & Files — No-code tables, forms and APIs with Postgres, Redis and durable files.
• Gotenberg PDF API with Authentication — PDF conversion API with generated Basic Auth and private URL filtering.

These are separate deployments; no preconfigured integration between the applications is implied.

Disclosure: this template is maintained independently. Its maintainer may earn Railway usage kickbacks when other people deploy it. Railway bills hosting separately; no paid software subscription or provider credits are included.