Foundation

Shared services for secure, observable, and reliable Data and AI workloads.

Agentic Friendly

Foundation is the shared platform layer beneath AI and Data. It turns infrastructure into governed services for identity, inference, networking, observability, storage, databases, policy, workflows, and software delivery.

Most users do not need Foundation component detail. Platform engineers use this section to understand responsibility boundaries, make architecture decisions, and diagnose the services behind a customer workflow.

Foundation capabilities

CapabilityResponsibilityStart with
Identity and policyauthenticate users and services, enforce tenant and team boundaries, and deliver secretsSecurity and compliance
Inferenceschedule and serve models with the required compute, runtime, and gateway behaviorInference
Networkingexpose services through DNS, certificates, gateways, routes, and trust relationshipsNetworking
Observability and auditcollect metrics, logs, traces, dashboards, and operational evidenceObservability and audit
Storage and databasesprovide persistent object, block, relational, and vector storageStorage and databases
Core services and deliveryreconcile configuration, run durable workflows, enforce admission policy, and deliver releasesOperating model

How Foundation supports a request

Traffic reaches a service through the shared gateway first. The gateway terminates TLS and, on routes that carry a gateway policy, validates the presented token. The service then authenticates the caller and authorizes each request against its permissions. The exact components can change without changing the customer-facing contract. Applications integrate through documented product interfaces such as the BSQAI API, while internal services remain behind the Foundation boundary.

Operating boundaries

  • Platform administrators own installation-wide configuration, tenant lifecycle, and each tenant's limits: its deployment policy, its quotas, and its monthly BCU allowance.
  • Platform engineers own service health, capacity, networking, storage, upgrades, and recovery.
  • Tenant administrators own federation, membership, delegation, model access rules, and user and group caps inside one tenant.
  • Application and data teams consume Foundation services through AI and Data interfaces.

Use Core concepts for the installation, tenant, team, and resource hierarchy. Use Deploy and operate for the lifecycle that begins before installation and continues through upgrades and recovery.

Architecture and implementation

On this page