Praxis Agents OS
View on GitHubRead the docs

Have it built by the person who wrote it.

Greg Asquith wrote Praxis Agents OS. He deploys it inside a small number of companies, connects it to their systems, builds the first agents, and keeps going from there.

Tell Greg about the jobEmail Greg

The software is open source. You can run it without paying anyone. This page is for companies that would rather not do it themselves.

01

First, one real job running.

A scoped project. It ends with Praxis live in your company, doing a piece of work that comes round every week.

  1. 01Pick the first job and the systems it touches
  2. 02Deploy Praxis on your cloud: storage, secrets, sign-in, roles
  3. 03Capture the knowledge, documents and know-how the job depends on
  4. 04Build the agents, skills and tools that job needs
  5. 05Connect your accounts and any internal systems
  6. 06Decide what runs on its own and what waits for a person
  7. 07Test it with the people who will use it, write it up, hand it over
02

Then, a roadmap that keeps adding.

An optional retainer that keeps turning more of what your team knows into work agents can do.

  1. 01New agents, tools and integrations as the team asks for them
  2. 02More teams, more data, more of the business
  3. 03Changes driven by what the audit log and the users say
  4. 04Model, reliability and infrastructure upgrades as the project moves
  5. 05A regular review of what to hand over next
  6. 06Fixes and support for everything already built

Month one gets it running. Every month after makes it do more.

The platform is public. Your business is not.

Improvements to the platform go back into the open-source project. Your agents, workflows, rules, data and internal connections stay private to you.

Open source, upstream

The platform improves in public

  • The runtime, the workspace and the tool registry
  • Approvals, audit and the rest of the governance layer
  • Fixes and improvements that help everyone
  • Integrations with products other people also use
Private, yours

What is built for you stays with you

  • Your agents, their instructions and your business rules
  • Views and dashboards built for your team
  • Connectors to your internal systems
  • Your configuration, credentials, data and history

What usually gets built first.

Every engagement starts with one job that matters and grows from there.

01

Ad account operations

Monday reporting with written commentary, pacing checks, search-term reviews, and campaign changes that wait for sign-off.

02

Data pipelines

Pull, classify and enrich records. Hold the doubtful ones for a person. Push the rest where they belong.

03

Questions over business data

Ask BigQuery or Airtable in English. Get a read-only query, the rows it touched, and a chart you can share.

04

Documents and inboxes

Read the thread or the invoice, draft the reply or the record, and let a person press send.

It works when there is a real job and a real owner.

The engagements that go well start with repeat work that matters, someone inside who owns it, and room to grow past version one.

Usually a fit

Agencies and operationally busy companies with work spread across ad platforms, spreadsheets, inboxes and internal systems. They want to keep their know-how in-house, need an audit trail, and have budget to keep building.

Usually not

A one-off script. General AI exploration with no job in mind. Extra developer hours. Or agents acting with nobody watching from day one.

Tell Greg about the job.

What the work is today, which systems it touches, who owns it, and what a useful first version would change. That is enough to start.

Start a conversationEmail Greg