Praxis Agents OS
Maintainer-led implementation

Build your private operating capability on Praxis Agents OS

Work directly with the project's creator to deploy the OS, connect it to your environment, build private agents and views, and extend the implementation against an ongoing roadmap.

The OS is open source. You do not need a commercial licence or Greg's involvement to use it.

01

Initial Implementation

Establish a useful Praxis Agents OS environment around the organisation's infrastructure, systems, governance, and first operating workflows.

  • Workflow and technical architecture
  • Infrastructure, deployment, identity, and roles
  • Custom agents, skills, tools, and operational views
  • Private and external-system integrations
  • Approval, audit, and execution policy
  • Testing, documentation, onboarding, and handover
02

Ongoing Development Roadmap

Continue expanding what the organisation can reliably delegate through a prioritised programme of private capability development.

  • New agents, tools, integrations, workflows, and views
  • Additional teams, systems, data sources, and use cases
  • Improvements driven by operational evidence
  • Model, reliability, governance, and infrastructure work
  • Roadmap review, prioritisation, release planning, and delivery
  • Bounded support and maintenance where it enables the roadmap
Initial implementation gets Praxis Agents OS operating inside your organisation. The ongoing roadmap expands what your organisation can reliably delegate to it.
Ownership boundary

Open upstream, private in your organisation

Reusable infrastructure can improve the open-source project while your agents, views, workflows, business rules, data, and internal connections remain private.

Upstream open source

Shared foundations improve in public

  • Core runtime and platform infrastructure
  • Governance, approval, audit, and execution mechanisms
  • Generally useful framework improvements
  • Reusable integrations with external products and model providers
Private implementation

Your operating capability stays specific to you

  • Agents, instructions, workflows, and business rules
  • Custom views, dashboards, and user experiences
  • Organisation-specific tools and internal connectors
  • Configuration, credentials, data, outputs, and operating history
Example roadmaps

Capability shaped around the organisation

Private development can focus on the workflows and operating controls that matter most to each organisation.

Marketing operations

Reporting, pacing, QA, recommendations, and recurring campaign tasks with review before consequential action.

Data pipelines

Ingest, classify, enrich, structure, review, and route operational data into private tools and workflows.

Operational views

Role-specific dashboards, queues, approvals, exceptions, and audit surfaces around live work.

Documents and invoices

Extract, structure, review, and export information from business records with visible exception handling.

Good fit

A durable operating capability, not general development capacity

The strongest engagements start with an important repeat workflow, a real internal owner, meaningful systems and governance constraints, and room to expand beyond the first implementation.

Usually a fit: unusual workflows, private context, custom interfaces, deployment control, approval or audit requirements, and budget for continued development.

Usually not a fit: cheap one-off scripts, vague AI exploration, staff augmentation, software access without implementation responsibility, or immediate unsupervised autonomy.

Next step

Describe the operating capability you need to establish

Include the workflow, systems, technical constraints, internal owner, and what would make an initial implementation useful.