01 Sessions
Launch and mirror Claude Code or Codex sessions per company, from any browser or your phone. A dedicated session host keeps terminals alive across restarts.
SELF-HOSTED · SOURCE-AVAILABLE · HUMAN-IN-THE-LOOP
The command deck for running many companies with a few humans.
Plexward turns one machine into an operations center for your whole portfolio: launch AI coding sessions per company, read morning briefings, watch spend roll up, and approve every outbound message from your phone. Your data never leaves your box.
One deck, every station.
02 Briefings
Daily and weekly situation reports per company plus a cross-portfolio roll-up: blockers, next steps, and what actually needs you today.
03 Approvals
Outbound messages are drafted by agents but sent by you. Approve, edit, or reject from Telegram. If the gate is down, nothing sends. Fail-closed, always.
04 Comms
A read-only WhatsApp digest pipeline and a cron-driven inbox triage across Slack, Gmail, Notion, and HubSpot, folded into each company's brain.
05 Studio
On-brand social images, carousels, and rendered video reels per company, generated locally and staged for one-click export.
06 Knowledge
Every company gets a "brain": a git repo of context, decisions, and artifacts that agents read first and index nightly.
The floor: every agent, live.
Sessions is mission control for the agents themselves. Every terminal across every company, mirrored live: open one, watch it think, take over the keyboard when you want to.
Wake up already caught up.
Every morning, each company's agents compile what moved, what's blocked, and what needs a decision, then a roll-up tells you the two things that actually matter today.
Every company, one keystroke deep.
Spend, calendar, open items from its real tracker, and quick-launch into a scoped agent session that already knows the company's context.
Nothing sends without you.
Agents draft, you decide. Every outbound message becomes an approval in your Telegram: Approve sends it, Edit sends your corrected words instead, and the correction is remembered. Reject, or just ignore it, and nothing ever leaves.
The deck keeps score: pending queue, decision history, and a correction rate per company that tells you which agents have earned looser reins.
Forty seconds, the whole deck.
Morning briefing, drill into a company, back out to the portfolio board. This is the entire loop of running a holding on Plexward.
Deploys like a tool, not a platform.
$ git clone github.com/plexward/plexward
$ cd plexward/control-center
$ bin/mc-setup
$ python3 server.py
Plexward on http://127.0.0.1:8099- Stdlib-only core. The dashboard runs on bare Python 3.11. No pip installs, no build step, no framework.
- Everything degrades. WhatsApp, Telegram, video, GPU: each subsystem is optional and fails soft.
- Any Linux box. A 4GB VPS runs the core; 8GB is comfortable with WhatsApp. Phone access over your tailnet.
- Your keys, your data. Secrets live in files you own. Business data never enters git, let alone anyone's cloud.
Built paranoid, because it runs your companies.
LOCALHOST ONLY
Every service binds 127.0.0.1. Remote access goes through your tailnet or an access-gated tunnel, never an open port.
FAIL-CLOSED SENDS
No WhatsApp message leaves without a human pressing Approve in Telegram. Gate down means nothing sends.
READ-ONLY PIPELINES
Digests and triage consume message streams; they never write back. Auto-send is per-rule opt-in, off by default.
NO TELEMETRY
Plexward phones home to nobody. The only network calls are the ones you configured.
Run your portfolio like a flight crew.
Plexward is in early access: source-available under the Functional Source License (free to self-host, converts to Apache-2.0 after two years). We onboard a few design partners at a time, by hand.