KingdomEdge · Customer Story

"It's working." — Cohort 0 pilot, Week 1

One of the first KingdomEdge subscribers — a Cohort 0 pilot member. This is what the first three weeks looked like once the bot was running cleanly. The numbers are real. Name withheld.

It's working — I'm seeing trades fire, the bracket orders are showing up in Alpaca, and I don't have to watch the chart. This is exactly what I wanted.
Cohort 0 pilot subscriber · Ultimate tier, after first week bot-active
93
Fills · Week 3
39
Closed trades
5
Watchlist tickers
0
Manual interventions

About this customer

A Cohort 0 pilot member. One of the small first group who agreed to run KingdomEdge during its pilot phase — before there was any external proof the platform worked.

They joined to help validate the platform, not for a personal outcome. Someone who believes in the vision and was willing to run the bot on their own account so KingdomEdge could learn from a real user before opening the doors wider. They followed the setup as documented, hit some bumps along the way, and by Week 3 the configuration was running cleanly on the standard Ultimate-tier stack.

The setup

Their setup is the standard Ultimate-tier configuration:

Their watchlist is intentionally focused:

TQQQ
Leveraged
XLK
Tech ETF
IWM
Small-cap
AMZN
Mega-cap
GOOGL
Mega-cap

Five tickers. The bot watches all of them. The customer watches none of them.

Week 1 — paper mode, first signals

Day one was setup. ~30 minutes total: TradingView indicators applied, Alpaca paper account linked through TradersPost, alerts wired to the SETS Trade indicator. Then they closed the laptop.

The first signal fired within the first few days. Not everything worked cleanly on the first pass — a couple of configuration bumps needed tuning before the pipeline was firing end-to-end reliably. Once dialed in, the Discord ping arrived, the bracket order appeared in the broker account, and the position was managed automatically.

"It's working — I'm seeing trades fire, the bracket orders are showing up in Alpaca, and I don't have to watch the chart."

Week 2 — discipline holds

Quieter week — markets churned sideways and the methodology fired fewer signals (the bot is conservative on purpose; most setups don't cross the HIGH threshold). Configuration continued to tune during this stretch as edge cases surfaced.

The pattern that emerged: the methodology stays the methodology. Second-guessing it defeats the point of automating it. Letting the bot pass on marginal setups is the whole design.

Week 3 — the data

June 20 through June 26. The first full week of consistent activity once their setup was completely tuned:

Note on numbers: this customer runs in paper mode on Alpaca by design. The methodology proves itself on real market data without real money at stake. Every Cohort 0 customer receives a full P&L summary every Saturday morning — the same format they'll see when they transition to live mode.

What surprised us

Two operational observations from the pilot:

1. The weekly summary email matters more than the dashboard. The dashboard provides real-time visibility, but the Saturday morning P&L email is what actually gets used week-to-week — to reflect on which signals worked and spot patterns. Real-time is for confidence. The weekly digest is for learning.

2. Knowing the bot is conservative is calming. Quiet days can create anxiety about whether something broke. The pilot-tested response: quiet days almost always mean "no setup met the threshold" — not "bot is down." Sentry monitoring + a proactive canary now confirms this within 15 minutes automatically if anything actually breaks (see below).

The one thing that broke (and how it got fixed)

Mid-pilot, an Alpaca API key was rotated on the broker side. The bot stopped firing — silently. For about 27 hours nothing about that failure was visible until a signal that should have fired didn't.

Within 60 minutes of detection, three things shipped: (a) self-serve credential rotation via a new dashboard panel, (b) a proactive monitoring canary that sweeps every active subscriber every 15 minutes, and (c) a structural fix that prevents future deploys from wiping fresh credentials. The 27-hour silent outage is now a 15-minute detection lag for any subscriber.

This is the whole point of running a pilot cohort. The pilot surfaces the failure mode. KingdomEdge ships the fix. Every subscriber who joins after benefits.

What this story shows

The point isn't the returns. It's the absence of effort.

93 fills in a week with zero manual interventions. No chart-watching. No second-guessing. A published methodology, executed by software that doesn't get tired or emotional. That's the actual product. The win rate is the bonus.

Important context: These results are one pilot subscriber's own. Past performance does not predict future results. Paper trading does not perfectly replicate live trading. The methodology has a published backtest baseline (61% win rate, 2.75 profit factor, +47R) but individual subscriber outcomes will vary based on tickers chosen, market conditions, and tier configuration. The point of this page is to show what the operational experience looks like — not to project P&L for any other customer.
KingdomEdge Algo

Want your own version of this story?

Same indicators. Same methodology. Same dashboard. Your own watchlist, your own broker, your own pace.

Start here → Watch the bot work