Frequently asked questions

Waygrid is an enterprise platform that unifies API management, security, observability, and AI governance in a single control plane. Six products share one policy engine and one audit trail, so a rule defined once applies consistently across your entire digital estate.

No. Most customers start with one product, often the API Gateway or a gateway consolidation, and adopt others as needs arise. Because every product shares the same foundation, each addition inherits the policies, catalog, and audit trail you already have.

Waygrid is designed to extend existing investments, not replace them. It runs in front of legacy systems, exposes modern APIs on top of older services, integrates with your identity provider, and exports operational data to the monitoring tools your teams already use.

Most organizations route their first production traffic through Waygrid within weeks and complete a full transition within a quarter. Every customer is supported by a dedicated solutions engineer and proven migration playbooks for the most common legacy gateways and ESBs.

Yes, coexistence is the standard approach. Traffic moves route by route on your schedule, endpoints and contracts stay stable for consumers, and every step can be rolled back instantly if anything looks wrong.

Every customer is assigned a named solutions engineer, meets with us for quarterly architecture reviews, and has a direct phone line staffed 24/7 by Waygrid engineers. Priority incidents receive a response within 15 minutes.

Waygrid's controls are mapped to ISO 27001, SOC 2, PCI DSS, GDPR, and DORA, with evidence exports designed to drop straight into your audit workpapers. Waygrid itself has passed every ISO 27001 and SOC 2 audit since 2019.

Every access decision and configuration change is recorded in a tamper-proof audit log with seven-year retention. When a regulator or auditor asks how a specific transaction was handled, the answer is a query, not an investigation.

Yes. Waygrid integrates with any OIDC or SAML identity provider, alongside mutual TLS and API-key flows. Policies are enforced consistently across all of them, so nothing needs to be standardized or replaced first.

Because AI traffic carries the same obligations as the rest of your data, and adds new ones: unpredictable costs, sensitive prompts, and fast-moving provider choices. The AI Gateway gives your organization one governed point of access to every LLM provider, with budgets, data protection, and a complete audit trail.

Your organization sets budgets by department, team, and application, and Waygrid meters every interaction in real time against them. Semantic caching answers repeat inquiries from previous results, which typically reduces spend on that traffic by 30 to 40 percent.

More than fifteen LLM providers, alongside your own private model deployments. Routing is provider-neutral: if one provider is unavailable, traffic shifts automatically to your designated alternatives with every policy still enforced.

Three models, one platform: fully managed in Waygrid Cloud across 28 regions, in your own AWS, Azure, or GCP environment managed by our control plane, or on-premises in your data centers. You can change models as your strategy evolves.

Yes. The on-premises deployment delivers the same product as our cloud, as signed releases you control, with FIPS-ready builds for the most regulated environments. Data residency is enforced by policy, so traffic and records stay in the jurisdictions your regulators require.

Traffic fails over automatically to the nearest healthy region under the continuity policies you define. Our 99.99% uptime SLA is measured monthly and credited automatically if we ever miss it.

Each product is priced on a usage metric that matches its value, such as API requests, managed APIs, or AI tokens, with volume tiers for enterprise estates. Full details are on our pricing page, and our team will gladly model your specific usage.

Very deliberately so. Waygrid has shipped ten major platform versions without a breaking change for customers, and every customer-facing feature carries a minimum 18-month deprecation notice, so your programs can plan in years, not sprints.

Start with a demo tailored to your architecture. From there, most organizations run a scoped proof of value on a real use case, supported by a solutions engineer, before committing to a wider rollout.