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
One identity · one quota · one audit trail
- 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.
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.
$ 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.
# 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.
$ ./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.
01 — For AI builders
Everything researchers, engineers, and AI app teams need to ship — from a notebook to production inference.
ConsoleX
AvailableLog in, get a governed Kubernetes workspace. No kubectl, no tickets.
Learn moreDevSpace
AvailableJupyter or VS Code on a GPU in seconds. Idle environments shut themselves down.
Learn moreTrainX
AvailableAdmins write the template. Users fill a form. Kubernetes runs the job.
Learn moreModelSphere
AvailableYour own Hugging Face Hub. Change one env var — every client just works.
Learn moreInferX
AvailableOpenAI- and Anthropic-compatible inference on your GPUs — measured to the token.
Learn moreImageSphere
AvailableAn OCI registry with real identity, runtime-mutable policy, and an air-gap story.
Learn moreAgentX
PreviewAgents as a first-class Kubernetes primitive — versioned, sandboxed, fully traced.
Learn moreGrokX
AvailableGround your agents in your documents — scanned PDFs included, every answer cited to the page.
Learn moreSlurm on TAIP
AvailableYour Slurm scripts, unchanged — running on Kubernetes, with one login, one home, one quota.
Learn more02 — For platform admins
Run TAIP at any scale. Manage users, quotas, GPU pools, and policy from one console.
03 — Cluster foundation
Stand up the underlying Kubernetes plane, identity, and storage that powers TAIP.
§ 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.
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.
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.
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.
§ 05 — Who it's for
Built for the teams that actually do the work.
TAIP is shaped around organizations where data control isn't optional — law firms, hospitals, financial services, government — and the research teams pushing the frontier.
01
AI research labs
From notebook to training run, without leaving the platform
Give researchers GPU-ready dev environments, curated training with live progress, and a clean handoff from experiments to production — all under the same identity and quota model.
Read more02
AI product teams
Ship LLM-powered products on infrastructure you control
Stand up OpenAI- and Anthropic-compatible endpoints, host fine-tuned models, and meter every token on dedicated capacity — with the cost, latency, and privacy your product needs.
Read more03
Platform & infrastructure teams
Run a serious internal AI platform without building one from scratch
TAIP gives platform teams the multi-tenant control plane, policy, and observability that turn a GPU cluster into a real product for the rest of the company.
Read more04
Regulated & on-prem deployments
AI that meets your compliance bar — in your environment
TAIP installs into your data center, your VPC, or air-gapped environments. Bring your IdP, your network policy, and your hardware — TAIP fits in.
Read moreBring 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.