# Gateway production infrastructure

**URL:** <https://forum.thegraph.com/t/gateway-production-infrastructure/6534>\
**Category:** Tooling\
**Created:** [April 19, 2025, 11:28pm UTC](https://forum.thegraph.com/t/gateway-production-infrastructure/6534 "2025-04-19T23:28:31Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![a194](https://avatars.discourse-cdn.com/v4/letter/a/a4c791/32.png) [@a194](https://forum.thegraph.com/u/a194)\
**Post date:** [April 19, 2025, 11:28pm UTC](https://forum.thegraph.com/t/gateway-production-infrastructure/6534/1 "2025-04-19T23:28:31Z")

</div>

Although anyone can run a Gateway, there’s no other choice besides the Edge and Node canonical Gateway. I am also quite curious about the possibility to lower the entry bar to expand the Gateway operator set:

- Operators can start small, serving data for niche use cases.
- More flexible cost models.

There’re some general information on edgeandnode/gateway github repo but I also can’t find any official docs on recommended infrastructure to operate a Gateway. Maybe I’ve missed something so I’d really appreciate if somebody can share your ideas/information sources on this. Thanks!
