# Share Data Between Two Ignition Instances

**URL:** <https://forum.inductiveautomation.com/t/share-data-between-two-ignition-instances/115912>\
**Category:** Ignition\
**Created:** [June 9, 2026, 4:18pm UTC](https://forum.inductiveautomation.com/t/share-data-between-two-ignition-instances/115912 "2026-06-09T16:18:29Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![joshua.showalter](https://avatars.discourse-cdn.com/v4/letter/j/9de053/32.png) [@joshua.showalter](https://forum.inductiveautomation.com/u/joshua.showalter)\
**Post date:** [June 9, 2026, 4:18pm UTC](https://forum.inductiveautomation.com/t/share-data-between-two-ignition-instances/115912/1 "2026-06-09T16:18:29Z")

</div>

A data center provider uses Ignition for monitoring assets in their ownership. A client/customer that leases white space in the data center and also uses Ignition for assets in the whitespace that are owned by the client/customer.

The client/customer would like to ingest ignition data from the data center providers ignition into the client/customer's ignition. Each Ignition instance is on it's own.

What is the best way to share data center provider ignition with client/customer ignition?

---

<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:** [June 9, 2026, 4:21pm UTC](https://forum.inductiveautomation.com/t/share-data-between-two-ignition-instances/115912/2 "2026-06-09T16:21:44Z")

</div>

The generic solution is to use WebDev in the data center provider Ignition instance to expose information via an API.

For simple cases, a shared database connection might suffice.

---

<div class="post-metadata">

**Author:** ![tgarrison](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/tgarrison/32/80965_2.png) [@tgarrison](https://forum.inductiveautomation.com/u/tgarrison)\
**Post date:** [June 10, 2026, 2:40pm UTC](https://forum.inductiveautomation.com/t/share-data-between-two-ignition-instances/115912/3 "2026-06-10T14:40:13Z")

</div>

MQTT would also be an option. data center provider could run a broker where they can control access rights to the different topics.

---

<div class="post-metadata">

**Author:** ![michael.flagler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michael.flagler/32/26272_2.png) [@michael.flagler](https://forum.inductiveautomation.com/u/michael.flagler)\
**Post date:** [June 11, 2026, 2:40am UTC](https://forum.inductiveautomation.com/t/share-data-between-two-ignition-instances/115912/4 "2026-06-11T02:40:35Z")

</div>

Why not just use a gateway network connection with a remote tag provider?

---

<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:** [June 11, 2026, 12:37pm UTC](https://forum.inductiveautomation.com/t/share-data-between-two-ignition-instances/115912/5 "2026-06-11T12:37:30Z")

</div>

Gateway Networks allow a lot more functionality than just tags, and would also preclude one org or the other from using the Enterprise module. Not a good fit for this, IMO.