Somebody has to be the neutral layer
New models arrive faster than anyone can integrate them, and every team building on them ends up writing the same fragile routing, retry and cost-tracking code — then rewriting it when the next one lands. Multigrid is that layer, written once so you do not have to.
- 2025
- started
- July 2026
- first release
- 1
- person building it
- 302
- models in the catalogue
Four things we will not trade away
The routing layer should be neutral
A gateway owned by a model vendor will always, eventually, route to that vendor. We sell no model of our own that competes with the catalogue, and our pricing does not reward us for steering you.
Opaque infrastructure is broken infrastructure
If you cannot see which provider served a request and what it cost, you cannot run it in production. Everything we can show you, we show you.
Switching costs are the enemy
We want you to be able to leave. Standard wire format, exportable logs, policies as code. A product that keeps customers by trapping them stops improving.
Charge for value, not for volume
A percentage on tokens taxes your success and gives us an incentive to route you expensively. A seat fee does not. That choice is deliberate and permanent.
Who is building it
One person, in Amsterdam. That is the whole answer, and it is worth knowing before you depend on this.
It is one person
Multigrid is a single developer’s project. There is no support rota, no on-call engineer and nobody carrying a pager overnight. The gateway, the dashboard, the billing ledger and this page were all written by the same person, which is also why a reply may take a day rather than an hour.
What that means for you
Every safety property this product claims is a property of the code rather than of a team: the spend cap is enforced before any upstream call, the ledger is append-only and reconcilable, and your provider keys are encrypted with a key that is not in the database. Those hold at three in the morning whether anyone is awake or not. The Trust Center is blunt about what is missing.
If you are evaluating this for something load-bearing, weigh that honestly — a one-person gateway is the right choice for some workloads and clearly the wrong one for others. The catalogue is 302 models across 6 providers, and 24 of those models can be served by more than one provider, so a single provider outage is survivable. A failure on this side is not, until there is more than one of us.
Getting in touch
There is one contact route and it is the support form in the dashboard, which writes your message to a table that gets read. The email addresses and chat servers this page used to list have all been removed: the domain has no mail routing configured, so they bounced without ever reaching anyone.