Praxia Core is open source· star on GitHub →

The command center for your AI coding projects

Praxia is a dashboard for managing many AI coding projects across your local agents — from your phone or any browser. Queue work for Codex, Claude Code, Gemini CLI, OpenCode, or Goose. Your own machine does the coding.

No credit card to self-host Code stays on your machine Bring your own agents
app.trypraxia.com
Portfolio
All projects
6 projects+ New command
72
Recall
Runningclaude
now

Wiring the vector recall API into the timeline view and adding cursor pagination.

~/dev/recall
54
Trading Bot
Queuedcodex
2m

Backtest harness queued — running the new risk model against Q1 data.

~/dev/trading-bot
88
Members Portal
Activeclaude
1h

Magic-link login shipped to prod. Polishing the member directory filters.

~/dev/members-portal
34
SiteLauncher
Blockedgemini
3h

Blocked on DNS verification step — needs a real registrar token to continue.

~/dev/sitelauncher
100
Vault
Doneopencode
1d

Encrypted secrets sync passing CI on all three platforms. Tagged v1.0.

~/dev/vault
18
Auto TA
Stalegoose
6d

Scaffolded the grader. No runs in a while — pick back up on rubric parsing.

~/dev/auto-ta
Why the name

Praxia means applied intelligence.

The name Praxia comes from the Greek word praxis, meaning the practical application of knowledge. Most AI systems help you think. Praxia helps you act.

It turns ideas into projects, projects into tasks, and tasks into completed outcomes. The goal is not simply artificial intelligence. It is applied intelligence.

One dashboard. Every local coding agent.

Claude Code
Codex
Gemini CLI
OpenCode
Goose

Adapter-based, so new agents slot in as they ship. Set a default agent per project — and a fallback.

Why it's different

Not remote control. A command center.

Some tools let you watch or drive one live AI coding session. The hard part isn't one terminal tab — it's keeping track of many projects, many runs, and the context to continue each one.

One live session

Remote terminal control

Streams a single agent in a single terminal tab. Great while you babysit one run — useless the moment you step away or juggle five projects.

Your whole portfolio

Praxia: a project command center

Sits a layer above the sessions. Every project keeps its docs, status, working directory, default agent, queued work, and run history — so you always know what to do next, across all of them.

How it works

Your browser is the remote. Your machine is the engine.

Three moving parts, one clean loop. Praxia coordinates; your computer executes against your local repos.

Browser / phonePraxia + PostgresLocal daemonYour repo → agent

The daemon connects outbound only — Praxia never needs inbound access to your computer.

01

You command from anywhere

Open Praxia in any browser — laptop or phone. Pick a project, read its latest status, and queue a command. The browser never runs shell commands; it just writes the request.

02

Praxia coordinates the work

The dashboard and database hold the source of truth: your projects, docs, progress, and a queue of commands waiting to run — scoped per project and agent.

03

Your machine does the coding

A lightweight daemon on your own computer claims queued commands, runs your chosen agent in the project's repo, and reports results, blockers, and progress back to you.

The project layer

Every project gets a home

Praxia focuses on the layer above your sessions. Each project carries the docs, status, runs, working directory, default agent, and command history you need to keep momentum across the whole portfolio.

Project docs

Each project syncs its README, VISION, and architecture docs so the context to continue is one click away.

Live status

Running, queued, blocked, stale, or done — every project shows a real state and a completion percentage at a glance.

Run history

A full log of commands and results per project, so you can see what each agent did and pick up exactly where it left off.

Working directory

Pin the exact local repo path the daemon should run in. No guessing, no wrong-folder mistakes.

Default agent

Choose Claude Code, Codex, Gemini CLI, OpenCode, or Goose per project — with a fallback agent if the first isn't available.

Command queue

Queue work from the dashboard. The daemon claims one command at a time and runs it safely in the right repo.

Core vs Cloud vs Enterprise

Same product. You pick who runs it.

Praxia Core is the free, open-source, self-hosted version. Praxia Cloud is the managed, hosted version. Praxia Enterprise is a custom install we build and run with you. All keep your code on your own machines.

Praxia Core

Free · self-hosted

  • Manage many projects & agents
  • Run from phone or any browser
  • Code runs on your own machine
  • PriceFree, forever
  • Database & hostingYou run Postgres + Next.js
  • Accounts & workspacesSingle operator
  • Daemon pairingManual key setup
  • Device tokens & audit logs
  • Usage limits & billing
  • Guided AI onboardingDIY via GitHub
  • Updates & supportCommunity / self-serve
  • Custom engines & workflows

Praxia Cloud

Managed · hosted

  • Manage many projects & agents
  • Run from phone or any browser
  • Code runs on your own machine
  • PriceFree to $9.99/mo
  • Database & hostingFully managed
  • Accounts & workspacesAccount + workspace
  • Daemon pairingShort-lived pairing codes
  • Device tokens & audit logs
  • Usage limits & billing
  • Guided AI onboardingAssistant walks you through
  • Updates & supportManaged + priority
  • Custom engines & workflows

Praxia Enterprise

Custom · built for you

  • Manage many projects & agents
  • Run from phone or any browser
  • Code runs on your own machine
  • PriceCustom
  • Database & hostingInstalled on your nodes
  • Accounts & workspacesSet up for your team
  • Daemon pairingWe set it up
  • Device tokens & audit logs
  • Usage limits & billingCustom terms
  • Guided AI onboardingWhite-glove install
  • Updates & supportDedicated + strategic counsel
  • Custom engines & workflowsThree, built for you
