Nuclearn Book a demo
Platform Governance and deployment

Your instance.
Your sign-in, your rules.

Each plant runs in its own single-tenant instance, hosted by Nuclearn in its own datacenter on its own hardware, with hosting, operations and support set up for 10 CFR Part 810 export controls. Access goes through your identity provider and the platform's roles.

Access control

Who can see what, and what they can do.

People sign in through the identity provider your plant already runs. Its groups become roles in Nuclearn, and every collection, project and chat carries its own access list.

  • Microsoft Entra ID
  • Okta
  • Ping Identity
  • Any OpenID Connect provider
  • LDAP and Active Directory

Single sign-on

Sign in through Microsoft Entra ID, Okta, Ping or any OpenID Connect provider. Accounts are created at first sign-in and matched on the provider's stable user ID.

Your groups become roles

Groups from your identity provider map to Nuclearn roles when people sign in. The admin screen lists the group names the provider has sent, so the mapping is set up without trial logins.

Who may sign in, and how

Sign-in can require claims from your identity provider, such as membership in a group. With single sign-on only, the password form is switched off.

Roles for what people can do

Editable roles with per-feature privileges decide which tools and admin screens each person can use. Permission changes are recorded.

Access lists on every object

Collections, projects, chats, agents, models and artifacts each carry an access list: people, groups or roles, at view, edit or manage. A project's access carries down to its subfolders, and sharing an agent doesn't share the documents behind it.

Search sees what you can see

Search, and the assistant's search tools, return documents from the collections the signed-in person can read and no others.

Microsoft Entra ID, Okta and Ping Identity are trademarks of their owners.

Governance

What the AI can do, and what it leaves behind.

Products switched on per deployment

Each product is a licensed module, switched on for your instance. The next one uses the same sign-in and roles.

Web access off by default

Web search and fetching web pages stay off until an administrator turns them on, and each web search shows its query first. Public NRC and DOE sources are searched through their own tools.

Approval before anything goes out

Emails an agent drafts wait for a person to review and approve them. Workflow stages can stop for approval.

A trail you can export

Each answer's sources export as a PDF report or a JSON audit trail, for one answer or the whole conversation.

Sharing

Share a project with the people who need it.

Projects hold files and chats. Share one with people or groups as view only, can edit or manage, and the rights carry to its subfolders.

The project's share dialog: add people or groups with view-only rights, and include all subfolders.
Where it runs

Our hardware, in a Part 810-compliant datacenter.

Each plant's single-tenant instance runs on servers Nuclearn owns, in Nuclearn's own datacenter, which is compliant with 10 CFR Part 810 export controls. It isn't on a shared public cloud.

A row of server racks in Nuclearn's datacenter, on a raised floor with perforated cooling tiles.
Nuclearn's datacenter, where plant instances run on Nuclearn-owned hardware.

Single-tenant, hosted by Nuclearn

Your plant's own instance, hosted by Nuclearn in its own datacenter on its own hardware. Azure Government or your own servers on request.

Set up for 10 CFR Part 810

How Nuclearn products are hosted, operated and supported is set up for 10 CFR Part 810 export controls.

A certified company

Nuclearn's information security management system is certified to ISO/IEC 27001:2022. See the certificate →

Request a meeting

Bring your security team's questions.

We'll walk through hosting, sign-in, data and the certificate with your IT and security staff.

Request a meeting