# Ignition Edge and Ignition Server

**URL:** <https://forum.inductiveautomation.com/t/ignition-edge-and-ignition-server/111361>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [October 11, 2025, 11:44am UTC](https://forum.inductiveautomation.com/t/ignition-edge-and-ignition-server/111361 "2025-10-11T11:44:28Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sudeep\_Kadlak](https://avatars.discourse-cdn.com/v4/letter/s/9f8e36/32.png) [@Sudeep\_Kadlak](https://forum.inductiveautomation.com/u/Sudeep_Kadlak)\
**Post date:** [October 11, 2025, 11:44am UTC](https://forum.inductiveautomation.com/t/ignition-edge-and-ignition-server/111361/1 "2025-10-11T11:44:28Z")

</div>

Ignition Edge and Ignition Server , I want to fetch Ignition Server Tags on Ignition Edge gateway.

Can you suggest any link or step by step procedure to do this

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [October 11, 2025, 12:55pm UTC](https://forum.inductiveautomation.com/t/ignition-edge-and-ignition-server/111361/2 "2025-10-11T12:55:25Z")

</div>

Pretty sure everything in Edge is designed to go the other way. Have you tried creating a remote tag provider in Edge pointing at your standard gateway? (I'm not sure it is allowed, but that is what you would need.)

Consider replacing Edge with Standard.

---

<div class="post-metadata">

**Author:** ![Chris\_Bingham](https://avatars.discourse-cdn.com/v4/letter/c/e5b9ba/32.png) [@Chris\_Bingham](https://forum.inductiveautomation.com/u/Chris_Bingham)\
**Post date:** [October 11, 2025, 6:51pm UTC](https://forum.inductiveautomation.com/t/ignition-edge-and-ignition-server/111361/3 "2025-10-11T18:51:45Z")

</div>

Ignition Edge allows only a single tag provider to be configured. You'll need to use an atypical approach, perhaps using message handlers between the two gateways. You could:

1. Have Edge periodically **request** data from Full (via [system.util.sendRequest](https://www.docs.inductiveautomation.com/docs/8.1/appendix/scripting-functions/system-util/system-util-sendRequest)). Full gateway will need a message handler configured to **receive, process & reply** to this message.
2. Have Full gateway periodically send data to Edge gateway (via [system.util.sendMessage](https://www.docs.inductiveautomation.com/docs/8.1/appendix/scripting-functions/system-util/system-util-sendMessage)). Edge gateway will need a message handler configured to **receive & process** the message from Full gateway.
3. Configure Edge provider as a remote tag provider on Full gateway, build a few memory tags in Edge gateway, then **write to those tags directly from full gateway**. Note that you might encounter some hiccups w/ security if the full gateway (as an unauthenticated actor, or with incomplete service security configured) attempts to write to Edge tags which have strict write permissions configured.

In all of the above, verbose documentation on the Edge tags (identifying the source of the data) will be a life-savor to your future colleagues.

Feel free to provide additional details if you'd like a recommendation on a path forward. What kind of tag data is needed? How frequently must this data be synchronized?