Connecting
A LITTLE ORDER FOR YOUR AUTOMATIONS

Your control room.

Keep your scripts running. Stay in the loop.

TOTAL SERVICES ▦
0
In this workspace
RUNNING ◉
0
Active processes
NEEDS ATTENTION △
0
Everything looks quiet
MANAGER UPTIME ◷
—
Waiting for connection

Services 0

Small programs, under control.

↻ Status refreshes every 2 seconds No containers. Just your commands.
YOUR LOCAL CONTROL ROOM

Sign in to your deck.

Use your username and password to manage services.

MAKE ROOM FOR A PROGRAM

Add a service.

Use the same executable and arguments you use in your terminal.

Folder ownership and version

Shared folders cannot be moved or deleted automatically. Existing services start marked shared until you review them. Save ownership changes before moving or deleting files.

Choose a type, then the process or web address to wait for.

SERVICE INSPECTOR

Live output

Waiting for output…
FOR JARVIS, CODEX & YOUR TOOLS

A small API. A lot of control.

Every control request uses your bearer token.

BASE URL
GET/api/servicesStatus of all services
POST/api/services/{id}/startStart a service
POST/api/services/{id}/stopStop its process tree
POST/api/services/{id}/restartStop, then start
GET/api/services/{id}/logsRecent output

PowerShell example

Full API documentation and Python client: README.md and deck_client.py in the app folder.

WORKSPACE SETTINGS

Your deck. Your account.

API key

Use your key for Jarvis, Codex, and other script calls. Anyone with this key can control this deck.

This computer

Nodes keep their own services, login, API key, and install folder. Switching roles does not stop any services. Saved node connections are inactive while in node mode.

Deployment locations

Each upload gets a folder and a separate Python environment.

Change browser login

Changing your login signs out other browsers. Your API key stays valid.

FROM SCRIPT TO SERVICE

Install a program.

Upload, review dependencies, then give your program its own environment.

Recent installations

No installations yet.
YOUR COMPUTERS, TOGETHER

Managed nodes.

Pair another full Process Deck instance. Set its role to Node in its Settings, then use its reachable address and API key.

Download Process Deck for another computer

Includes the node setup guide and Install-ProcessDeckStartup.ps1. Setup creates a dedicated environment, downloads Python if needed, starts before login under your account, and allows connections on Private and Domain networks. Run it in Administrator PowerShell and enter your Windows password locally. No accounts, API keys, services, or machine data are included.

Add a node

The node restarts Process Deck to install it, after running installations finish, and starts its running services again.