WHY IFTAH AI
Put models and agents into production with integrated identity, policy, access, and audit controls in your environment.
YOUR PRIVATE AI PLATFORM
IFTAH AI
Governed models, agents and tools inside your environment
Compare deployment control, integration responsibilities, and ongoing operations across four approaches to enterprise AI.
Model and infrastructure choice stays with your organization.
ONGOING OWNERSHIP
Your organization integrates provider controls with its identity, data, risk and audit requirements.
ONGOING OWNERSHIP
Internal engineering owns continuity, control evidence, incident response and release management.
ONGOING OWNERSHIP
Responsibilities transfer from the implementation team into a sustainable customer operating model.
ONGOING OWNERSHIP
Iftah maintains the platform; the customer retains authority over its environment, data, identity, keys, approvals and final decisions.
Iftah maintains the platform, with clearly agreed responsibilities for infrastructure, access, support, and operations.
Apply governance before each model, data, tool, or external-service action. Each stage can allow, block, or require approval according to your policies.
A request or agent action passes through identity, policy, data controls, model and tool routing, approval and execution, and audit evidence. Each stage may allow, block or require approval.
Who is making the request?
Resolve the user, workload, application, role and approved identity context.
Is this use permitted?
Evaluate workload, data classification, model, destination, requested tool and policy.
Can this information be processed?
Apply configured controls to restrict, detect, mask, block or escalate sensitive content.
Which approved capability may be used?
Route to permitted models, retrieval sources, enterprise tools and approved endpoints.
May the action proceed?
Allow, require human approval or block agent tool calls and business-system actions.
What happened and why?
Record relevant context, decisions, selections, approvals, outcomes and enforcement actions.
ALLOW
The governed path continues
APPROVAL REQUIRED
Execution pauses for an authorized decision
BLOCK
The requested path stops
Configured enforcement points can deny execution when identity, policy or required controls are unavailable.
A finance agent requests an export containing restricted data. Configured classification policy blocks the tool call and records the denial before execution.
Define local data processing, permitted external services, and administrative access before production.
The Iftah control layer runs within a customer-approved environment. Optional external models, enterprise services, telemetry and support sessions connect only through explicitly enabled and policy-controlled paths.
CUSTOMER-APPROVED ENVIRONMENT
IFTAH AI CONTROL LAYER
Identity · Policy · Guardrails
Approved external model endpoint
POLICY-CONTROLLED
Document telemetry fields, processing locations, content exclusions, and disablement controls for the selected architecture before enabling outbound reporting.
Give architecture, security, and procurement teams a clear view of deployment, dependencies, access, and control evidence for production approval.
REVIEW ARTEFACTS
Shows component, data, storage and external-connection placement.
Identifies deployed components, services, connectivity and outbound operational data.
Maps relevant risks to enforcement, policy, approval and operating responsibilities.
Defines who may administer, how access is approved, duration and records.
Documents recorded requests, decisions, approvals, selections, tool calls and outcomes.
Defines transferable policies, configurations, logs and platform artefacts.
Next step