@Justin Connell Great questions, thanks for digging in! 1. Configuration every time? No. Settings are persisted via localStorage (webhook URL, API key, Supabase credentials). One-time setup, everything survives page reloads and browser restarts. 2. Single index.html — backend plans? n8n actually serves as the backend here. It handles all request processing, AI routing, RAG search, logging, and escalation logic. Supabase handles data persistence. So the architecture is: - Frontend: index.html on Netlify (static) - Backend: n8n workflows (5 in total) - Database: Supabase (PostgreSQL + pgvector) - Auth: dual API key model (public for widget, private for dashboard) The real limitation right now is that n8n runs locally with ngrok. Moving n8n to a cloud deployment (n8n Cloud, Railway, or VPS) is the actual next step before going to production — that gives a permanent webhook URL and removes the dependency on a local machine. The localStorage point is fair though — for a multi-tenant SaaS with multiple users per client, server-side session management would be the right move. That's a natural evolution once the product is deployed on cloud infrastructure. 3. Authentication and role-based access? There's already a two-tier access model via API keys: a public key for the embeddable widget (restricted to public documents only) and a private key for the internal dashboard (full document access). It's lightweight but functional for the target market — small businesses. Full login/register with role-based access is the next layer, and it fits naturally into the backend milestone. Demo — absolutely yes. The dashboard is live right now at charming-sable-0dd4f8.netlify.app and the widget is embeddable on any site. Happy to walk through it on the next call. Would love to hear your thoughts on the architecture and where you see it going.