Pricing & access
Start with a conversation about what you run. Nohm access is scoped per organisation, with deployment, users and compute considered together.
Discuss your scope ↗Stage 01 / By agreement
By invitation
Commercial terms agreed individually
Organisations shaping Nohm through their own live studies, working directly with the team. Design-partner places and commercial terms are agreed individually.
Stage 02 / By agreement
Annual licence + metered compute
Invoiced directly · quoted per organisation
A bounded analysis workflow on an organisation's isolated stack, with metering and cost controls. Confirm the available studios, deployment safeguards and access scope with the team.
Stage 03 / Planned
Self-service, metered
Published pricing at launch
The intended next access model: self-service onboarding, automated metered billing and contractual support. Availability depends on readiness and isolation checks, not a promised launch date.
How commercials are structured
01
An annual licence per organisation, covering the agreed deployment, aligned data substrate, granted studios and platform updates. Scope and fixed charges are agreed in advance.
02
Named users with access granted per assistant and per studio. A modeller and a reviewer may need different permissions; the quote should reflect the people and workflows involved.
03
Analysis usage measured against actual consumption, with agreed per-run ceilings and an organisation cap. Review the metering and cost controls alongside your quote.
Compare the scope / 1 of 2
Indicative scope, subject to your agreement. Public-beta entries are planned, not available entitlements.
| Capability | Design Partner | Private Beta | Public Beta — planned |
|---|---|---|---|
| Analysis Studio | Included in scope | Included in scope | Planned |
| Visualisation Studio | Included in scope | Included in scope | Planned |
| Project Hub | Included in scope | Included in scope | Planned |
| Emil · Theo · Lola | Included in scope | Included in scope | Planned |
| Wider assistant roster | Not included | Not included | Planned |
| Isolated stack per organisation | Included in scope | Included in scope | shared tenancy |
| Microsoft Entra sign-in | Included in scope | Included in scope | Planned |
Hosted PLEXOS solves are not included in the first two stages. Future availability remains subject to licensing and worker-readiness checks.
Compare the scope / 2 of 2
Indicative scope, subject to your agreement. Public-beta entries are planned, not available entitlements.
| Capability | Design Partner | Private Beta | Public Beta — planned |
|---|---|---|---|
| Run lineage & approval gates | Included in scope | Included in scope | Planned |
| Cost metering & caps | Included in scope | Included in scope | Planned |
| Hosted PLEXOS solves | Not included | Not included | licence permitting |
| Self-service sign-up | Not included | Not included | Planned |
| Automated billing | invoiced | invoiced | Planned |
| Contractual availability & support | best effort | agreed per contract | Planned |
| Independent security assessment | Confirm scope | Confirm evidence | Broader testing planned |
Hosted PLEXOS solves are not included in the first two stages. Future availability remains subject to licensing and worker-readiness checks.
Sequence
Each stage depends on evidence that the previous requirements have been met. Ask which gates apply to your deployment.
Separate private data from deployable assets, manage credentials securely and establish a clean deployment boundary. These are prerequisites, not optional extras.
Invite organisations into a bounded scope. Verify authentication, permissions, metering, monitoring and restore procedures for the deployment before access is granted.
Hosted energy-model solves require isolated workers, a durable queue and per-job quotas. PLEXOS licensing is a separate gate and may limit or prevent hosted execution.
Self-service onboarding, automated billing, broader security testing and contractual support. Shared tenancy follows demonstrated isolation, not an assumed launch date.
Commercial questions
Because cost-to-serve is still being measured rather than guessed. A run's real cost depends on carriers, granularity, climate years and horizon, and those vary by an order of magnitude between customers. We meter it, show you the metering, and quote against your scope — which is slower than a pricing page and considerably more honest.
The proposed private-beta structure is an annual organisation licence with metered compute on top. Confirm seat requirements, caps, term and renewal conditions in your quote.
Agree per-run ceilings and an organisation-wide cap before access starts. Estimates and approval gates are part of the intended workflow; ask the team to demonstrate how limits are enforced for your deployment.
Agree ownership, export formats, the exit window and retention in your contract. Models, runs, assumptions and generated documents should remain usable outside the platform; confirm the supported export route before signing.
Academic and student access is considered case by case. Tell us the programme, cohort size and the studios required; access is granted explicitly rather than assumed.
Nohm is built by Exajoule Ireland with Terajoule Energy, out of consulting work on European energy system studies. It exists because the tooling for that work did not, and it is shaped by the people who had to do it the hard way first. More on the about page . Meet Nohm ↗
Your study / Your scope
Bring the carriers, geography, climate years, time horizon and users you have in mind. Start with the work; agree the terms around it.
Request access ↗