System v2.4 operational

The control plane for CLIProxyAPIPlus.

Aiproxy gives your team a structured control plane for activation, provider routing, tenant access, and operational visibility across the CLIProxyAPIPlus runtime core.

Start setupRead docs

Connect providers, issue a tenant key, and complete the first successful call without exposing raw runtime complexity.

System Status

Control-plane readiness across the active runtime surface

Live

Active Nodes

1,402

Across 12 regions

Global Latency

12ms

Edge-to-runtime median

Recent Events

Synced
provider_attach.us-east · success
tenant_key.issue · success
runtime_probe.edge-04 · healthy

How Aiproxy works

Understand the runtime core, the control plane, and the activation path before you scale usage.

Runtime core

CLIProxyAPIPlus remains the runtime core that handles provider-backed traffic execution and request routing.

Control plane

Aiproxy sits above the runtime to manage workspace onboarding, provider connections, and entitlement state.

Tenant keys

Each workspace issues tenant keys through the control plane so access stays tied to plans, activation, and lifecycle controls.

Analytics and admin

Operational visibility, runtime awareness, and backoffice support stay in one SaaS surface instead of being scattered across tools.

Pricing

Simple plans that match workspace growth

Start free while you validate the activation flow, then move to the pricing page when you need higher request volume, more provider slots, and expanded operational controls.

View pricingStart setup

Activation workflow

Connect provider, issue a tenant key, make your first successful request, and observe usage from one control plane.

01

Connect provider

Attach the provider your workspace runtime will use so the control plane can unlock the traffic path.

02

Generate tenant key

Issue a tenant-scoped key that keeps access tied to the workspace, plan limits, and activation state.

03

First successful request

Send the first runtime-backed call and confirm the workspace is ready for real usage.

Operational visibility

See runtime readiness, first-call progress, and workspace state without leaving the control plane.

Entitlement enforcement

Provider slots, key issuance, and activation behavior stay connected to the workspace plan.

Admin support path

Backoffice and analytics stay close to the activation flow so support and operations share the same context.

Ready to activate your workspace?

Start setup when you are ready, or read the docs if you want to evaluate the control plane first.

Start setupRead docs