Home / Platform
Platform

The whole stack, delivered working.

A standard application library your employees open on day one, a governance layer your IT office controls, and managed operations under one SLA. The operational machinery stays on our side, and it keeps working because we keep it working.

Built on the certified stack. We add the layer that finishes it.

Hardware, model serving, and the engineer-facing management plane are solved problems, so we build on NVIDIA AI Enterprise and certified enterprise hardware as they ship. Our engineering goes to the layer the substrate leaves open: the finished applications and the governance experience on top.

Your perimeternothing inside leaves
Governed applications
Enterprise chat · retrieval over your corpus · IDE coding endpoint · add-on catalog
We deliver
The Freehold layer — governance & experience
Config-driven control · access & budgets · egress posture · content-free audit · shared memory
We build & operate
NVIDIA AI Enterprise
NIM model serving · Run:ai scheduling & orchestration · validated version matrix
Certified stack
Certified enterprise hardware
Dell · HPE · Lenovo AI factory lines — on your balance sheet, or your cloud tenancy, or none at all
Yours
one SLA · one accountable party · substrate field work delivered by the hardware vendor as our subcontractor

What's in the box.

Three things, delivered together and priced as a configured deployment. Customer differences are expressed as configuration over a fixed catalog, which is what keeps a Freehold deployment fast to stand up and predictable to run.

01

The standard app library

Enterprise chat and content creation, retrieval over your own corpus, and a private coding assistant in the IDE, plus add-on applications from a growing catalog. Every app arrives finished.

The catalog →
02

Governance & experience

Model assignment per app and per group, access and roles, per-person budgets, egress posture, and a content-free audit trail, all operated from a console built for IT generalists.

The console →
03

Managed operations, under one SLA

We operate the platform, gate every upgrade, watch capacity, and hold on-call. Hardware field service is delivered by the vendor as our subcontractor, so your recourse is always us.

How operations work →

A model menu tiered to what the hardware can serve.

The models on the menu and the models loaded in GPU memory, ready to answer instantly, are two different numbers, and VRAM sets the ceiling. The menu is tiered around that fact, with each tier's response behavior disclosed before anyone selects it, and every hosted model shows its capacity with provenance: an industry-benchmark estimate at first, then a number measured on your own hardware.

TierWhat it isWhat you're promised
Hot Pinned in GPU memory, occupying its footprint continuously. The tier for everyday chat, retrieval, and coding models. Answers instantly, always.
Available Loaded on demand from the local cache, freeing its capacity while idle. The tier for the specialized tail. A stated first-call wait, disclosed in the console before anyone selects the model.
External, under your keys Frontier and hosted open models reached through your gateway, with per-person allowances. Capacity taken from the provider's own rate limit, with the data boundary labelled and every call in the audit trail.

Bring your own keys. Claude, Gemini, and other frontier providers plug in under your own accounts. Per-person allowances cap spend, and when an allowance is spent the app falls back automatically to a local model. Cross-vendor optionality keeps your deployment portable: each provider is one entry on your menu, under your keys.

Operations

We hide the platform. Hiding a thing means owning it.

You bought "no ML team, never touch the console," so operating what's underneath is our job, permanently:

  • Upgrade gating. Every platform, driver, and model update is validated against real workloads before your fleet takes it. Updates are pulled from inside your perimeter on a schedule we gate, never pushed in by a vendor.
  • Signed releases. Applications and models update across the fleet through a signed release path. What arrives is what was validated.
  • Drift reversion. The running system is continuously reconciled against its declared configuration. Tampering is detected and automatically restored.
  • Monitoring and on-call. First-line triage is ours; hardware and platform vendors respond behind us, under back-to-back commitments, as our subcontractors.
Accountability

One SLA, hardware to application.

The accountability chain is deliberately simple: you hold us, and we hold our subcontractors. Dell, HPE, or Lenovo field engineers replace a failed GPU in your building; Red Hat and NVIDIA fix defects in their layers; none of that is a second vendor relationship you manage.

The one thing we never hand off is the control plane: the surface where models are deployed, access is set, egress is enforced, and your audit trail lives. It runs inside your perimeter, it holds your keys, and its custody is precisely what you're paying us to own.

Why the control plane stays inside →

Every app plays by the same rules.

The catalog stays coherent because every application, whether first-party, adopted open source, or partner-supplied, enters under the same contract:

Named & versioned

Real product names, real versions, a labelled publisher. You're trusted to know what you're running.

Governed

Access, egress, and model assignment enforced by the same gateway and policy layer as every other app.

Metered

Usage measured the same way everywhere, feeding budgets, capacity planning, and your posture decisions.

Kept current

Updated across the fleet through the signed release path. An app you add today is an app that stays maintained tomorrow.

Explore the application catalog →

See it configured for your constraints.

Tell us your posture requirements and the applications your teams need. We'll walk you through a configured deployment, priced from the catalog.

Talk to us