Do you see our prompts?
No, not by default. Classification happens on the device or at your gateway, and only metadata reaches Oqulix: the destination, a data class label with its confidence, sizes, whether the tool is sanctioned, and who sent it. Raw content is stored only if your organisation signs a content addendum and switches content mode on. It is then encrypted under its own key, purged on your retention schedule, and every read is audited.
Do we have to replace our DLP?
No. Oqulix sits on top of the DLP you already run. It ingests its detections, adds the AI context (which tool, which model, sanctioned or not, which department and device) and shows them beside your other AI signals. Enforcement stays with your DLP.
Which DLPs, gateways and agents are supported?
FortiDLP is supported today through a streaming connector, and a connector framework covers further DLP vendors. LiteLLM-based LLM and MCP gateways, OpenTelemetry GenAI spans from internal model stacks, a Windows endpoint agent, and the AI vendors' own usage APIs (Claude, OpenAI, Amazon Bedrock, Azure OpenAI and Google Vertex AI) are all supported. Firewall telemetry, for unmanaged and BYOD devices with no agent, is coming next.
Where is our data stored?
Every tenant is isolated by PostgreSQL row-level security and its own identity realm. The design is built around India's DPDP Act and GDPR: because only metadata leaves by default, very little personal data is processed at all. Ask us about hosting region during your demo.
How long does deployment take?
Connecting a DLP or pointing a gateway at Oqulix is a configuration change, not a project, and the first events appear once traffic flows. Onboarding asks HR or Legal to sign the monitoring notice first, and we recommend doing that before connecting anything.
Can Oqulix block traffic?
No. Oqulix is a visibility layer: it observes and reports, and it does not block, redact or change anything. Enforcement stays with your DLP and the controls you already run.
Can we see token usage and cost for Claude and OpenAI?
Yes. Connect the vendor's admin usage API with a read-only key. Tokens appear within about a minute of showing in the vendor's console; billed cost appears once the vendor closes the day, and is never estimated. Amazon Bedrock, Azure OpenAI and Google Vertex AI connect the same way.
How is one customer kept apart from another?
Each tenant has its own identity realm. Your organisation is derived from which realm signed your token, never from anything the client sends, and every query is constrained by row-level security. Device keys can only submit events; they can't read the dashboard.