Three ways to run it, one product.

Yes. All three tiers share the same configuration model. From Tier 1 to 2: install K3s on the same machine and import the embedded data into PostgreSQL. From Tier 2 to 3: add cluster nodes and switch the backends to TimescaleDB and Elasticsearch, automated by migration tooling. Plan one to two days of migration services per upgrade.

The licence includes the standard MaestroHub connector library: common industrial protocols such as OPC UA, Modbus, MQTT, REST, S7, EtherNet/IP, BACnet, file and CSV, and others. There is no per-connector or per-protocol metering. Specialised industry connectors or advanced modules, if they apply to your use case, are confirmed in the commercial agreement.

MaestroHub is software you deploy, not a hosted service. The central instance's infrastructure is owned and paid for by the customer, wherever it lives. Hosted in a cloud, you pay the provider for nodes, storage and egress, and egress is the main cost that grows with each site. Hosted on premises or at a factory, there are no cloud bills, only hardware and your own network, which is often the lowest total cost when you already own data centre capacity.

The first site covers architecture sizing, network and security integration, connector configuration, training and acceptance: typically two to eight weeks of professional services, depending on protocol mix and integration depth. Each further site under a central instance is configuration only, often done by your own team after first-site training. With local deployments, each new local MaestroHub repeats a slimmer version of the first-site setup. Detailed scoping yields a fixed-bid quote.

Standard Enterprise support includes ticketing and knowledge base access. The premium tier adds 24/7 Slack support. Maintenance releases and security patches are included in all tiers.

MaestroHub follows a quarterly minor-release cadence with monthly security patches. Tier 3 uses rolling Helm upgrades: pods restart one after another and the service continues. Tier 2 is a single-node restart, typically under five minutes. Tier 1 is a native service restart, under a minute per site. Upgrades are customer-controlled: you choose when to apply them.

MaestroHub stores all customer data in open, documented formats: PostgreSQL and TimescaleDB rows, MQTT messages, YAML and JSON configuration. You can export data at any time with standard database tooling, and configurations can be versioned in Git. Source code escrow is available through the commercial agreement. You always own your data, your configurations and your hardware.

Yes. Tiers describe deployment shape, not location. Tier 1 is the lightest option and is typical for a factory that needs local control at one site. But any tier can be placed at a factory site: if the site needs multi-site management on premises, or application-tier high availability of its own, install Tier 2 or Tier 3 there. The reverse holds too: Tier 2 and Tier 3 can live at a factory, in your data centre, or in a cloud.

No, Fleet Manager is optional. Multi-site management is handled natively by a single Tier 2 or Tier 3 instance. Fleet Manager becomes relevant only when you have several separate MaestroHub deployments and want one place for monitoring, licensing and shared sign-in settings across all of them. We recommend it once you have two or more deployments, but you can skip it if you run a single instance.