One licence.One site. Unlimited.
DjiniousCC is licensed per site — one physical plant — with nothing inside that site metered. No per-tag charge, no client seats, no screen count, no charge for the Digital Replica. Tell us about your plant and we will quote it.
A licence covers a plant, not a number of signals
One site means one physical plant. Everything that plant needs to be supervised, historised, alarmed, drawn, automated and replicated is inside the licence. If you run several plants, each is a site, and an estate is quoted as a group rather than as the sum of its parts.
- Grow the tag count without a conversation about licensing
- Add operators, engineers and viewers freely — there are no seats to buy back
- Build as many screens as the plant needs, in as many concurrent designer sessions as you have engineers
- Connect as many devices and protocols as the plant has
Inside the licence
- Tags
- Unlimited
- Clients and users
- Unlimited
- Screens
- Unlimited
- Device connections
- Unlimited
- Concurrent designers
- Unlimited
- Digital Replica
- Included
What sits outside the licence
Three things are not in the per-site price, and we would rather say so on this page than in month three of a procurement.
Support tier
Response times and coverage hours are chosen and priced per deployment. A plant that runs unattended overnight does not want the same tier as one with an engineer on site.
Redundancy
Hot-standby and high-availability configurations are quoted per deployment, because what has to survive a failure differs by plant.
Professional services
Commissioning, tag mapping, screen authoring, procedure development and training, if you want us to do them rather than do them yourself.
An estate is quoted as an estate
Several plants under one operator are quoted as a group, not as the arithmetic of separate licences. One deployment can run every site in it — a single asset register, one tag namespace and one alarm list across the estate.
We quote on the call.
There is no price list to send you, because the number depends on your plant. So pricing is worked out in the same session where we stand DjiniousCC up against your own tags — bring the site count, a rough tag count, the protocols in the field and what you need supported, and you will leave with a number and with anything DjiniousCC does not do yet.