Deploy Typebot | (Just Updated) Chatbot Builder You Can Sign Into Without An SMTP Account

Deploy and Host Typebot on Railway

Typebot is an open-source chatbot and conversational-form builder: a visual drag-and-drop editor with 30+ block types, conditional logic, variables, native OpenAI/LLM blocks, webhooks and Google Sheets integrations, and an embed library that drops a bot into any website as a container, popup or chat bubble. This template deploys Typebot 3.17.2 as five services — the Builder (the editor), the Viewer (the runtime that serves published bots), PostgreSQL, Redis and MinIO for uploads — and it is set up so that you can sign in the moment the deploy finishes, without owning an SMTP account and without exposing registration to strangers.

About Hosting Typebot

Typebot's only first-party sign-in method is an emailed login code; everything else is OAuth against GitHub, Google, GitLab, Azure AD, Keycloak or a custom OIDC issuer. Self-hosting it therefore normally means supplying working SMTP credentials before you can open your own instance for the first time, and transactional SMTP from a cloud host is exactly the thing that tends not to work.

This deployment runs a mailbox inside the Builder container and points Typebot's SMTP at it, so the login code is delivered locally and read at /inbox on the Builder URL, behind HTTP basic auth. That mailbox is the credential surface of the whole instance, so the container refuses to boot if its password is empty.

Registration is closed: DISABLE_SIGNUP is on and only the address in ADMIN_EMAIL can create an account, so a public Builder URL is not an open sign-up page for whoever finds it.

Uploads go to a MinIO service on a volume, and the bucket is created and made publicly readable on the Builder's first boot rather than by a one-shot container you have to remember to delete afterwards.

Common Use Cases

• Lead qualification — conversational forms that qualify website visitors before handing them to sales, in place of a static form.
• Customer support — AI-answering bots wired to your own OpenAI or Anthropic key, with webhook handoff to a human.
• Conversational surveys and onboarding — chat-style flows with branching, which typically complete at a higher rate than long forms.
• WhatsApp and embedded bots — the same flow published to a website bubble and to a WhatsApp number.

Why Deploy Typebot 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 scale it.

Deploying Typebot here gives you the editor, the bot runtime, the database, the cache and the object storage provisioned and wired together in one click, with private networking between them, a volume on every service that stores anything, and no per-chat or per-bot pricing.

Dependencies for Typebot Hosting

• Typebot Builder — the visual editor, ghcr.io/bon5co/typebot-railway-builder:3.17.2 (upstream baptistearno/typebot-builder:3.17.2 plus the built-in mailbox and gateway)
• Typebot Viewer — the runtime that serves published bots, ghcr.io/bon5co/typebot-railway-viewer:3.17.2
• PostgreSQL 17.6 — bots, workspaces, results
• Redis 8.2.1 — Typebot's sign-in rate limiters and cache
• MinIO — S3-compatible storage for uploaded and bot-sent media

Deployment Dependencies

• Typebot GitHub — https://github.com/baptisteArno/typebot.io
• Typebot self-hosting docs — https://docs.typebot.com/self-hosting
• Wrapper images — https://github.com/bon5co/typebot-railway
• MinIO — https://min.io

Implementation Details

• Signing in the first time. Open the Builder URL, enter the address shown in the Builder's ADMIN_EMAIL variable, then open https:///inbox and log in with admin and the generated INBOX_PASSWORD. The login code is in the message there. Typebot rate-limits login requests to one per minute per IP, so wait a minute before asking for a second code.
• Only ADMIN_EMAIL can register. To let a colleague in, invite them from inside the workspace; invitations bypass the sign-up block. To use a real mailbox instead, set SMTP_HOST, SMTP_PORT, SMTP_USERNAME and SMTP_PASSWORD on the Builder and the local mailbox stops being used.
• Two public URLs. The Builder is the editor and the Viewer serves published bots. Embed or share the Viewer URL, not the Builder one.
• Adding a custom domain to the Builder or Viewer means redeploying that service so the new domain reaches the app's environment.
• The images are pinned to 3.17.2 rather than tracking latest, because Typebot applies database migrations forward on boot.

Hardware Requirements