Sovereign Deployment — Your Data. Your Infrastructure. Your Intelligence.

Deployment models

Four models. No hidden fifth tier.

Each model below states plainly what remains inside your own environment. Where a capability is still being confirmed by NourSoft's product and architecture teams, it is labelled as such on this page rather than presented as shipping today.

01

On-Premise

NourNexus runs on customer-controlled infrastructure inside your own data centre. Source content, extracted text, derived structure, indexes and the knowledge layer all remain on hardware your organization operates.

Stays inside your environment

Source documents and media
Extracted content, entities and metadata
Semantic index and knowledge layer
Audit trail and access decisions

02

Isolated / Air-Gapped

Operation inside an environment with no external network connectivity, for the most tightly controlled government and enterprise estates. Nothing traverses an outbound connection because no outbound connection exists.

Stays inside your environment

Everything in the On-Premise model
Model artefacts and processing, with no external inference calls
Updates applied through your own controlled media process

Planned capability, confirmation pending

Applicability to specific NourNexus and C-MIND functions is being confirmed by the product team; this page does not claim it as available across every capability today.

03

Private / National Cloud

Deployment into a controlled hosted environment dedicated to your organization, aligned to your data-residency requirements rather than to a shared multi-tenant public service.

Stays inside your environment

Content and derived knowledge, within your tenancy and residency boundary
Identity, access policy and audit under your control
No obligation to ship sensitive content to a public API endpoint

Terminology pending validation

The exact naming of this model is pending final validation by NourSoft's architecture team and may change before publication.

04

Hybrid

Workload placement according to business, security and governance requirements. Sensitive processing is held locally while elastic or non-sensitive workloads run in a controlled cloud environment.

Stays inside your environment

Whichever classifications your policy designates as local-only
The governance decision itself — placement is policy-driven, per workload
A single integration surface across both halves of the estate

NourNexus is designed to keep sensitive processing inside your own infrastructure wherever your deployment model requires it.

Consistency across models

The deployment changes. The platform does not.

Choosing a model should be a governance decision, not an architectural rewrite. The same capabilities, the same integration surface and the same governance controls are intended across all four.

Capability consistency across the four NourNexus deployment models
Aspect	On-Premise	Isolated / Air-Gapped	Private / National Cloud	Hybrid
Content stays in your environment	Yes	Yes	Within your tenancy and residency boundary	By policy, per workload
External network dependency	None required for processing	None — no outbound connectivity	Within the controlled environment	Only for the workloads you place there
Document and Arabic intelligence	Same capability set	Same capability set	Same capability set	Same capability set
Integration surface	One API-first interface across every model — illustrative developer experience
Governance & audit	Identity, role-based access, classification, lineage and audit apply in every model
Status	Roadmap framing — confirm with product team	Confirmation pending	Terminology pending validation	Roadmap framing — confirm with product team

Status labels follow the Product Truth & Evidence System: NourNexus is described throughout as a platform in active rollout, and no row above should be read as a commercial guarantee before product leadership confirms it.

Choosing a model

Start from the content, not from the infrastructure.

The right model usually follows from three questions your governance team has already answered.

Question 01

What is the highest classification in scope?

The most sensitive class of content in the estate sets the floor. If that class cannot leave the organization, the processing for it cannot either — which points to On-Premise, or to Isolated where the environment permits no connectivity at all.

Question 02

Where must the data physically reside?

Residency requirements determine whether a controlled hosted environment is acceptable at all, and if so, where it must sit. This is the question that separates Private / National Cloud from the two fully local models.

Question 03

Does every workload carry the same constraint?

Often it does not. When a minority of content carries the strict constraint and the rest does not, Hybrid lets you apply the strict treatment where it is genuinely required instead of across the whole estate.

Regulatory posture

Designed to support alignment with Saudi data governance and cybersecurity requirements.

What this page states

NourNexus is designed to support alignment with Saudi data governance and cybersecurity requirements.
Deployment models are intended to let sensitive content remain inside your own environment.
Governance controls — identity, access, classification, lineage, audit — apply to derived knowledge, not only to source files.

What this page deliberately does not state

No claim of NCA, NDMO or SDAIA certification, accreditation or endorsement.
No compliance guarantee on behalf of your organization — alignment is a shared responsibility with your own governance function.
No uptime, throughput or accuracy commitment, and no customer names or endorsements.

Any certification statement will be published only against documented evidence supplied by NourSoft. Until then, this page uses the wording above verbatim.

Next step

Deploy intelligence where your policy allows it to live.

Bring your governance constraints to the conversation. We will work through which of the four models fits, and what that means for your content in practice.

Request a Demo Talk to an Engineer

Executive and technical journeys both start here — or open for a quicker answer.