Overview
How Licensing Works
Our licensing model distinguishes between (a) infrastructure owners and (b) modelling analysts.
Infrastructure owners are organisations — town councils, toll agencies, national government agencies — responsible for managing infrastructure such as a road network. Modelling analysts are individuals who run Juno Cassandra models, analyse the outputs and prepare reports.
A Juno Cassandra licence is purchased and held by the organisation that owns the infrastructure. The commercial relationship is between Lonrix and that organisation.
A modelling analyst working for an organisation needs that organisation’s permission to work under its licence. The licence holder tells Lonrix which analysts to authorise, and we create an account for each of them.
Note on Elements
Each licence has a limit on the number of elements in the infrastructure network. What an element is depends on the type of infrastructure being modelled. For example:
- In a road network, elements are road segments in the model input set
- In a water network, elements are pipe elements
- In a bridge network, elements may include trusses, piers, or other structural components
Licence pricing is based primarily on the number of elements to be used in analyses for the licensee’s network.
Analysts may be staff of the licence holder, or they may work for a third party such as a consulting firm. In all cases they must be formally nominated by the licensee.
The number of people to be given access is agreed with each organisation as part of setting up the licence, based on how you intend to use Juno Cassandra. It may affect the licence cost. Tell us who needs access and what each of them needs to do, and we will work it through with you.
Juno Cassandra Runs in the Browser
Juno Cassandra is a web application. There is nothing to install, no runtime to deploy, and nothing for your IT department to approve beyond normal access to the internet. Models run on our servers, not on your machine.
If you used the earlier desktop version, two things have gone away. There are no longer any computer-specific licence keys — you are not tied to a registered machine, and you no longer need to send us a computer identifier. And there is no software version to keep up to date; everyone is always on the current release.
Accounts and Access
Access is granted per person and per client project.
- Every user has their own account, secured with a password and two-factor authentication. Accounts are never shared.
- An account can be granted access to more than one client. A consultant working for three councils has one login and chooses which client project to work in. Each of those clients must have authorised them separately.
- Two levels of access exist. A modeller can upload inputs, tune the setup, run models and publish results. A stakeholder has read-only access — they can see the project and its results but cannot change anything or start a run. Stakeholder accounts are useful for asset managers and executives who want the outputs without the controls.
Licence Check Process
An analyst signs in with their own credentials and two-factor code.
The system determines which client projects that analyst has been authorised for, and presents them as a choice. All work happens inside the chosen client’s project.
When a model run starts, the number of elements in the input set is checked against the element limit for that client’s licence. A run that exceeds the limit will not proceed.
Building Your Own Domain Model
A Juno Cassandra licence includes the right to build, debug, publish and maintain your own domain model — the part that holds your engineering: how elements deteriorate, when work is triggered, what it costs and how condition recovers.
There is no additional licence fee for this. The Domain Model Assistant — which is what makes it practical for an engineer rather than a software developer — is free and publicly available. See Training for how we support people through it.
The one thing a licence does not cover is the AI coding assistant subscription used alongside it. That is a subscription you hold directly with the provider.
Licence Use Auditing
Our licensing model is designed to be straightforward and easy to use. However, from Lonrix’s perspective there is a critical risk: a dishonest person could attempt to use one client’s licence to perform analyses for other clients who do not hold licences.
To protect Lonrix and licence holders against such misuse, our End User Licence Agreement (EULA) allows Lonrix to collect usage information. This includes when users sign in, which client they are working under, and what work they run. By accepting the EULA, both organisations and analysts agree to this collection and to the audit process.
As per our EULA, Lonrix reserves the right to audit licence usage. Audits may be random or triggered by anomalies. They may include contacting licence-holding organisations to confirm that an analyst is legitimately working for them.
Lonrix also uses anomaly detection to identify irregular use — for example an analyst appearing to use a single licence continuously over a long period, or input sets whose size varies significantly under one licence.
Lonrix will take all reasonable care to conduct audits professionally and discreetly. The objective is twofold:
to protect licence holders against an analyst using their licence for other clients’ networks; and
to protect honest users from unfair competition by those performing work for unlicensed clients, thereby encroaching on the market for compliant users.
End-User Licence Agreement
Every user accepts the EULA on first sign-in, and is asked to accept it again whenever a new version is issued. You cannot use the application without accepting it.
To read the full agreement, click here.