Platform  /  Sealed Cluster
Platform

Sealed Cluster

Dedicated accelerators, dedicated network, dedicated storage. The default product, and the one most customers start with.

A shared endpoint with logical separation is not the same thing as a machine nobody else touches. Sealed Cluster is the second one.

What single tenancy actually means here

  • Your accelerators are allocated to you for the contract term and are not time-sliced, oversubscribed or reallocated between customers.
  • Your traffic runs on a dedicated network segment with no shared inference gateway and no shared load balancer.
  • Your model weights, embeddings, indexes and caches live inside your tenancy and are destroyed on termination to a documented standard, with a certificate.
  • We contractually do not train on your data, do not retain prompts or completions beyond the operational window you set, and do not use your content to improve any model or service.
  • Every one of those statements is written into the agreement rather than a policy page we can revise unilaterally.

Standard configurations

ConfigurationTypical useIndicative scale
Single nodePilot, evaluation, a single high-value workflow8 accelerators
DepartmentalOne business unit in production across several workflows4 to 16 nodes
EnterpriseMultiple business units, mixed interactive and batch16 to 100 nodes
Dedicated hallFull isolation including physical separation and independent power feed100+ nodes

How a deployment runs

Week one, we size. You give us a representative workload — a document set, a task, a volume estimate — and we model throughput on real hardware rather than a spreadsheet.

Weeks two to four, we stand up. Cluster provisioned, model pinned, corpus indexed inside your tenancy, connectors configured, access federated to your identity provider.

From then on, we operate. You get a named engineer, a monthly capacity report, and a change window you control. Model upgrades are proposed, never pushed.

Week 1sizing on real hardware
Weeks 2–4provisioned and indexed
Ongoingnamed engineer, no forced upgrades

Start with one workload.

Most customers begin with a single high-value process and expand once the evaluation numbers are in front of them.