Simple, Transparent Pricing

Yes. The Developer plan carries a 14-day trial: it exists so you can connect equipment, build dashboards, and work against the REST and WebSocket APIs before committing. Creating the account costs nothing, the console asks for a card when the trial starts, nothing is charged during the trial, and cancelling before it ends costs nothing either. Any plan showing a Trial Available badge on this page works the same way. In practice, most teams begin by putting real devices from one site onto the platform, wiring up the dashboards and alarm rules that site actually needs, and letting the results make the case internally. Because every plan includes real-time monitoring, alerting, and full API access, the trial runs on the real product rather than a demo environment, and whatever you build during it carries forward when you upgrade. If you outgrow the Developer allotment mid-evaluation, upgrading takes effect immediately and billing simply starts on the new plan.

Not per unit. There is no per-tag license fee and no per-device line item, but every plan carries a device cap and a data allotment, so the question is which tier your fleet lands in rather than whether each tag bills. ControlCom Connect does not license tags the way traditional SCADA and historian products do, where every point you add to a screen or a trend carries its own license cost. Instead, plans are priced by data volume and device count: each one includes a set number of devices, stored variables, messages, and alarms, plus a data retention window, and the numbers are published on this page. Within a tier, instrumenting a machine more thoroughly, adding calculated variables, or trending more signals is an engineering decision rather than a new license SKU, but those data points do count against the stored-variable and message allotment, and a fleet that outgrows its tier moves up to the next one. Map your device count and expected data volume onto the plan table before you commit, and when you cross a plan boundary, the upgrade is a plan change rather than a renegotiated contract.

Every plan, including Developer, includes real-time monitoring, alerting, dashboards, and full REST and WebSocket API access. Industrial protocol connectivity (Modbus, OPC-UA, BACnet, MQTT, EtherNet/IP) is part of the platform, not a per-driver add-on, so connecting a mixed fleet of PLCs, meters, and sensors does not generate a list of module line items. Security is not tiered away either: encryption at rest, edge-to-cloud encryption, enforced multi-factor authentication, role-based access control, and the outbound-only edge architecture are on every plan, as listed on the security page. What distinguishes the higher tiers is capacity and assurance rather than core function: more devices, messages, and alarms, longer data retention, audit logs and SOC 2 report access on Professional and Enterprise, and single sign-on on Enterprise. There are no hidden fees, and the plan comparison table on this page is the source of truth for what each tier includes.

Yes. You can upgrade or downgrade at any time as your device count, data volume, or retention needs change, and billing adjusts to the new plan. Nothing about your configuration is lost in a plan change: dashboards, alarm rules, asset hierarchies, users, and historical data within your retention window all carry across, so moving tiers is a billing decision rather than a migration project. This matches how industrial deployments actually grow: most customers start with one site on a small plan, prove the value, then add sites and devices in steps, upgrading as each allotment fills. Seasonal operations can size down in the off season without dismantling anything. The one thing to plan around is data retention, since each tier includes a stated retention window; if you are downgrading, export or confirm what you need first. There is no lock-in mechanism designed to make leaving or downgrading painful.

The Enterprise plan covers what the lower tiers do not: larger device fleets, longer data retention, more user seats, and enterprise requirements. It is also where security reviews at larger organizations usually land: audit logs and SOC 2 Type II report access come in at the Professional tier, and single sign-on via SAML or OIDC is included on Enterprise, so users sign in through the identity provider your organization already runs. For hybrid requirements, the ControlCom Edge Server runs on your hardware at each site, keeps local HMI panels and threshold alarms working when connectivity drops, and makes outbound connections only, while ControlCom Connect itself runs as a managed cloud service; Enterprise plans size that edge footprint to your fleet. Contact sales with your device count, expected data volume, and retention needs, and the quote gets built from those numbers rather than from a generic enterprise rate card.