Judicex runs as a local Flask workspace where you ingest official sources and matter files into a SQLite knowledge base, then draft, chat, and run workflow checks against only what you fed it. The LLM answers are bound to that evidence store — the vendor describes this as an 'answer contract that fails closed instead of hallucinating.' You deploy it on your own infrastructure, which means client files never leave your network. The MCP server lets you connect external tools, and JSON workflow packs let you encode firm-specific matter analysis profiles. The ceiling appears when your team grows past a handful of users — multi-tenant auth and SSO are on the roadmap but not yet shipped.