Skip to content
TAIP

TAIP — The AI Platform

Sovereign AI
infrastructure.

The full AI lifecycle — develop, train, register, serve, operate — running on hardware you own, behind a boundary you control. Speaking the APIs you already use.

on-prem · VPC · air-gapped — zero bytes leave

11
products, one platform
5
GPU vendors supported
12+
model serving presets
2
languages — EN · 中文
100%
air-gap installable
0
bytes leave your perimeter

§ 01 — The argument

AI teams are offered two bad deals. TAIP is the third option.

Rent everything and lose control — or assemble everything and own the debt. We built the platform that should have existed: coherent like a cloud, yours like hardware.

Option one

Rent someone else's cloud

  • Your prompts, weights, and data live on infrastructure you don't control
  • Per-token pricing set by someone else, changed without asking you
  • Their roadmap, their deprecations, their region availability
  • Compliance becomes a negotiation instead of a property

Fast to start. Expensive to trust.

Option two

Stitch a dozen open-source tools

  • JupyterHub + a trainer + a registry + a gateway + a dashboard…
  • Identity, quotas, and audit glued together by your team, forever
  • Every upgrade is an integration project; every gap is your on-call
  • The platform team becomes the product team — unpaid

Free to download. You own the debt.

The third option

TAIP — one platform, your perimeter

  • The whole lifecycle — develop, train, register, serve, operate — on one stack
  • One identity, one quota model, one audit trail across every product
  • Open standards at every seam: OCI, OpenAI/Anthropic APIs, OIDC, OTEL
  • Installs into your data center, your VPC, or a fully air-gapped site

Coherent like a cloud. Yours like hardware.

§ 02 — Proof, not promises

Point your stack at your own perimeter.

No proprietary SDKs, no client rewrites. TAIP speaks the protocols your tools already speak — these are real workflows from shipping products.

change one URL, keep your code
from openai import OpenAI
client = OpenAI(
    base_url="https://inferx.intra.example/api",  # ← the change
    api_key=os.environ["INFERX_API_KEY"],
)
# Anthropic SDKs and claude-code work the same way via /anthropic/v1
# every request lands in the dashboard: cost · P50/P95/P99 · errors

Drop-in for both OpenAI and Anthropic SDKs, streaming included — with per-key budgets, rate limits, and model allowlists.

one env var, every client
$ export HF_ENDPOINT=https://models.intra.example

# everything downstream just works — no client patches
from transformers import AutoModelForCausalLM
model = AutoModelForCausalLM.from_pretrained("meta-llama/Llama-3.1-8B")
# served from your registry; cached from upstream or fully air-gapped

Wire-compatible with the Hugging Face Hub API — including git clone and multi-gigabyte LFS transfers.

real SSH, no kubeconfig
# your laptop → a GPU environment, through the DevSpace bastion
$ ssh alice+jupyter@bastion.intra.example
(jupyter) $ nvidia-smi --query-gpu=name --format=csv,noheader
NVIDIA A100-SXM4-80GB
# idle for 2h → scaled to zero, PVC intact, GPU back in the pool

Native SSH UX — shell, SCP, and port forwarding — authenticated by your uploaded key, no kubectl anywhere.

idempotent from bare metal
$ ./install/00-preflight.sh                      # read-only validation
$ ./install/03-install-cluster.sh --cluster site-a
ok  k8s · cilium · longhorn · cert-manager · envoy-gateway · authentik
# Ctrl-C and re-run is the documented recovery path
# same bundle, same registry, same result — across sites and months

Content-addressed bundles: re-packing a version bump moves only changed layers. One registry serves many clusters.

Standards as load-bearing interfaces —
where one exists, we use it.
We don't invent protocols.

  • OCI
  • OpenAI API
  • Anthropic API
  • OIDC
  • Gateway API
  • KServe
  • Kueue
  • OTEL
  • DRA
  • Cosign
  • eBPF

§ 03 — The suite

Eleven focused products. One platform.

Each product is sharply scoped and ships on its own. Together they share identity, tenancy, policy, and observability — a platform, not a folder of tools.

All products

§ 04 — Why sovereign

Private by design. Unified by default.

Law firms don't send privileged files to outside vendors. Hospitals don't put patient records on shared servers. As AI handles your most sensitive work, it should meet the same bar.

01

One platform, the entire AI lifecycle

Notebooks, training, a model registry, inference, and agents — on a single, consistent stack. One identity, one quota model, one audit trail. Stop stitching together a dozen tools.

02

Governance is the product, not the homework

Per-user namespaces, quotas that repair their own drift, default-deny networking, OIDC everywhere, audit logs, per-token cost attribution. The unglamorous parts, done first.

03

Yours to run, anywhere

Your data center, your VPC, or a fully air-gapped facility — by design, not retrofit. Identity is self-hosted. Images are pre-staged. No node ever needs the public internet.

Bring the platform inside

Your hardware. Your IdP. Your data.

From bare hosts to a working AI platform — connected or fully air-gapped. See how the pieces fit, then see it on your own racks.