Practical Notes
- Quant: the README exposes two deployment paths out of the box: Docker Compose for local trials and Helm for Kubernetes.
- Quant: the default local entry lands on
http://localhost:8082, which makes environment verification straightforward.
Rollout pattern
- Start in Docker Compose with one model configuration and one evaluation set before you touch Helm.
- Promote only after you can tie a bad answer back to a prompt diff or trace record inside the same system.
- Treat internet exposure as a separate security review because the maintainers call out SSRF and privilege risks directly.
Watchouts
This is not a no-config SaaS toy: you need to own model credentials, deployment topology, and public-network hardening before treating it as a shared operations plane.
FAQ
Q: Can I try it without Kubernetes? A: Yes. The README puts Docker Compose first for local deployment and Helm second for cluster rollout.
Q: What problem does it solve best? A: It centralizes prompt iteration, evaluation data, and traces so debugging is less fragmented.
Q: What is the main risk? A: Publishing it on a public network without hardening; the maintainers explicitly warn about security review first.