Skip to main content
Version: 3.0

Trying and buying

Try it before you decide. All questions

Can we try it ourselves before we buy?​

Available

Short answer

Yes. Download it and it runs a two-hour evaluation, which an administrator can extend from the banner as often as needed. A factory simulator gives you live OPC UA, Modbus and MQTT data without hardware. For a pilot we propose one virtual machine, one line, no production writes and six weeks, with your own people running the checks.

  • The evaluation. A new installation runs the free trial: up to 20 pipelines, 20 connections and 5 users, and the semantic layer on up to 100 topics. After two hours, scheduled pipelines pause and nothing is lost; Extend 2 hours in the banner starts a fresh trial. See Licensing and trial.
  • Data without hardware. The Digital Factory Simulator runs a brake caliper line with OPC UA, Modbus, MQTT, an MES and an ERP. Build your first pipeline takes you from the first connection to a stored value.
  • A pilot. One virtual machine beside one line, reading only, for six weeks. Your engineers run the checks that matter to you, for example stopping a destination to watch the buffer, walking a value back to its PLC address, and verifying the audit trail.

Try it: Install and run, then Get started.

How is it licensed? Per tag, per user, per site?​

Available

Short answer

Per site, not per tag and not per user. Prices are on our offerings page at maestrohub.com/offerings.

  • Editions. Foundation and Enterprise. Enterprise adds Kubernetes, workspaces and Advanced Access Control. See License editions.
  • Add-ons. Some features are added to a licence of any edition, for example Approvals.
  • No count of tags or users. Connect as many machines and signals as the hardware carries.
  • Offline. The licence is a signed key, checked inside the product without a licence server. See Licensing and trial.

You are a young company. What if you disappear? Can we talk to a reference? Who owns our data?​

Available

Short answer

Your data stays in your environment and your own stores, your configuration exports as open JSON, and every release image is signed with a software bill of materials you can verify without us. We have no public references yet; real deployments exist, and their names are not ours to give.

  • Your data. MaestroHub runs on your servers. Its history is a bounded window, and long-term history is written to the stores you already own. See Can we still report on last month or last year?
  • Your configuration. Connections, functions, topics, pipelines and dashboards export as one .mhub.json bundle, a plain JSON file. See Backup & Migration.
  • Our releases. Each release image is signed with Cosign and carries an SBOM (SPDX and CycloneDX) as an attestation, so you can check what you run is what we built.
  • References. None public yet. Real deployments exist, and their names are not ours to give.

We do not ask you to take any of this on trust. Run the outage drill, walk a value back to its source, and call the endpoint that verifies the audit chain yourselves, then decide.