// how it is built
Edge-native, with a budget that cannot run away.
The whole thing runs on Cloudflare's edge. A single Worker serves the widget loader, the iframe frame, the conversation API, and the owner admin. Conversations, messages, leads, spend, and an audit log live in D1 (SQLite at the edge). KV holds the rate-limit counters. Lead notifications go out through Resend.
Replies come from OpenAI gpt-4.1, with every reply costed per token and rolled up against a hard monthly ceiling. The same abuse layer that protects MonkNote protects this: Turnstile, layered rate limits, moderation, and IP hashing so no raw visitor IP is ever stored.
Same family as the rest of my builds: no servers to babysit, no cold-start tax, and a clean owner dashboard for transcripts and leads.
runtime
Cloudflare Workers
abuse defense
Turnstile + rate limits
budget
hard monthly spend cap