5 Product & traction

The model service and Praxis App have usage and revenue records. September 2026 figures are historical; current capabilities, work in progress, and year-end goals are separate.

Praxis has usage records for its model service and Praxis App, and is turning internally used agent capabilities into platform services businesses can integrate.

Product status

The web version of Praxis App has users; the model service has a common address, public catalog, console, and API documentation generated from official specifications. The internal agent system is used in daily work; internal use, available documentation, and a complete stable external service are different stages.

The table separates existing foundations, work underway, and delivery goals. See the developer documentation for current integration scope; the year-end column states goals, not launch announcements.

ProductExisting foundationWork underwayEnd-of-2026 goal
Model serviceLaunch record; common address, OpenAI and Anthropic compatible interfaces, model catalog, and consoleImprove the catalog and billingStable service with complete documentation
Agent serviceInternal system used daily; service API documentation existsTurn internal capabilities into a complete platform serviceStable service
SandboxResource access foundation and API documentationImprove the service and guidesStable service
SearchResource access foundation; developer page still says not openBuild the service and complete documentationStable service
Praxis AppWeb version with usersRebuild on the cloud servicesWeb, desktop, and mobile
Complete onboardingSign-up, payment, and calls have been run throughRemove the need for staff assistanceFull process works independently

Usage and revenue so far

As of September 2026, the business record showed more than a thousand registered users, hundreds of additions each month, hundreds of monthly active users, and tens of daily active users. Dozens of paying users prepaid for usage; these historical ranges do not prove the current launch scope of the new platform.

More than ten teams connected directly to the model service, with the number growing weekly. Monthly processing ranged from billions to around ten billion tokens, predominantly on Chinese models chosen by users; tokens measure information processed by models.

In the same period, model revenue exceeded purchasing costs, with a gross margin of roughly 20% that was improving month by month. Here gross margin means revenue after purchasing costs, not company net profit; updated periods, definitions, and detailed records remain to be supplied.

The App uses the platform first

Praxis App is being rebuilt entirely on the cloud services as the platform’s first major customer. The team tests capabilities with real work before offering them to external customers.

The App helps developers and businesses build and operate agent services. Personal Agents assist that work, and Service Agents enter the business’s own operations; App use creates resource usage on the platform.

The method has been used in practice

People leading an AI team built the initial platform. People make decisions and accept results, while AI handles much of development and operations; this supports the cost argument in Why now, although a full cost comparison remains to be supplied.

What we aim to deliver by year end

The end-of-2026 goal is stable model, agent, sandbox, and search services, complete API documentation, and independent sign-up, payment, and first use. Praxis App is planned for web, desktop, and mobile, with specialized agents able to learn, be published, and run through the complete process.

We intend to complete each capability first, then deepen it. The next chapter explains customers’ alternatives and Praxis’s position among them.

Export

On this page