praxonneGitHub

Programmable proxy runtime · private preview

Every request can become a reviewed capability.

Praxonne connects forward and reverse proxy requests through bounded child processes. When a route needs new behavior, an approved AI bridge can generate a candidate, test it against the live contract, and propose the successful code as a draft pull request.

Explore the architecture Read the security model

Successful response ≠ trusted code. Human review and deployment policy stay in control.

request
PXpolicy gateway
fork()child workload
2xxcontract result
gitdraft PR
request → responseisolated, observable, reviewable
forward + reverseprocess isolatedschema governedPR native

The request lifecycle

A proxy that can learn—without skipping review.

Each request is isolated in a child process. A missing capability can produce a candidate implementation, but shipping remains a Git workflow.

  1. 01Route

    Match a forward or reverse route against explicit tenant policy.

  2. 02Fork

    Connect the request and response inside a bounded child workload.

  3. 03Generate

    Ask an approved agent bridge for a narrowly scoped candidate.

  4. 04Evaluate

    Run contracts and policy checks; status 200–302 is only one signal.

  5. 05Propose

    Push a feature branch and draft PR with provenance and purpose.

Model-agnostic bridge

Generate through a boundary you can replace.

Praxonne does not bind proxy execution to a model vendor. Provider-specific credentials and protocols stay behind an agent bridge with allow-listed operations, bounded context, and auditable outputs.

See every promotion gate
01
Gemini 3.6 Probridge profile
candidate only
02
ChatGPT SOL 5.6bridge profile
candidate only
03
Claude Fablebridge profile
candidate only
+
Your modelsame contract
portable

Profile names are deploy-time configuration supplied by the operator; they are not claims of provider availability or a released bridge integration.

One system, explicit boundaries

Built as a fleet—not a mystery box.

01

Proxy plane

Forward, reverse, and bidirectional services isolate request work.

02

Control plane

Rust APIs, a Leptos web surface, CLI, Flutter, and native desktop clients.

03

Contract plane

Shared interfaces and JSON Schema keep services and 15+ SDK targets aligned.

04

Operations plane

Cloudflare Workers, Kubernetes app-of-apps manifests, and declarative data schemas.

The non-negotiable

Code can propose itself.
It cannot approve itself.

A `200..=302` response makes generated code eligible for review. Promotion still requires deterministic tests, provenance, an allow-listed repository, a feature branch, and a draft PR that explains what changed and why.

View the developer surface