Ignition Edge Compared with Ignition
Because Edge is a lean solution, it does have some functionality limitations compared to full Ignition. Ignition and Ignition Edge share the same basic platform, but Edge is a leaner version of Ignition made specifically for use in on edge-of-network devices. Ignition comes with unlimited Tags, Clients, and database connections, while Ignition Edge comes with unlimited Tags, two Clients (one local and one remote) and no database connectivity.
Database access is disabled. This means that any database queries or bindings will not work, and the user sources that require a database connection will not be available. The Status and Configure pages of the Gateway Webpage have been updated to remove these features and reduce confusion. Despite this restriction, some "historical" storage can happen inside of Ignition.
All Gateway level scripting is disabled including Gateway Event Scripts and Tag Event Scripts. This does not affect project or Client-scoped scripts. If you wanted to take advantage of Gateway Events Scripts and Tag Events Scripts with an Edge installation, you can do so through the use of the Compute product. Keep in mind that you will not see the “Gateway Events” menu item in the Designer on unlicensed Gateways. Applying a compute license will require a Designer restart before the menu item will appear.
Gateway and Project Backups
A Gateway backup made in an Edge installation will work perfectly in other Edge installations. Edge Gateway backups are not compatible with Ignition Gateways, so you may not take an Edge Gateway backup and restore it on an Ignition Gateway. Nor may you take an Ignition Gateway backup and restore it on an Edge Gateway.
However, you can still export Tags, windows, and other project resources in the Designer from full Ignition Gateways, and import them into an Edge project, or vice versa.
Edge Gateways only contain a single active Realtime tag provider. Additional providers may not be created.
Edge Gateways contain a single historian provider, which is an instance of an internal historian provider (named the "Edge Historian Provider")
Edge's core functionality and products largely determine which modules run on the platform. Third-party modules will not run on an Edge Gateway, with the exception of any third-party module explicitly stated by a product, such as the Edge IIoT Product.