Why now – Palantir alternatives for Europe: what 'sovereign' actually means, and how European public bodies are decidingRegister →
AI & DATA IN YOUR OWN DATACENTRE

AI & Data On-Premises

Your datacentre, first-class. The complete platform on hardware you own — cloud-grade operations, confidential computing, and not a byte beyond your walls.

In Your Perimeter

Run the complete platform on hardware you own and operate — data never leaves your datacentre or edge site.

Confidential On-Prem

Confidential VMs and GPUs on AMD SEV-SNP and Intel TDX keep data and models encrypted in use, on your own hardware.

Cloud to Air-Gapped

The same AI OS runs from Azure-consistent on-prem infrastructure through to fully disconnected, air-gapped networks.

In plain terms

On-premises has a reputation for being the punishment option — last year's software, missing features, everything harder than in the cloud. That penalty is a choice vendors make, not a law of nature. This page describes an on-premises deployment that is the same product, current, and operable by a normal team.

Read this if you're required to keep data physically on your own premises, and unwilling to accept a cut-down product for it.


Definition

On-premises AI & data means running the entire platform — models, agents, ontology, and analytics — on infrastructure you own and operate, inside your own datacentre or edge location. Data and models stay physically within your perimeter and under your control, with confidential computing and zero-trust enforcement available on your own hardware.

Hyperscale cloud is not always an option: data-residency rules, sovereignty mandates, latency, or disconnected sites can require AI to run where the data lives. The AI OS runs entirely on-premises — the same agents, ontology, and insights you would run in the cloud — keeping data, models, and prompts physically inside your perimeter. From Azure-consistent infrastructure with Azure Local through to fully disconnected, air-gapped networks, you choose how much of the cloud operating model to bring in-house without giving up control.

Where it fits

On-Premises in the Scrydon platform

One integrated, sovereign architecture. Here is where On-Premises sits — highlighted against the full stack it works with.

Sync CRM
Verify ID
...
Approve
Welcome

The AI OS for Humans & AI Agents

Revenue Overview — Q2 2026
Connected to Cognitive Enterprise
Revenue
€4.2M
+12%
Pipeline
€11.7M
+8%
Churn
2.1%
−0.3pp
Monthly RevenueJan – Dec 2025
JanMarJunSepDec
Customer
Account
Order
Product
Contract
LineItem
Supplier
Billing
holds
placed
of

Ontology & Semantic Layer, one connected model for your data, knowledge & processes

Combining the best of data lakes, data warehouses and search

TablesKnowledge

AI agents, workflows & automations that execute across your systems

AI Workflows

Integrate across A2A, MCP, legacy systems and data sources

Secure domain federation, trusted data sharing, and cross-boundary intelligence

Sovereign Foundations

Deploy from Air-gapped to Hyperscale
A closer look

On-Premises in depth

Sovereign Foundations

Observability
Full-stack monitoring & alerting
Zero-Trust
Continuous verification
Automation
GitOps & policy-as-code
Key Management
HSM-backed secrets
Kubernetes
Sovereign cluster orchestration
Identity
Federated IAM (SAML/OIDC)

The AI OS only works if it can be trusted. Every layer of the platform rests on a zero-trust infrastructure and identity foundation that operates consistently from fully air-gapped on-premises deployments through to hyperscale cloud environments. Sovereignty is not a feature added on top — it is the condition under which everything else operates.

  • Zero-trust architecture: Continuous verification for every request, every user, and every workload — no implicit trust, even inside the perimeter.
  • Federated identity: Seamless integration with your existing IdP (SAML, OAuth 2.0, OIDC) for unified, policy-enforced access control.
  • Air-gapped deployment: Run the complete platform with no external network dependencies — ideal for defence, critical national infrastructure, and classified workloads.
  • Confidential computing: Hardware-level encryption of data in use via AMD SEV-SNP and Intel SGX, protecting workloads even from infrastructure administrators.

Deployment Options: From Air-gapped to Cloud

IN YOUR DATACENTRE

The full platform, on hardware you control