Contact us
Setup flow

Up and running in minutes

Pick your path. Self-hosting is a few terminal commands; hosted pairs your machine with a short-lived code — no inbound access required either way.

Self-host (free)

$ git clone github.com/bouttheb/praxia-core
$ cd praxia-core && npm install
$ npm run db:up && npm run db:init
$ npm run dev
# open http://localhost:3030
  1. 1Clone Praxia Core and run npm install
  2. 2Point DATABASE_URL at Postgres (Docker, Neon, or Supabase)
  3. 3Initialize the database and start the dashboard
  4. 4Run the daemon on your machine and add your repos
Read the self-host guide

Hosted (managed)

A guided assistant checks your tools, installs the daemon, and walks you through pairing — so the only thing you bring is your repos.

  1. 1Create your account and a workspace
  2. 2Run the daemon installer and paste your pairing code
  3. 3Confirm the heartbeat — your machine is now linked
  4. 4Import a repo, queue a command, watch the result return
Start hosted
Pricing

Free to self-host. Ridiculously cheap to host.

Praxia Cloud is the managed command center. Your own machine and AI accounts still do the coding work through a paired daemon.

Praxia Core

Self-hosted

The open-source shell you run yourself: dashboard, project docs, command queue, local daemon, and agent adapters.

$0
forever
Self-managed Postgres and hosting. No Praxia Cloud account required.
Get it on GitHub

Free

Try it
$0/mo

Try the hosted dashboard with real projects and one local machine.

  • 5 projects
  • 100 runs per month
  • 1 paired machine
  • 7-day run history
Start free

Lite

Hobby
$3.99/mo

For hobby builders who want Praxia as a daily project command center.

  • 12 projects
  • 300 runs per month
  • 1 paired machine
  • 30-day run history
Choose Lite
Recommended

Plus

Popular
$5.99/mo

For serious solo builders running a portfolio of AI coding projects.

  • 36 projects
  • 1,000 runs per month
  • 2 paired machines
  • 90-day run history
Choose Plus

Unlimited

All day
$9.99/mo

For people who want Praxia open across their whole AI workspace.

  • 100 projects
  • Fair-use unlimited runs
  • 3 paired machines
  • 1-year run history
Choose Unlimited

Praxia Cloud plans do not include AI model usage. Bring your own Codex, Claude Code, Gemini CLI, OpenCode, or Goose setup.

Praxia Enterprise

A custom install, built for your operation

We install Praxia on your infrastructure, build custom engines around your workflows, and stay on to make them better. Three stages, one outcome: an AI operating system you own.

Stage 1
On signing

Foundation

Acquisition, configuration, deployment, and optimization — a live AI operating system running across your nodes.

Stage 2
Months 1–3

Build

Discovery, design, and delivery of three custom engines with their agents and workflows, built around how your operation actually runs.

Stage 3
Ongoing · month-to-month

Compounding

Ongoing optimization, agent tuning, process refinement, and strategic counsel. Cancel anytime.

Full deployment: a complete, owned AI operating system with three custom engines — live in roughly 90 days.

Start the conversation
Built to be trusted

Powerful automation, on your terms

Praxia can ask an agent to change files in a local repo, so it's designed to keep execution and control firmly under your hands.

Your code never leaves your machine

The browser only writes command rows. The daemon decides what it can run, in repos you explicitly add.

Outbound-only pairing

The daemon connects out to Praxia. There's no inbound port into your computer to expose or secure.

Revocable & auditable

Hosted pairing uses short-lived codes and revocable device tokens, with audit events for privileged actions.

FAQ

Questions, answered

Is this just remote control for a terminal?

No. Tools that stream a live session are great for babysitting one run. Praxia works the layer above: it tracks many projects, each with its own docs, status, working directory, default agent, queued commands, and run history — so you can manage a whole portfolio of AI coding work, not one tab.

Where does the code actually run?

On your own machine. A lightweight daemon on the computer that has your repos and authenticated agent CLIs claims queued commands and runs them locally. The browser and dashboard only coordinate — they never execute shell commands.

Which agents are supported?

Claude Code, Codex, Gemini CLI, OpenCode, and Goose today. The adapter design means new agents can be added over time. You set a default agent per project, with an optional fallback.

What's the difference between Praxia Core and Praxia Cloud?

Praxia Core is the free, open-source, self-hosted version you run yourself on GitHub. Praxia Cloud is the paid hosted version that adds managed Postgres, accounts and workspaces, short-lived daemon pairing, revocable tokens, audit logs, usage limits, billing, and a guided onboarding assistant. Both keep code execution on your machine.

Do I need to open a port or expose my computer?

No. The daemon connects outbound only. Praxia never needs inbound network access to your machine, which keeps the security surface small for both self-hosted and hosted setups.

Can I run the dashboard and daemon on different machines?

Yes. A common setup runs the dashboard on a home server or VPS while the daemon runs on the workstation that holds your repos. The daemon always uses its own local paths for working directories.

Is it really free to self-host?

Yes. Praxia Core is open source under AGPL-3.0. Clone it, point it at your own Postgres, and run it for free. You only pay if you choose Praxia Cloud for the managed experience.

Contact

Want Praxia set up for you?

Ask about a guided install, team setup, or anything else. We reply by email.

Take command of every project

Start hosted in minutes, or self-host the open-source Core for free. Your agents, your machine, one command center.