Your webhook stays private
Visitors see a public bot ID. The destination URL stays encrypted on your server.
Turn an existing n8n workflow into a branded, protected client chat product in under 20 minutes. No exposed webhook. No per-message platform fee.
Runs in your Docker environment. Conversation storage stays off unless you enable it.
How can we help with your booking?
Visitors see a public bot ID. The destination URL stays encrypted on your server.
Run BotLatch where you run the rest of your stack. Store transcripts only when you choose.
Share a revocable report with message volume, success rate, errors, and response time.
Paste the production Chat Trigger URL and declare exact website origins.
Set the voice, colors, launcher, prompts, position, and theme.
Copy one script tag into the client website and run the built-in test.
Give your client a read-only reliability report with no configuration exposure.
BotLatch checks the boundary before a request can reach the private workflow.
Manage every client installation from one self-hosted console.
Desktop and mobile previews keep the handoff out of custom CSS.
Revocable links expose reliability and usage only.
Encrypted destinationThe webhook URL is protected with persisted ASP.NET Core Data Protection keys.
Network guardrailsPrivate, loopback, link-local, metadata, and redirect destinations are blocked by default.
Minimal recordsNo IP addresses or message bodies are logged by default.
Honest scopeBotLatch is not a compliance certification or a substitute for your client agreement.
Run unlimited client and bot records in one self-hosted BotLatch installation.
In Docker on a server you control, usually beside or near your n8n installation.
Not by default. You can choose no transcripts, seven days, or thirty days per bot.
No. Expiration stops future updates. Your last eligible version keeps running.
Active production Chat Trigger workflows returning output, text, or message. See the compatibility page for the tested window.
Support covers BotLatch installation, relay behavior, and the documented contract. It does not build or debug your agent logic.
You have 30 days if the supported workflow cannot be deployed after following the documented setup and support path.
No. Stripe handles the purchase. After installing BotLatch, open /setup on your own BotLatch host to create the single local owner account.
No. Visitors use the embedded chat without signing in. Their chat requests stay on the customer-controlled BotLatch infrastructure and never pass through BotLatch.com.
Deploy, connect, brand, install, and report from one controlled system.