Open surfaces,
not a connector catalogue.
LexVio integrates the way infrastructure does — a REST API, signed webhooks, your identity provider, and a deployment target you choose. Everything on this page is a shipping capability with its own feature page, not a logo wall.
- ✓REST over HTTPS, Bearer-token auth
- ✓HMAC-signed webhook payloads
- ✓SAML 2.0 + SCIM 2.0 against your IdP
- ✓Air-gapped on-prem option
Developer
Move data in and out of LexVio from your own systems.
Per-org API key. A read-only Indian legal-data API — clause benchmarks, judgment and statute search.
Standard REST, Bearer-token auth, JSON out. Metered by a monthly call quota per key rather than a rate limit. Keys carry no scopes, there is no scan or search-your-own-data endpoint, and the OpenAPI spec is not served in production. Not included in any published plan.
HMAC-signed outbound webhooks with retries and a delivery log. Six research events fire today.
HMAC-SHA256-signed JSON POSTed to an HTTPS endpoint you register, retried six times out to 24 hours then auto-disabled. Only the research thread and memory events are emitted; the judgment, statute, cause-list, benchmark and compliance events are subscribable and unpublished. Subscriptions hang off an Intelligence API key.
Append-only record of state-changing actions, enforced in the database.
Database triggers reject updates outright and reject deletes without an explicit purge flag, so it is append-only in fact rather than by convention. Read and filter it in the admin surface — there is no CSV export and no audit event on the webhook set, so it cannot be streamed to a SIEM today.
Identity & SSO
Your directory stays the source of truth for who has access.
Not shipped. Connector configuration exists; SAML sign-in does not.
You can store IdP connector configuration and there are setup guides for the major providers, but there is no assertion endpoint, no signature validation, no just-in-time provisioning and no way to enforce SSO over passwords. If SSO is a procurement requirement, treat it as not delivered.
SCIM 2.0 user provisioning from your IdP, with a provisioning log.
Create, update, deactivate and delete users, with the discovery documents an IdP expects and every call logged. Groups are read-only and map to a LexVio role. Rotation is mint-then-revoke rather than one action. Runs without SAML, which it has to, because SAML sign-in is not shipped. Not included in any published plan.
Channels
Reach the AI from where the document already is.
Two-way text conversation with the assistant over WhatsApp, in English or Hindi.
Text in, text out, with the conversation kept per number and outbound notifications on the same channel. Documents you send are recorded but never read — no download, no OCR, no analysis — so upload contracts in the app instead. Messages traverse Meta's infrastructure.
Audio in, punctuated text out, in English or Hindi. It transcribes; it does not answer.
Up to 25 MB per file, with sessions kept in your history. There is no speech synthesis in the product and no automatic hand-off from a transcript to the assistant — paste the transcript into the copilot yourself.
Right-click any PDF or Gmail attachment and send it to the scanner.
Chrome, Edge and Firefox. Not built yet — scope and permissions will be documented here before it ships.
Deployment
Where LexVio runs, and whose name is on the output.
Air-gapped install via Helm chart. No outbound telemetry when AIR_GAPPED=true.
Runs inside your own Kubernetes, licensed by RS256-signed heartbeats verified before any lookup. Air-gapped mode is enforced by refusal in the application code at each outbound vendor — which means no model inference at all, not inference served locally: there is no configurable model endpoint to point at your own server. Contracted separately from any published plan.
Store your logo and two brand colours. Today they reach transactional email, not exported reports.
PDF and DOCX exports carry LexVio's own header, colours and footer and do not read your brand configuration, so white-labelled deliverables are not available. There is no footer-text field and no way to remove the LexVio attribution. Not included in any published plan.
What is not on this page
There is no marketplace of one-click app connectors. If you need LexVio inside an existing matter-management, ERP, or ticketing system, the route is the Intelligence API plus webhooks — you subscribe to the events you care about and we POST signed JSON to your endpoint.
The identity providers named above are the ones our SAML and SCIM implementations are tested against. Anything SAML 2.0 or SCIM 2.0 compliant should work; tell us what you run and we will confirm before you commit. See security and trust for the controls behind these surfaces, and the full feature inventory for everything else LexVio ships.
Wiring LexVio into something?
Start with the API.
Per-org keys, scoped access, and outbound webhooks on every event that matters.