YAA\IF Platform

Deployment

Run YAAIF wherever it fits your operating model

Same platform, same governance, same audit trail. You decide where the stack lives: on your own bare-metal Linux, inside your cloud tenant, or as a managed service we operate for you.

Option 01

Bare-metal Linux

Deploy directly onto your own Linux hosts, including air-gapped and sovereign environments. No cloud dependency, no call-home, and no shared multi-tenant components. Fits into the operations runbook your platform team already runs.

  • Runs on standard x86_64 or ARM Linux distributions
  • Works air-gapped, with sealed update bundles
  • Integrates with your existing identity, secrets, and SRE tooling

Option 02

Your cloud, your tenant

Deploy into your AWS, Azure, GCP, or any Kubernetes-capable private cloud. The platform lives in your accounts, your VPC or VNet, your region, under your network and IAM controls. Spend stays on your existing cloud commitments.

  • Customer-managed AWS, Azure, GCP, or other Kubernetes
  • Your IAM, your KMS, your network policies
  • Regional pinning for data residency and latency

Option 03

Managed SaaS by us

Prefer to skip the platform engineering? We operate a dedicated YAAIF environment for you on our infrastructure. Same governance, same audit posture, same controls. We handle the upgrades, the patching, and the on-call rotation.

  • Dedicated single-tenant environment per customer
  • We operate the platform, upgrades, and SRE
  • Fastest path to first pilot and first production rollout

The choice is reversible. Customers often start on managed SaaS for the first pilot, then move into their own cloud tenant or bare-metal cluster as governance maturity catches up. Open formats for configurations, workflows, and audit data keep the migration straightforward.

More on the platform

Continue exploring how YAAIF runs

How it works

The five-layer architecture every request flows through.

Trust

The control posture that holds up to internal audit and regulators.

Observability

The Third Eye: every request correlated across seven layers.

Next step

Pick the deployment model for your first pilot

A 30-minute briefing maps the right deployment option onto your operating model: identity, residency, network controls, and SRE constraints.