# Different tag definitions for each deployment mode

**URL:** <https://forum.inductiveautomation.com/t/different-tag-definitions-for-each-deployment-mode/114498>\
**Category:** Ignition\
**Created:** [March 16, 2026, 10:44am UTC](https://forum.inductiveautomation.com/t/different-tag-definitions-for-each-deployment-mode/114498 "2026-03-16T10:44:29Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![dmcwilliam](https://avatars.discourse-cdn.com/v4/letter/d/e480ec/32.png) [@dmcwilliam](https://forum.inductiveautomation.com/u/dmcwilliam)\
**Post date:** [March 16, 2026, 7:51pm UTC](https://forum.inductiveautomation.com/t/different-tag-definitions-for-each-deployment-mode/114498/6 "2026-03-16T19:51:27Z")

</div>

> [@pturmel](#):
>
> It is trivial to stand up a trial gateway to run a bunch of simulators. 🤷‍♂️

Are you referring to the Ignition Programmable Device Simulator?

> [@pturmel](#):
>
> I really don't like having different behaviors across dev/test/prod

Yeah I get that, but I guess the whole flexibility of having deployment modes is that it should be possible to have slight differences, if required.

Anyway, back to the original question - is it possible via the UI for us to import different tag definitions using deployment modes or will these always import to core?

Also tagging @paul-griffith for input as the responder to the [original post](https://forum.inductiveautomation.com/t/deployment-mode-tag-definition/114125/7).

---

_[View the full topic](https://forum.inductiveautomation.com/t/different-tag-definitions-for-each-deployment-mode/114498)._