HyperX

First-party agent runtime

Your own AI agent runtime — private, portable, real.

HyperX runs real agents that edit files, run commands, and stream every step back to you. The model catalog is controlled by the server, not shipped in the app — so free and premium models and routing can change without a client release.

Check live status See how it works

Mobile app: not yet released. This page reflects the current backend, which is real and verifiable below.

What HyperX is

A self-hostable runtime built on the official Cline agent engine. HyperX owns the product surface — catalog, routing, limits, entitlements, and workspaces — while the platform underneath stays portable.

Real tool execution

Agents operate in isolated remote workspaces with real file edits and command execution — not scripted replies.

Live in backend

Dynamic model catalog

Providers and models are served live by the runtime and can be enabled, disabled, or rotated server-side.

Live in backend

Free-tier routing

HyperX-managed free models with per-user usage tracking, limits, and health-aware fallback.

Live in backend

Premium & BYOK

Entitlement-gated premium models and bring-your-own-key providers, with credentials kept server-side or in secure user storage.

In progress

Streaming & approvals

Ordered event streaming over SSE/WebSocket with human-in-the-loop approvals and cancellation.

Live in backend

Accounts & sign-in

Verified identity, project ownership, and entitlements enforced server-side. Web sign-in ships with the app.

In progress

Live status

This panel reads the real HyperX runtime health and catalog endpoints. It shows only what the backend actually reports — nothing here is simulated.

Checking…

On the free tier the runtime may be asleep and take up to a minute to answer the first request. If no backend URL is configured for this deployment, the panel stays unavailable by design — it never fabricates a healthy result.

How it works

A single runtime powers free, premium, and bring-your-own-key models — with every routing, limit, and access decision made server-side.

  1. You connect

    Sign in from the app; the server derives your identity from a verified token.

  2. Catalog loads live

    The client fetches the current model catalog from the runtime — no baked-in list.

  3. Runtime routes

    Free, premium, or BYOK access is checked and routed, with health-aware fallback.

  4. Agent executes

    The agent runs real tools in your workspace and streams every step back.

Roadmap

Honest status of what is running today versus what is still being built.

  • Shipped Agent runtime with real tool execution, streaming, and approvals
  • Shipped Dynamic server-controlled model catalog and free-tier routing
  • Shipped Verified authentication boundary with owner-scoped authorization
  • In progress Public accounts, entitlements, and premium/BYOK onboarding
  • In progress First-party mobile app release
  • Planned Public team features and advanced project controls

Security & privacy

Server-side secrets

  • Provider API keys and JWT secrets live only on the server.
  • They are never embedded in the site, app, or logs.

Verified identity

  • Identity comes from a server-verified token, not client input.
  • Projects and sessions are scoped to their owner.

Fail-closed

  • Production refuses requests without a valid token.
  • No development bypass is ever used in production.