DEPLOYMENT · MODELS AND HOSTING

Choose the models. Choose where bolde. runs. Set the security level in writing.

Model choice and hosting choice are separate decisions. Select routes for the work and hosting for your environment; confirm both for your deployment.

We label every claim. Planned: not yet verified. On request: scoped and confirmed for your deployment. Available: has a verified release record.

TWO INDEPENDENT DECISIONS

A model route does not decide your hosting.

What may process the work?

Public frontier models · private models · a combination, by agreement.

Where does bolde. run?

Hosting options: On request.

Model routes and hosting are confirmed for each deployment and recorded in its agreement.

FOUR SECURITY LEVELS

Set the boundary that fits the work.

LEVEL 01

Open

Models: Public frontier models, only by separate agreement. Availability is confirmed on request. On request — not yet verified for this site.
Hosting: On request
We run: Defined in your Security Level Schedule
You decide: Defined in your Security Level Schedule
Recorded in: Your Security Level Schedule

LEVEL 02

Hybrid

Models: Private models for sensitive work; public frontier models for the rest, only by separate agreement. On request
Hosting: On request
We run: Defined in your Security Level Schedule
You decide: Defined in your Security Level Schedule
Recorded in: Your Security Level Schedule

LEVEL 03

Private

Models: Private models only. On request
Hosting: On request
We run: Defined in your Security Level Schedule
You decide: Defined in your Security Level Schedule
Recorded in: Your Security Level Schedule

LEVEL 04

Sovereign

Models: Private models on hardware you control. On request
Hosting: On request
We run: Defined in your Security Level Schedule
You decide: Defined in your Security Level Schedule
Recorded in: Your Security Level Schedule

MODEL ROUTES

Choose a model route for the work.

Model routes are private models, customer-provided models, or public frontier models by separate agreement. Public frontier availability is not confirmed for this site; any such route needs a separate agreement and explicit confirmation of the provider, approved data classes, processing boundary and access path.

Route	How it is selected	Status
Private models	Private models, with the supported model and permitted data confirmed for the deployment. Verification record Evidence The Security Level Schedule is a draft and requires a deployment truth-table confirmation for the selected model route. Owner CTO Last checked Not yet verified	On request
Customer-provided models	Private or customer-provided models, with operational and ownership terms set by agreement. Verification record Evidence The Security Level Schedule is a draft and requires a deployment truth-table confirmation for the selected model route. Owner CTO Last checked Not yet verified	On request
Public frontier models	Only by separate agreement, and availability is not confirmed for this site. The provider, approved data classes and processing boundary are recorded for the deployment. Verification record Evidence The Security Level Schedule and deployment truth table must confirm the specific provider, route, data classes and access path. Owner CTO Last checked Not yet verified	On request

These are model routes, not a promise that each individual model is supported. The exact model, permitted data and access path are confirmed for each deployment.

HOSTING OPTIONS

Choose an environment separately.

Environment	Status	Verification record
ASG-hosted	On request	No dated deployment truth-table confirmation is recorded for this hosting option on this site. Owner: CTO. Last checked: Not yet verified.
Your cloud	On request	No dated deployment truth-table confirmation is recorded for this hosting option on this site. Owner: CTO. Last checked: Not yet verified.
Azure	On request	No dated deployment truth-table confirmation is recorded for this hosting option on this site. Owner: CTO. Last checked: Not yet verified.
AWS	On request	No dated deployment truth-table confirmation is recorded for this hosting option on this site. Owner: CTO. Last checked: Not yet verified.
On-premises	On request	No dated deployment truth-table confirmation is recorded for this hosting option on this site. Owner: CTO. Last checked: Not yet verified.
Government cloud	On request	No dated deployment truth-table confirmation is recorded for this hosting option on this site. Owner: CTO. Last checked: Not yet verified.

“On request” means the CTO deployment truth table has not confirmed this option. Your schedule records the selected environment and its boundaries.

PRIVATE AND SOVEREIGN BOUNDARIES

What stays inside your environment?

The answer is written for the selected deployment in its Security Level Schedule. These intended boundaries remain On request until the hosting, model routes and access paths are confirmed.

LEVEL 03

Private

On request

The draft schedule calls for private models with no outside model calls. Before this level is contracted, confirm the host, egress rules, administrative access and where logs are kept.

LEVEL 04

Sovereign

On request

The draft schedule places private models on customer-controlled hardware under customer-held keys. Before this level is contracted, confirm any identity, support or update path that crosses the boundary.

DATA AND INFERENCE

Two boundaries to ask about.

Data residency describes where records are stored. Inference residency describes where a model processes them. The Security Level Schedule records both for your deployment; neither follows automatically from the other.

OWNERSHIP

Review the ownership terms.

Data return and tuned-model terms are shown as Planned in the Trust Center until their owners verify the evidence. Ask to review the terms for your deployment.

Discuss private or sovereign model processing with a principal →