A public API sends your data to someone else's cloud. A DIY platform takes 18 months and a bespoke security review. A consulting build leaves you dependent on the people who built it. Iftah is the fourth path: a productized, governed AI stack running in your own environment — operated by us, audited by you, owned by neither.
Read moreاقرأ المزيدShow lessعرض أقلA public API sends your data to someone else's cloud. A DIY platform takes 18 months and a bespoke security review. A consulting build leaves you dependent on the people who built it. Iftah is the fourth path: a productized, governed AI stack running in your own environment — operated by us, audited by you, owned by neither.
Why the shape wins
The fourth path
Each alternative forces a trade you can't afford in a regulated environment. Iftah keeps the productized spine — but the value is integration of mostly-production components plus a built governance layer, not a from-scratch rebuild.
Control
Answers by default and sends your prompts off-region to be served and moderated elsewhere — the exfiltration you're trying to prevent.
Iftah approach
In-region, single-tenant, default-deny. Guardrails run in your cluster and the audit trail is yours — a hosted API cannot offer this by definition.
Time & risk
A year of security-critical plumbing — identity, policy, guardrails, audit — that you then own and have to defend.
Iftah approach
Reuse the proven, self-hosted serving and request path and wrap your existing stack; Iftah builds only the missing assurance core — no new attack surface for you to own.
Repeatability
Leaves you a bespoke system tied to the people who built it, different at every site.
Iftah approach
One productized platform with the same default-deny baseline everywhere; only your signed overlay differs, and every change flows as signed GitOps — reproducible and attributable.
The governance moat
The differentiator isn't a feature list; it's a single path where every stage refuses to weaken the next. This is the layer DIY teams get wrong and a public API can't offer.
Your Entra ID or Okta is the source of truth; apps and agents get the same treatment. No raw keys, and context comes only from signed tokens — never a header a caller can set.
OPA allows only on an explicit, approved rule. Unknown or newly discovered models deny by default; if policy or audit is down, the request denies.
Presidio and NeMo run as pods in your region — never a SaaS moderation API — tuned for your domain identifiers. PHI buffers before a token can escape.
Approval is pinned to the model's content hash, not its name. The hook pins one approved digest, disables fallback, and records what was actually served.
Every request writes to immutable, hash-chained, in-region storage you control — and if audit can't be guaranteed, new requests deny.
Fail-closed at every stage — deny on timeout, unknown, or unavailable audit. No degraded “allow” mode.
The operating model
The boundary is yours: your cloud account, cluster, region, registry, and IdP. Iftah operates the install inside it — never as a managed service that holds your data.
Residency by topology
A dedicated install in your own cluster and account — no shared SaaS. With models self-hosted in your own cluster and no external callbacks, no code path can carry content across a boundary.
A governance contract
Iftah operates the install remotely but holds no standing access to prompts, responses, or pods. Any content access is client-approved, time-boxed, and logged in your own trail — a hard go-live gate.
Control in, metrics out
Signed artifacts go in — Helm charts and OPA bundles; only health, latency, and version come out. They land in your own registry, so there's no outbound dependency — air-gap friendly.
Never silently default
Local-OPA single-cluster keeps authorization fast and fail-closed. Multi-cloud and hybrid is a supported, content-free-metadata option — shipped only behind a residency assessment, never silently.
Straight talk
Precision matters more than marketing for regulated buyers. The honest boundary, matched to the architecture.
In-region single-tenant residency, default-deny governance, and an immutable WORM audit you control — not merely that it runs inside your infrastructure.
Not a managed cloud that hosts your data, and not a hand-off where you run it alone. Operated for you under audited, break-glass-only access.
We don't train your models. We do produce a signed provenance attestation binding what was approved to what's running, plus measured guardrail gates before PHI go-live. Evidence, not a compliance certificate.
Most of the platform is integration of proven production serving components and your existing repos; the new part is the built governance core: OPA, the enforcement hook, WORM audit, provenance, guardrails.
Next step