No. BYOA is included in your existing LuxGov plan. You pay separately for your own AI platform subscription (Copilot, ChatGPT Plus/Team, etc.), not to LuxGov.
Not today. Both require the real MCP protocol (JSON-RPC), and LuxGov's current implementation is a REST API, not that protocol. See the AI Boundary Guide for the full explanation. ChatGPT users can still connect through a Custom GPT Action instead.
Project status, status reports, evidence tied to a specific clause, project context (delivery method, building type), and conflict information (which currently returns an honest "not yet available" answer). Nothing else, and never anything that lets it change or delete data.
LuxGov only sees which specific tool your AI calls and what data it requests, for example which project, never your original question or your AI's final answer.
Once your AI assistant receives information from LuxGov, it leaves LuxGov's sovereign storage environment and is subject to your AI provider's own data handling. If you have jurisdiction-specific data residency obligations beyond what LuxGov's storage provides, confirm your AI provider's processing location before connecting.
No. MCP access is read-only in its current phase. It cannot upload files, trigger analysis, or modify anything in LuxGov.
No. LuxGov provides access to evidence-derived information. It does not provide compliance approval, certification, or a legal opinion — a licensed reviewer or certifier makes that determination.
It depends on your plan: Trial 10/min, Standard 30/min, Professional 60/min, Enterprise 120/min.
Keys are shown once, at generation. If you lose it, revoke it and generate a new one — there's no way to retrieve the old value.
No, and we'd rather tell you that up front. Every platform tested against LuxGov so far needed at least one real fix along the way (a disconnected tool, a field-hijack bug, a wrong file format). See the Troubleshooting Guide before you start.
Check the Troubleshooting Guide first. If your issue isn't listed, contact LuxGov support with your platform name and the exact error you're seeing.