PRAXIS / OPEN SOURCE INFRASTRUCTUREPROXY · AI · POLICY

Built for the traffic ahead

Move fast.Stay in control.

A programmable proxy for your services. An AI gateway for your agents. Explicit policies for the boundaries that matter.

Rust at the core. YAML in your hands.

THE REQUEST PLANE
A foundation for services and AI trafficApplications connect through the Praxis proxy. Praxis AI adds model and tool workflows. Policy Engine is a separate integration for identity, authorization, and data controls. This is a conceptual view of the three projects.ApplicationsCoding agentsMCP clientsServicesAI modelsTools + agentsYOUR CLIENTSYOUR BACKENDSPraxisROUTE / FILTER / FORWARDPolicy EngineIDENTITY + ACCESSPraxis AIMODEL + TOOL WORKFLOWS

APPLICATIONS / AGENTS / MCP CLIENTS

PraxisRoute · filter · forward
Praxis AIModels + tools
Policy EngineIdentity + access

YOUR SERVICES. YOUR AI BACKENDS.

One proxy foundation. Compose the AI and policy capabilities your system needs.
  • 01 / SPEEDNative Rust executionConfigurable pipelines, compiled filters
  • 02 / PROXYYour traffic. Your rules.HTTP reverse proxy + TCP forwarding
  • 03 / AIModels meet agentsResponses, Messages, MCP + A2A
  • 04 / SAFETYBoundaries you defineIdentity, authorization + data controls

01 / PRAXIS · PROXY FOUNDATION

One proxy.
Two paths.

Praxis is a configurable HTTP reverse proxy and TCP forwarder. Compose filters for HTTP requests, handle TCP connections through their own hooks, and extend the framework in Rust.

THE HTTP REQUEST PATHPRAXIS / PROXY
  1. 01 / RECEIVEClient requestEnter the proxy
  2. 02 / COMPOSEFilters + routingShape the request path
  3. 03 / DELIVERUpstream serviceForward the request
Compose HTTP filters and routing before forwarding to an upstream service.
PARALLEL PATH / TCP

Connections have their own lifecycle.

  1. Accept
  2. Filter
  3. Forward
EXTEND / RUST

Build beyond the defaults.

Extend the proxy framework with your own Rust filters.

02 / PRAXIS AI · AGENT WORKFLOWS

Your AI.
In full flow.

Bring Codex, Claude Code, or your application to a gateway for supported OpenAI Responses and Anthropic Messages flows. Compose filters for model mapping, conversation state, tool calls, and guardrails around your chosen backends.

ONE GATEWAYCLIENTS → BACKENDS
  1. 01 / CLIENTSCodex · Claude Code · appsSend supported API requests
  2. 02 / PRAXIS AICompose the AI filter pipelineMap models · manage state · call tools · apply guardrails
  3. 03 / BACKENDSYour models and toolsRoute to configured providers and integrations
Capabilities depend on the filters, build features, and backend integrations you configure.
INTERFACE / 01

OpenAI Responses

POST /v1/responses
INTERFACE / 02

Anthropic Messages

POST /v1/messages

03 / PRAXIS POLICY ENGINE · ENFORCEMENT

Decide what runs.
Control what returns.

Praxis Policy Engine is a separate policy runtime for tools, data, and APIs. Use verified identity and configured rules to authorize an operation, transform its result, or deny it.

ONE OPERATIONEXPLICIT DECISION
INCOMING CALLCaller + operation
PRAXIS POLICY ENGINEIdentity + rulesEvaluate the configured policy
The decision depends on the caller, operation, and policy you configure.
  • 01 / AUTHORIZEAllow
  • 02 / TRANSFORMRedact
  • 03 / STOPDeny

Build in the open

Join the community

Get help in the relevant project, report an issue, or propose an ecosystem change.

Community and contribution paths