# Is EAM License a must have when having multiple gateway servers or a nice to have?

**URL:** <https://forum.inductiveautomation.com/t/is-eam-license-a-must-have-when-having-multiple-gateway-servers-or-a-nice-to-have/71264>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [March 17, 2023, 9:53pm UTC](https://forum.inductiveautomation.com/t/is-eam-license-a-must-have-when-having-multiple-gateway-servers-or-a-nice-to-have/71264 "2023-03-17T21:53:44Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Daniel\_Calderon](https://avatars.discourse-cdn.com/v4/letter/d/51bf81/32.png) [@Daniel\_Calderon](https://forum.inductiveautomation.com/u/Daniel_Calderon)\
**Post date:** [March 17, 2023, 9:53pm UTC](https://forum.inductiveautomation.com/t/is-eam-license-a-must-have-when-having-multiple-gateway-servers-or-a-nice-to-have/71264/1 "2023-03-17T21:53:44Z")

</div>

Hi, I'm estimating a solution and the most probable architecture we will use is the "scale out architecture" in the attached picture. The only thing I want to know is if it is necessary to get the EAM license to get the three gateways talking/sharing data, or this is just a nice to have tool when you really want to manage multiple gw from a main one? In my architecture one of the gw would have Perspective license, whereas the other two would only have core and historian.

 ![EAM license](https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/a/fa957005dc74f68542e12d3f575f59023e36b24f.png)

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [March 17, 2023, 9:57pm UTC](https://forum.inductiveautomation.com/t/is-eam-license-a-must-have-when-having-multiple-gateway-servers-or-a-nice-to-have/71264/2 "2023-03-17T21:57:14Z")

</div>

The 'Gateway Network' used for point to point communication between gateways (i.e. sharing tags) is a _platform_ feature; no modules are required.

Remote administration (sending projects between gateways, installing upgrades remotely, etc) is a feature of EAM.

---

<div class="post-metadata">

**Author:** ![Daniel\_Calderon](https://avatars.discourse-cdn.com/v4/letter/d/51bf81/32.png) [@Daniel\_Calderon](https://forum.inductiveautomation.com/u/Daniel_Calderon)\
**Post date:** [March 17, 2023, 10:22pm UTC](https://forum.inductiveautomation.com/t/is-eam-license-a-must-have-when-having-multiple-gateway-servers-or-a-nice-to-have/71264/3 "2023-03-17T22:22:43Z")

</div>

Thanks Paul.

---

<div class="post-metadata">

**Author:** ![msteele](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/msteele/32/77889_2.png) [@msteele](https://forum.inductiveautomation.com/u/msteele)\
**Post date:** [March 20, 2023, 3:29pm UTC](https://forum.inductiveautomation.com/t/is-eam-license-a-must-have-when-having-multiple-gateway-servers-or-a-nice-to-have/71264/4 "2023-03-20T15:29:03Z")

</div>

Related to this, are any integrators using EAM for remote administration during dev/test/deploy then disconnecting the client's gateway instance from EAM/gateway network upon delivery?