A working request path
Applications use a familiar endpoint. Administrators choose the providers, models, credentials, fallback rules, and cost strategy behind it.
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 who is asking, how much a request may cost, which rules apply, and whether the provider is healthy. The product runs in AWS today with self-service setup, prepaid billing, managed Bedrock, and company-approved portfolio reports.
- 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 a common checkpoint. A team can start with a single application and keep the same connection as its needs change.
What is working
Evaluate the product, not a slide-deck promise.
The public site shows sanitized product captures and current limits. Qualified recipients can request a dated briefing with more product, commercial, risk, and test detail.
Money controls before spend
Prepaid credit, hard budgets, spend reservations, and reload caps stop excess use as it happens. Teams do not have to wait for an invoice.
Governance in the path
The gateway applies identity checks, policy, and safeguards in one place. Its audit record explains each decision.
Portfolio operating view
Company-approved reports compare cost, budgets, reliability, model use, and key safeguards. They exclude prompts, keys, and 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 provider account and put a single workload behind the gateway. It can then test routes, policy, budgets, and reports in a small rollout.
$499–$1,500 monthly
Company and Portfolio plans add shared administration, reporting, and oversight as usage grows.
From $36,000 annually
Enterprise customers can add identity setup, assurance support, deployment design, and ongoing operations help.
A differentiated expansion path
See each company clearly. Compare a portfolio on common terms.
Private-equity operating teams can compare participating companies on common terms. 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 a short request. We verify the recipient and purpose, then send the approved material to the work email provided.