Typebot
Conversational forms that outconvert static ones - unlimited chats and seats on a managed Postgres.
One-click deploy, from $25/mo on a Miget plan.
Typeform proved that conversational beats static for completion rates, then priced it like a luxury: $29/month buys 100 responses. Typebot is the open-source version of the idea - a drag-and-drop builder for chat-style forms and bots, with logic, variables, integrations, and result analytics - and it was a top-10 template on Railway by deploy count.
The architecture is template-friendly: two stateless Next.js apps (the builder where you design, the viewer respondents see) on one managed Postgres, each on its own domain with PORT honored - no proxies. The builder runs migrations; the pair redeploys cleanly.
Self-hosted, your ADMIN_EMAIL account gets the unlimited plan: unlimited typebots, chats, and seats. Even Typebot’s own cloud charges $39/month for 2,000 chats.
Upstream project: Typebot
#what you get
- Drag-and-drop conversational flows: logic, variables, scoring
- Embed anywhere: bubble, popup, or full-page on the viewer domain
- Integrations: webhooks, OpenAI blocks, Sheets, and more
- Results analytics with drop-off insight
- Two stateless apps on managed Postgres - clean redeploys
- Unlimited chats and seats self-hosted (FSL license)
#topology
| Service | Role | Public |
|---|---|---|
| builder | bot designer + workspace (:5000) | yes (own domain) |
| viewer | respondent UI + chat API (:5000) | yes (own domain) |
| db | Postgres - managed service on Miget, container locally | no |
#miget sizing
// this stack needs
2.5 GiB RAM · 5 GB disk · 3 services
Both apps are stateless Next.js processes; the viewer is the traffic-facing one and scales by plan. Uploads need optional S3 config - core flows do not.
Hobby - recommended fit
$25/mo
2 vCPU · 4 GiB · 80 GiB disk
Headroom for your own apps: 8 GiB at $49/mo
Professional - production
$43/mo
2 vCPU · 4 GiB · 25 GiB disk
Dedicated resources, production SLOs - plan details
One Miget plan is a fixed pool of compute - the whole stack (managed databases included) deploys inside it, and anything left over runs your other apps. No per-service or per-seat math.
#vs. the managed service
What the hosted equivalents charge, against the flat Miget plan this stack fits on. Prices as of June 2026, sources linked.
| Service | Plan | Monthly | What you get |
|---|---|---|---|
| Typebot on Miget ★ | 4 GiB plan | $25 | this whole stack, flat - no usage meters, and room left for your own apps |
| Typeform | Basic | ~$29 | 100 responses/mo, 1 user ($25 annual); Plus $59 for 1,000 responses |
| Typebot Cloud | Starter | ~$39 | 2,000 chats/mo, 2 seats; +$10 per extra 500 chats |
Self-hosted Typebot grants the unlimited plan to your admin account - no chat or seat meters anywhere.
#vs. other PaaS
Estimated monthly cost of running this exact stack (2.5 GiB RAM, 5 GB disk, 3 containers) elsewhere, from published June 2026 rates.
| Platform | Est. monthly | Notes |
|---|---|---|
| Miget ★ | $25 flat | compose stacks first-class: one deploy, dedicated vCPU, managed Postgres/Valkey, volumes and TLS all included in the plan |
| Heroku | ~$125 | no volumes; nothing between 1 GB ($50) and 2.5 GB ($250) dynos - 2 GB containers cost far more than shown |
| DO App Platform | ~$35 | no persistent volumes - stateful containers need managed DBs/Spaces (base $5 Spaces included here) |
| Render | ~$33 | per-service instances (0.5 GB $7, 2 GB $25) - every container is its own paid service |
| Railway | ~$26 | usage-based ($10/GB RAM-mo); vCPU billed separately at $20/vCPU-mo on top |
| Fly.io | ~$16 | cheapest sticker price - but burstable shared CPUs (1/16 core; dedicated vCPUs cost ~2-3×), no compose deploys (one app per container, manual wiring), managed DBs billed extra |
Estimates assume RAM fully allocated at published on-demand rates - and sticker price isn't the whole comparison: the cheaper rows buy burstable shared CPUs, per-service wiring instead of a compose deploy, and managed databases billed separately. Heroku and DO App Platform have no persistent volumes at all - stateful stacks like this one need workarounds there.
#deploy it
On Miget
- Create a Compose Stack in app.miget.com pointing at the templates repository
- Set the stack path to
typebot -
Set the required variables:
ENCRYPTION_SECRET, exactly 32 chars, identical on both appsADMIN_EMAIL, this account gets the unlimited planSMTP_*, magic-link login (or GitHub/Google OAuth vars instead)NEXTAUTH_URL / NEXT_PUBLIC_VIEWER_URL, the two apps’ https domains after first deploy
- Deploy. Miget layers
compose.miget.yaml(RAM, privacy, volumes, managed services) automatically
Locally first?
Every template is portable, vanilla Docker Compose - the Miget overrides are ignored locally:
git clone https://github.com/deployable-sh/stacks
cd miget-compose-templates/typebot
docker compose up -dSame files, same behavior. The template README covers connection strings and scaling notes.
#faq
How does this compare to Typeform pricing?
Typeform Basic is $29/month for 100 responses - a single popular form blows through that in a day. Self-hosted Typebot has no response meter at all: $25/month infrastructure, unlimited chats, unlimited seats.
Why two apps and two domains?
Separation of concerns upstream: the builder is your internal workspace; the viewer is the public-facing bot runtime you embed on sites. Both honor PORT, so each simply gets its own domain - no proxy sidecars needed.
What does the FSL license mean for me?
Free for internal use and client work; the restriction is reselling access to your instance as a hosted service. Each FSL release converts to Apache-2.0 after two years. For the standard "our company’s forms" use case, nothing changes.
How do logins work without passwords?
Magic links by email (point SMTP at a real relay - or at the mailpit template during testing) or OAuth (GitHub/Google/Azure AD vars). Set DISABLE_SIGNUP=true once your team is aboard.
Ship Typebot today
One compose stack, 2.5 GiB of RAM, from $25/month flat, and it runs on your laptop with the same files.