NewPramaan now supports India data residency for litigation records.Talk to sales
PRAMAANLitigation record intelligence
Talk to sales
AI processors

Approved AI Processors

Last updated: 5 July 2026

1. How to read this page

AI inference can involve both a broker and a serving processor. The broker routes a request. The serving processor runs the model endpoint. PRAMAAN evaluates both layers before allowing a route for customer matter content.

This public page summarizes the approved AI inference posture. The in-product registry and per-run audit trail are the operational source for the exact route used on a given inference.

2. Broker / routing layer

OpenRouter. PRAMAAN uses OpenRouter as the broker/routing layer for current approved global AI inference routes. PRAMAAN configures brokered requests with no-training / zero-or-limited-retention controls and provider allowlists for approved routes.

When a route uses OpenRouter, selected prompts, instructions, source excerpts, metadata, and generated outputs are transmitted to OpenRouter for routing and then to the selected serving processor.

3. Serving processors currently approved for global inference

  • Amazon Bedrock - Claude model family; brokered route through OpenRouter; training excluded; global region class.
  • Google Vertex AI - Gemini model family; brokered route through OpenRouter; training excluded; global region class.
  • Azure OpenAI - GPT model family; brokered route through OpenRouter; training excluded; global region class.

These processors may change as model quality, availability, contractual terms, and residency options change. Material changes should be reflected in PRAMAAN's approved-processor list and audit records.

4. What Zero Data Retention means

ZDR means Zero Data Retention. In practical terms, PRAMAAN uses it as a routing requirement: the inference request should go only to an endpoint whose policy says the provider does not store the submitted prompt, source excerpt, or generated response after processing the request.

ZDR also means that the provider route should not train on customer matter content. It does not mean the data was never transmitted, and it does not mean the inference happened in India. The selected content still travels to OpenRouter and the selected serving processor for the live inference call.

ZDR is separate from PRAMAAN's own audit records. PRAMAAN can still record operational facts such as firm, user, matter, model route, provider, region, time, and policy used, without treating the full prompt or response as provider-retained training data.

5. OpenRouter-accessible provider network

OpenRouter publishes a broader provider network. The providers below were visible on OpenRouter with no-training and ZDR markers when reviewed. They are not all enabled for every firm or every matter by default; PRAMAAN uses approved allowlists, firm policy, and per-run audit records to identify the exact route used.

  • Amazon Bedrock (US) - No training + ZDR
  • Google Vertex AI (US) - No training + ZDR
  • Azure OpenAI (US) - No training + ZDR
  • NovitaAI (US) - No training + ZDR
  • DeepInfra (US) - No training + ZDR
  • AtlasCloud (US) - No training + ZDR
  • Parasail (US) - No training + ZDR
  • Z.ai (SG) - No training + ZDR
  • Weights & Biases (US) - No training + ZDR
  • Fireworks (US) - No training + ZDR
  • Groq (US) - No training + ZDR
  • Morph (US) - No training + ZDR
  • Together (US) - No training + ZDR
  • AkashML - No training + ZDR
  • Inceptron (SE) - No training + ZDR
  • ModelRun (US) - No training + ZDR
  • DigitalOcean - No training + ZDR
  • DekaLLM (ID) - No training + ZDR
  • Venice (US) - No training + ZDR
  • Nebius Token Factory (NL) - No training + ZDR
  • Moonshot AI (SG) - No training + ZDR
  • Decart (US) - No training + ZDR
  • NextBit (ES) - No training + ZDR
  • Cerebras (US) - No training + ZDR
  • Phala (US) - No training + ZDR
  • Wafer (US) - No training + ZDR
  • io.net (US) - No training + ZDR
  • SambaNova (US) - No training + ZDR
  • Perceptron (US) - No training + ZDR
  • Perplexity (US) - No training + ZDR
  • Baseten (US) - No training + ZDR
  • MARA (US) - No training + ZDR
  • Seed (SG) - No training + ZDR
  • Mancer - No training + ZDR
  • Ionstream (US) - No training + ZDR
  • Inception - No training + ZDR
  • Clarifai (US) - No training + ZDR
  • Infermatic - No training + ZDR
  • Reka AI - No training + ZDR
  • Relace - No training + ZDR

Provider policy can vary by endpoint, model family, route, and contractual setting. If a route is materially added, removed, or changed for customer matter content, PRAMAAN should update the approved-processor record and preserve the exact provider and region in the audit trail.

6. Retention and training posture

PRAMAAN-approved AI inference routes are configured so customer matter content is not used to train third-party foundation models. Retention is disclosed as zero or limited retention depending on the route and provider terms.

Do not treat no-training, zero retention, or limited retention as a promise that inference occurred in India. Region and retention are separate controls.

7. Firm-controlled inference policy

Firms with India-only inference requirements can request an India-resident inference policy from the settings panel. The firm chooses its inference policy, can change it, and PRAMAAN records policy changes plus per-run provider and region details in the audit log.

Model quality and availability can differ by residency policy. Global routes may use stronger model families than routes constrained to a single country.

8. Questions

For processor questions or diligence requests, contact legal@pramaan.io.