Proposal: Give Praxis AI Its Own Identity

[leseb]

Summary

Give Praxis AI its own name and mission while retaining Praxis as its technical foundation.

[Name] is an open-source gateway for AI and agentic protocols, powered by Praxis.

Motivation

Praxis AI has grown beyond a collection of AI-specific filters. It now provides a standalone gateway with provider translation, routing, MCP/A2A support, response state, guardrails, credentials, and observability.

The current name can make it sound like a Praxis plugin rather than an independently usable product. Agent Router follows a similar model: an independent product identity powered by Envoy.

Proposed mission

Enable applications to use model and agent protocols natively while centralizing translation, routing, policy, state, and observability.

Relationship with Praxis

The new project would own AI and agent protocols, translation, routing, state, and policy.

Praxis would continue to provide networking, TLS, upstream management, load balancing, filter pipelines, and dynamic reload.

In short: the project understands agent traffic; Praxis carries it.

Scope

This proposal would:

• Establish a distinct name, mission, and product identity.
• Position the project as “powered by Praxis.”
• Document the boundary between the projects.
• Preserve existing binaries, crates, configuration, and deployments initially.

It would not require forking Praxis, moving repositories, or immediately renaming technical artifacts.

Open questions

• What should the project be called?
• Should it be described as an AI gateway or an agentic protocol gateway?
• Which technical artifact names should eventually change?

Proposed decision

Approve an independent identity for Praxis AI while preserving Praxis as its foundation and avoiding unnecessary compatibility changes.

[senanz]

+1 I like the idea and it's making sense