Feature 06 · Self-hostable
Your support stack, on infrastructure you own.
Open architecture on serverless edge infrastructure means you can run the whole stack on your own account — no surprise vendors.
Most support tools are black boxes you rent, with data and pricing you don't control.
Clanker Support is built to run on serverless edge infrastructure you can own. The architecture is open, so instead of renting a black box you can deploy the whole stack on your own account and keep your data and your bill under your control.
No surprise middlemen, no opaque per-seat pricing — just components you can see, running where you choose.
What you get
Own the stack
Deploy the full system on your own infrastructure account rather than depending on a single hosted vendor.
Serverless edge
Runs on edge infrastructure that scales down to zero and up automatically — no servers to babysit.
No surprise vendors
Open architecture means no hidden dependencies and no lock-in you only discover at renewal.
What it means in practice
- ✓Keep customer conversations on infrastructure you control.
- ✓Scale with usage on serverless edge — pay for what you use.
- ✓Audit and extend the stack, because the architecture is open.
Explore the rest
Drop-in widget
One script tag. Loads in a shadow DOM so your styles never leak — and theirs never leak into you.
02Answers from your docs
Paste your knowledge base or system prompt. The agent stays on-topic and admits when it doesn't know.
03Escalates to humans
Customers reach a human in one tap — the conversation lands in your inbox with full context. No lost threads.
04Email threading
Replies go out as email and customer responses thread back into the same conversation automatically.
05Your model, any time
Built on LLM Gateway. Pick from a curated catalog of web-search-capable models per project — a config change, not a rewrite.
Frequently asked questions
Can I self-host Clanker Support?
Yes. The stack is MIT open source and runs on serverless infrastructure, so instead of renting a black box you can deploy the whole thing on your own account. You bring your own keys and a database; the code you deploy is the same code behind the hosted service, and one environment variable marks your own workspaces as internal so plan limits never apply — the self-hosting docs walk through it.
Where does my data live when I self-host?
On infrastructure you own. Customer conversations stay in your own database, on your own account, rather than in a vendor's cloud — which is what makes Clanker Support a fit for teams with data-residency requirements.
Is there any vendor lock-in?
No. The open architecture means no hidden dependencies and no surprise vendors you only discover at renewal. You can audit and extend the stack, run it where you choose, and keep both your data and your bill under your control.