The SaaS Gateway is in Beta. It is fully functional and safe to use for real workloads, but you may see rough edges, and we may evolve details as we learn. Feedback is very welcome.
Self-hosted or SaaS?
Both are the same gateway, with the same guardrails, budgets, routing, and monitoring — the difference is who runs it and where your traffic flows.Self-hosted gateway
Runs in your network. Prompts and completions never leave your infrastructure. You deploy and upgrade the container. Best when data locality is a hard requirement.
SaaS Gateway (Beta)
Runs in Guardway’s cloud, dedicated to your organization. Nothing to deploy or upgrade — ready in about two minutes. Best when you want the fastest path to a governed LLM endpoint.
Data path difference, stated plainly: with the SaaS Gateway your requests flow through Guardway-managed infrastructure on their way to your LLM provider. Your gateway is dedicated and isolated — its own private instance and its own database, never shared with other customers — but unlike self-hosted, traffic does transit our cloud. Request logs are retained for 30 days in the Logs view.
How it works
Every organization gets its own gateway instance behind one shared front door:- Your app calls
https://gateway.guardway.aiwith your Guardway API key. - The edge identifies your organization from the key and routes the request to your dedicated gateway — never anyone else’s.
- Your gateway applies your guardrails, budgets, and routing, forwards the request to your LLM provider, and streams the response back.
Good to know
Where to go next
Set up your SaaS Gateway
One click to provision, first request in minutes.
Manage, redeploy, delete
What each action does — and exactly what happens to your data.