Polyrouter Cloud is the fully-managed router — the same explicit-first routing, fallbacks, budgets and metadata-only cost tracking, without running the container yourself. Get early access.
Polyrouter Cloud is the same router you can self-host today, run for you. One endpoint and one key for every model you use, with explicit-first routing, automatic fallbacks when a provider degrades, hard spend limits that block rather than warn, and metadata-only cost tracking — without a container, a database, or an upgrade path to keep an eye on.
It is the same routing engine, not a reimplementation. A config that works on your own box works on Cloud, and you can move between the two without rewriting how your agents call you.
Self-hosting is the right answer for a lot of teams, and it is available now. These are the reasons people ask us for the managed version instead:
You get one email when Cloud opens, and nothing else. No drip sequence, no onboarding series, and we do not share your address. The only thing we store about you is the address itself — we do not ask for a company, a team size, or a use case, and there is an unsubscribe link on the one email you will get.
Joining the waitlist does not commit you to anything and does not reserve a paid plan. Early-access pricing means the people on this list get the launch pricing when it opens.
One thing we do count, so we know whether writing documentation is worth it: when a signup succeeds we add 1 to a tally of how many people arrived that month from a search engine, from another site, or directly. That tally is a number per month — it is not attached to your address, and there is no row in it that is you. We do not store the page you came from, your IP address, or anything else about the visit, and we run no third-party analytics.
You do not have to wait for Cloud to use polyrouter. It self-hosts with Docker Compose — one app container next to PostgreSQL — under AGPL-3.0, with your keys on your own box and zero markup on what your providers charge.