On-premises deployment runs every layer of the platform inside your own environment. Data and models stay resident in your datacentre or edge location, while you keep a cloud-grade operating model and the same zero-trust and confidential-computing controls used everywhere else.

  • Data resident in your perimeterData, models, and prompts stay physically inside your datacentre or edge site — important for sovereignty and data-residency rules.

  • Confidential computing on-premHardware-isolated confidential VMs and GPUs on AMD SEV-SNP and Intel TDX keep memory encrypted during execution.

  • Zero-trust and identityThe same federated identity and zero-trust access model applies on-premises as in the cloud.

  • Same capabilities everywhereThe same AI OS, ontology, agents, and insights as a cloud deployment — sovereignty never depends on where you run.

DEPLOYMENT OPTIONS

Where you can run the platform on-premises

The AI OS runs across on-premises targets, from Azure-consistent infrastructure in your datacentre to fully disconnected networks — so you can match the operating model to your sovereignty and connectivity requirements.

  • Azure LocalRun the AI OS on Azure Local (formerly Azure Stack HCI) — Azure-consistent infrastructure in your own datacentre, with Trusted-launch VM hardening, and Foundry Local on Azure Local for in-cluster inference.

  • Air-GappedRun the complete platform on fully disconnected networks, with no internet and no external dependencies — sovereignty in its strictest form.

SHARED RESPONSIBILITY

What you run, what we run — and what nobody outside runs

The reason on-premises software has a bad name is usually an unclear line: the vendor assumes the customer will operate things the customer thought were the vendor's, and the gaps show up as stale versions and unpatched systems. This deployment draws the line explicitly. You own the ground and the keys; Scrydon owns the software and how it is released; nobody outside your perimeter operates anything.

LayerYou runScrydon provides
Hardware, network, physical securityYour datacentre or Azure Local cluster, your network boundaryReference sizing and the confidential-computing requirements to meet
Identity and policyYour identity provider, your access policyThe identity and governance enforcement that consumes them
Encryption keysHeld by you; never exportedA platform that works with keys it cannot read
Platform releasesApplied by your team on your scheduleSigned, versioned releases with the same cadence as every other deployment
ModelsChosen and hosted by you, inside the perimeterModel-agnostic serving of open-weight or permitted models
DataNever leavesNothing that requires it to
SupportAccess granted by you, through a path you control — or none at all when air-gappedEngineers who work within that access, not around it

The refusals are the point. There is no vendor-side control plane that must be reachable for the platform to run; no telemetry that has to leave for it to stay supported; no feature held back for the on-premises tier. The current release, the current models and the full AI OS run on hardware you own, operated by a normal team, with the same zero-trust and confidential-computing guarantees the platform gives everywhere.

FAQ

Frequently asked questions

What does running the platform on-premises mean?+
It means running the entire AI and data platform — models, agents, ontology, and analytics — on infrastructure you own and operate, inside your own datacentre or edge location, so data and models stay physically within your perimeter rather than in a public cloud region.
Can I use confidential computing on-premises?+
Yes. On-premises deployments support confidential VMs on AMD SEV-SNP and Intel TDX, and confidential GPUs, so AI inference and training run with data and model weights encrypted in use — on your own hardware, inside your own datacentre.
What is Azure Local and how does it fit?+
Azure Local (formerly Azure Stack HCI) is Azure-consistent infrastructure that runs in your own datacentre or edge location. Running the AI OS on Azure Local gives you a cloud-grade operating model while data stays in your perimeter, with confidential computing available on your own hardware.
How is on-premises different from air-gapped?+
Air-gapped is the strictest form of on-premises: the platform runs on networks fully disconnected from the public internet. Other on-premises options, such as Azure Local, keep data in your perimeter while still allowing controlled connectivity for a cloud-consistent operating model. Both run the same AI OS.
Do on-premises deployments lose any capabilities?+
No. You get the same AI OS, ontology, agents, and insights as a cloud deployment. Because the platform is model-agnostic and can serve open-weight models on your own hardware, frontier-grade AI works without depending on external services.

Or write to us

Tell us what you are working on and who should reply. A person reads it and replies within one business day.

We only use these details to reply to you. Privacy policy

Prefer to write? Email hello [at] scrydon.com and we will get back to you.

Partners

Building the future of Data & AI together with leading innovators. Learn more.
Delaware logo