Your PMO field guide.

From download to your first session.

1. Create your own account and complete email verification, or use the configured Google sign-in.
2. Open your workspace and inspect which tools are enabled for your account.
3. Install the customer desktop for local broker setup, Orbital controls and the Alpaca paper/live workers. Browser simulation remains available separately.
4. Pair your desktop below. In the workspace, save your startup and route preferences.
5. Refresh the profile and check whether a recently connected device acknowledged the current revision.
6. Use an entitled simulation tool and review its journal. A saved profile or paper result does not enable live orders.

Install for your Windows account.

Supported target: 64-bit Windows 10 or 11 with .NET Framework 4.8 and HTTPS access to pmo-bot.com and your selected provider. Python is included. No administrator elevation or broker desktop restart is required. The exact release is checked on a clean Windows CI virtual machine, with test-program outbound network blocked.

The customer desktop download is free. Read the purchase policy.

Download / update PMO Desktop Installation guide

Reading release metadata...

Desktop 1.3.0 includes your local Orbital Command Deck, top trading switches and limits, paper execution, account-specific Alpaca live activation, and verified update downloads. Your explicit activation request waits for a qualified strategy and validates the broker lifecycle before automatic trading starts. Your account credentials and journals stay on your computer.

Loading SHA-256...

1. Download PMOBotSetup.exe from the button above.
2. Compare its SHA-256 with the release metadata. PowerShell: Get-FileHash "$HOME\Downloads\PMOBotSetup.exe" -Algorithm SHA256.
3. Review the unsigned-build notice. If your organization requires signed software, wait for a signed release. Do not disable security protections.
4. Run the installer and choose whether to start the companion at Windows sign-in.
5. Press Install PMO Bot. The current-user install creates PMO Bot shortcuts on the Desktop and Start menu.

Files are stored under %LOCALAPPDATA%\PMOBot\Desktop. No existing PMO source folder or broker installation is overwritten. Closing the companion window hides it to the tray. Use its tray menu to exit.

Pair and manage your desktop.

On your own PMO Desktop, press Pair this desktop. Enter its eight-character code here. Never approve a code sent by another person.

Sign in to your verified PMO account to pair or manage devices.

Choose the correct account route.

Saving a route selects a setup preference. It does not connect an account, verify entitlements, install its adapter, or submit an order. A software subscription does not grant broker authority. Alpaca live activation requires your own account, approved limits and explicit authorization in your local Orbital panel.

1. Choose only providers you use in Workspace → Startup & broker preferences.
2. Read the displayed mode and provider requirements before saving.
3. Use provider-owned applications for their own account approval, data entitlements and API permissions. Do not enter broker credentials into support tickets or the desktop pairing form.
4. In PMO Desktop choose My local broker accounts. Enter your own account and API credentials there. Credentials are encrypted for your Windows user. For ProjectX enter an existing provider session token. PMO does not sign into or renew that session.

Current customer web simulation supports BTCUSD, ETHUSD, SOLUSD and XRPUSD using Kraken public spot quotes. It supports simulated buys and closing a held simulated position. It does not submit market, limit, stop, bracket or short orders to a broker.

Start the guarded customer paper worker.

1. Pair this desktop to your own verified PMO account and choose Alpaca in Workspace startup preferences.
2. Enter the exact Alpaca paper account number, paper API key and secret under My local broker accounts.
3. With a current paper-terminal entitlement, choose Start guarded PAPER entries. Account, quote, fee, signal, inventory and risk gates still apply. No setup means no order.
4. PMO uses the existing closed-candle crypto scanner. Only qualified long USD spot setups advance. No signal means no entry.
5. Use Stop new entries / keep protection to pause entries while existing managed exits continue.
6. Automatic sign-in startup and resuming previous paper entry permission are separate opt-in preferences. Every new account requires its own setup. No owner login is shared.

The local worker enforces the stricter dollar and percentage limits. Its conservative per-trade cap reserves the entire spot notional plus costs within the saved equity-risk fraction. A drawdown breach persists for 24 hours across restarts. Stale cloud profiles block entries while protective management continues. Authentication refusal pauses requests until explicit local remediation.

Your Alpaca controls, together at the top.

1. Install or update PMO Desktop, pair your own verified account, and sync your profile. Live setup requires an active software plan with risk controls.
2. Under My local broker accounts choose ALPACA_LIVE and save your exact live account number, API key and secret. Paper credentials are separate.
3. Choose Open my Orbital Command Deck. At the top, review every switch and risk limit, then save. Limits must fit within your paired account profile.
4. Choose Request Alpaca live ON. Confirm the displayed account number and the authorization for one bounded real-money validation followed by automatic trading.
5. Leave the runtime running. PMO waits for a fresh qualified strategy. It verifies entry, broker stop, recovery, duplicate rejection and exit. When those checks pass, trading starts automatically. You do not need to return from TradingView to press Validate.
6. Alpaca OFF cancels pending activation and stops new live entries. Existing protection continues. A settings or software change invalidates the old activation binding and displays the next required action.

The local panel also shows strategy observations, your journal, connection status and exact blockers. It listens only on this computer and requires a temporary panel token. NinjaTrader is not part of this Alpaca activation path. Broker authentication refusal requires one explicit retry using the top panel after you correct the credentials.

Run a first customer simulation.

1. Open Workspace → Paper terminal with an existing active software entitlement.
2. Read the simulated starting balance and quote source. It is not a funded broker balance.
3. Choose a supported symbol and a $1–$50 amount within your saved limit.
4. Submit a simulated buy. PMO checks the quote, spread, cash, position count and current realized-loss limit.
5. Use the close action for the held simulated position. Review its recorded fees and net result.
6. Review the report. The simulation assumes a 0.4% fee per side. This is not a statement of your actual broker fee.

Live public ticker data does not make a simulated fill a real broker order. The public proof feed uses a separate journal from your customer simulation.

Risk controls and stopping have separate jobs.

Pro, Elite and Enterprise customers with active access edit the bounded risk profile in their workspace. A saved cloud preference and a desktop acknowledgement do not prove a broker worker enforces that value.

• The desktop Stop new entries / keep protection control blocks new paper and live entries. The Orbital Alpaca OFF control blocks live entries. Managed exits continue.
• Exit display turns off new paper and live entries and stops profile checks. The protection worker stays running for existing managed trades.
• Revoking a desktop removes its profile access. It does not cancel broker orders.
• Stopping new entries, preserving protective exits, cancelling an order and closing a position are distinct controls.
• Owner LIVE controls belong to the protected operator deployment. They are not included in this customer companion.
• For an execution incident, inspect the actual broker orders and positions, use the relevant approved stop control, and contact the broker for broker-side intervention.

Customer simulation daily-loss enforcement counts gross realized losing trades and fees in the UTC day. It excludes open mark-to-market losses. Percentage preferences are not enforced by this simulator. Do not treat them as a full portfolio circuit breaker.

Update, recover and remove the companion.