← Templates · Automation
TY
Typebot
Community3 services
Typebot, the open-source conversational form and chatbot builder — design flows visually, publish, and collect responses without writing code.
| Runs | 3 services |
|---|---|
| Stack | typebot-buildertypebot-viewertypebot-db |
| Provisioned for it | Nothing, it's self-contained |
| Verified | Not yet |
Why deploy on Railyard
Railyard provisions all 3 services in this stack together — typebot-builder, typebot-viewer, typebot-db — wired to reach each other over the private network, on a server you already pay for.
Deploying Typebot is one piece of a bigger stack you can keep building — add a database, a worker, a cache, or another app, all on the same servers you already pay for.
Good for
- Conversational forms and lead-gen chatbots embedded on a site
- Internal surveys and support triage flows built visually instead of coded
Good to know
- Postgres is wired up automatically between the builder and viewer
- Nobody can sign in until you add at least one login method — Typebot's own /api/auth/providers comes back empty with no SMTP or OAuth env vars set, which is every service in this template by default. Set SMTP_* (for email sign-in) or one of GOOGLE_CLIENT_ID/GOOGLE_CLIENT_SECRET, GITHUB_CLIENT_ID/GITHUB_CLIENT_SECRET on typebot-builder before inviting anyone — ADMIN_EMAIL alone only grants that address admin rights once it can actually log in
- File-upload blocks need their own S3-compatible bucket — set the S3_* env vars on both services yourself if you need that feature
- Redis isn't included — Typebot's own docs call it optional for a single-instance deployment