Self-hosted software earns a reputation for being heavy when the first hour is spent on prerequisites. The evaluation path here is deliberately short, and the same steps scale to a production install.
One command to a running demo
Unzip and run the local runner. It creates the demo database, applies the schema and seed accounts, and starts the server - then tells you the dashboard URL and the sign-in details.
Running it again is safe: an existing database is detected and left untouched rather than reset.
One tag to add chat to your site
A single script tag before the closing body tag, pointing at your own server. No build step, no package to install, and it behaves the same on WordPress, Shopify, a custom application or plain HTML.
Operations you can reason about
A liveness endpoint says the process is answering. A readiness endpoint reports the database, licence and schema individually, so an outage tells you which dependency failed instead of returning a bare error.
Privileged actions are written to an audit log, so 'who changed that setting' has an answer.
A checklist rather than a leap of faith
The download includes a verification checklist that walks through proving each surface actually works - health, sign-in, the widget, the public APIs, and a full end-to-end conversation with a rating.