Manage
Data residency
What runs in Pakistan, how to keep a workload in the country, and what Paranine keeps.
In Pakistan
Paranine's API, dashboard, request logs and billing records run in Pakistan. Your keys, your organisation's records and the metadata of every request are processed and stored there.
Where inference runs
Each model belongs to a pool, shown in the catalogue:
| Pool | Where the model runs |
|---|---|
| PK NPU | Inside Pakistan. Prompts and completions stay in the country. |
| Global | With Paranine's partners outside Pakistan. |
To keep a workload in Pakistan, call PK NPU models and set the key's allowed models to those models only, so it can't be pointed elsewhere by mistake. Residency follows the model you call: there is no setting to forget.
What Paranine keeps
- Request metadata (model, key, status, timings, tokens, cost and tags) for 12 months. This is your request log.
- Account activity: who changed what in your organisation.
- Billing records: credit added and spend.
Prompts and completions are never stored. If a workflow needs them kept, keep them on your side.
Our commitment
The PK Endpoint page states Paranine's residency commitments in full. Where it and these docs could be read differently, that page is the commitment.
Further reading
- What a sovereign AI gateway is: the category, and how to tell a real one from a badge.
- Data localisation, the PDPB and AI: what the bill expects of personal data that leaves the country.
- Paranine launches as Pakistan's first sovereign AI factory: the launch announcement.
Something unclear or wrong on this page? Tell us. Machine-readable copies: llms.txt.