Use cases
Sentinel fits wherever AI must be in-country and governed. What differs by sector is which guarantee they are actually buying — so the sectors below are grouped by the door they come through.
For telcos & builders
Selling what you build on it. The proof these buyers want is a number — what it cost, what it sold for, and the margin between. See the telco door.
Telcos & operators
Launch an AI revenue line under your own brand. Resell Sentinel on your own markup and prepaid credits, see margin on every request, and give each downstream tenant its own white-label theme and invoice — no model lab, no billing stack to build. Your operations team works in a shared workspace with scoped roles rather than a shared login.
Banking & finance
KYC, support, treasury, and analysis on regulated data — in-country, metered in PKR, with per-key caps, per-tenant quotas, and guardrails that redact PII before a call leaves the pipeline. Spend is attributable per desk and boundable per key, which is what makes AI approvable rather than merely possible.
Developers & startups
An OpenAI-, Anthropic-, and Gemini-compatible API at sentinel.junaid.pk/v1 — point your existing SDK at it, pay in PKR on prepaid credits, and ship on a live 35B model without a foreign cloud account. Start with one key; the same console grows tenants when you have customers of your own.
For defence & government
Proving nothing left. The proof these buyers want is a constraint — demonstrable, and structural rather than procedural. See the defence door.
Government & public sector
Citizen services, executive dashboards, and internal tools on inference that stays inside the country. Residency is a build guarantee rather than a contractual promise, and Sentinel Watch provides an audit trail an assessor can read.
Defence & national security
The Sentinel Sovereign enclave runs air-gapped with external routing compiled out. No data leaves, because the build carries no external-provider client — there is no setting that could send it. Classified traffic is deliberately not usage-metered: counting it would itself leak volume, timing and frequency.