Pricing & access

Tell us what you
need to run.

We agree access with each organisation. Tell us about your study, data and users so we can discuss a price.

Discuss your study ↗

Stage 01 / By agreement

Design Partner

By invitation

Commercial terms agreed individually

Design partners work with us on a real study. We agree what Nohm will support and the commercial terms for each organisation.

  • Working sessions with the product team
  • Separate deployment for each organisation
  • Named contact, working sessions
  • Future terms agreed in writing
Discuss access ↗

Stage 03 / Planned

Public Beta

Self-service, metered

Published pricing at launch

Public beta is planned. It would offer online sign-up and usage-based billing after security and operating checks. There is no launch date yet.

  • Self-service onboarding
  • Automated metered billing
  • Contractual availability and support
  • Wider assistant roster
  • Independent penetration testing required before launch
Register interest ↗

What goes into a quote

Deployment, people
and compute.

01

Platform licence

The proposed annual licence covers the agreed deployment and features. The quote should list the workspaces and updates included.

02

Users

Modellers, reviewers and approvers may need different access. We will agree how many people need each role.

03

Compute

A detailed model across several climate years uses more computing resources than a short analysis. Agree how usage is measured and limited before work starts.

Compare stages / 1 of 2

What each stage includes.

These are examples, not agreed terms. Public beta features are planned.

Features by access stage
FeatureDesign PartnerPrivate BetaPublic Beta (planned)
Analysis StudioIncluded in scopeIncluded in scopePlanned
Visualisation StudioIncluded in scopeIncluded in scopePlanned
Project HubIncluded in scopeIncluded in scopePlanned
Emil · Theo · LolaIncluded in scopeIncluded in scopePlanned
Wider assistant rosterNot includedNot includedPlanned
Separate deployment for each organisationIncluded in scopeIncluded in scopeshared tenancy
Microsoft Entra sign-inIncluded in scopeIncluded in scopePlanned

Compare stages / 2 of 2

Access and security.

These are examples, not agreed terms. Public beta features are planned.

Features by access stage
FeatureDesign PartnerPrivate BetaPublic Beta (planned)
Run history and approval gatesIncluded in scopeIncluded in scopePlanned
Usage tracking and cost limitsIncluded in scopeIncluded in scopePlanned
Hosted PLEXOS solvesNot includedNot includedlicence permitting
Self-service sign-upNot includedNot includedPlanned
Automated billinginvoicedinvoicedPlanned
Contractual availability & supportbest effortagreed per contractPlanned
Independent security assessmentConfirm scopeConfirm evidenceBroader testing planned

Running PLEXOS online is not included in the first two stages. Future access depends on licensing and technical checks.

Access stages

What we need to check
before wider access.

Access depends on the checks below. Ask which ones are complete for your deployment.

  1. 01

    Prepare the deployment

    Separate private data, secure credentials and set up the deployment.

  2. 02

    Private beta

    Before granting access, test sign-in, permissions, usage limits, monitoring and data recovery.

  3. 03

    Run models online

    Running energy models online requires separate workers, a job queue and limits for each run. PLEXOS licensing must also be agreed.

  4. 04

    Public beta

    Wider access would require online sign-up, automated billing, more security testing and support terms. There is no launch date yet.

Commercial questions

Questions to settle
before access.

Why can't I just see a price?

We are still measuring the cost of different workloads. A short analysis and a detailed model across several climate years require different compute, so a single public number would say very little. Tell us the scope and we can explain the proposed charge and how usage would be measured.

What is the minimum commitment?

The proposed private beta has an annual organisation licence and metered compute. Your quote should state the users, usage limits, term and renewal conditions.

Can a run cost more than I expected?

Set a limit for each run and for the organisation before metered work starts. Ask us to show how estimates, approvals and limits work in your deployment.

What happens to my models if we stop?

Agree ownership, export formats, the exit window and retention in the contract. Ask for a demonstration of how your models, runs and documents would leave the platform before you sign.

Do you offer academic or student access?

We consider academic and student access case by case. Tell us about the programme, number of users and work you want to do. Access is agreed explicitly.

Who is behind Nohm?

Terajoule Energy develops Nohm. It grew out of energy studies where modelling, economics and reporting were difficult to keep connected. About Nohm ↗