A working request path
Applications can use one compatible endpoint while administrators control eligible providers, models, credentials, health fallback, and request-cost routing.
Investor overview
Working software for controlling how organizations use and pay for AI.
AI Gateway HQ sits between an organization’s AI tools and model providers. It checks access, cost, security rules, and provider health before a request is sent. The product is operating in AWS with self-service access, live prepaid billing, managed Bedrock, and company-approved portfolio reporting.
- Working production product
- Published pricing and live billing
- Company-approved portfolio reporting
ProductAI cost, access, and routing software
Current stateOperating product in production
Primary usersIT, platform, security, and finance
Customer pathSelf-service through enterprise
Why this exists
AI adoption is spreading faster than the controls around it.
Organizations are adding model providers, coding agents, cloud AI services, and internal applications at the same time. The result is fragmented credentials, inconsistent policy, unpredictable spend, and evidence that is difficult to compare.
AI Gateway HQ gives those requests one checkpoint. A team can start with one application, then keep the same connection as providers, workloads, budgets, and security requirements change.
What is working
Evaluate the product, not a slide-deck promise.
The public site shows sanitized captures and current boundaries. Qualified recipients can request a dated briefing with deeper product, commercial, risk, and validation detail.
Money controls before spend
Prepaid credit, hard budgets, reservations, auto-reload caps, and cost evidence act before or alongside provider traffic—not only after an invoice arrives.
Governance in the path
Identity, policy, safeguards, and reason-coded audit evidence apply at the gateway rather than depending on every application to implement them consistently.
Portfolio operating view
Company-approved reporting compares AI activity, observed cost, budgets, reliability, model mix, and essential safeguards without including prompts, keys, or customer data.
A practical adoption path
Start with one use case; expand when the controls prove useful.
The first step stays economical by using customer-owned provider accounts. Larger plans add shared controls, reporting, identity, deployment options, and ongoing operational support.
Free and prepaid
A team can connect its own provider account, put one workload behind the gateway, and validate routing, policy, budgets, and evidence without a long implementation project.
$499–$1,500 monthly
Published Company and Portfolio plans add the controls organizations need as more applications, administrators, providers, and participating companies share an operating view.
From $36,000 annually
Enterprise customers can add identity integration, assurance support, deployment design, and a broader operating relationship.
A differentiated expansion path
One company is useful. A permissioned portfolio view changes the operating conversation.
Private-equity operating teams can compare participating companies using common definitions while each company keeps its own administrators, credentials, policies, payments, and data.
- Independent companies Every company keeps a separately authorized account and security boundary.
- Explicit approval A company owner approves aggregate reporting and can revoke it immediately.
- Comparable measures Activity, observed cost, budgets, reliability, model mix, and essential safeguards use the same definitions.
- Honest evidence The product labels what the gateway measured and where invoice or business-outcome evidence is still required.
Controlled investor review
Request investor briefingRequest the current investor briefing.
Submit one short request. We verify the recipient and purpose before sending the current approved material to the work email provided.