Post-trade behavioral enforcement · Futures only

You don't losefrom bad trades.You lose when you stop
following your rules.

Guardian doesn't give you signals.

It shows you when you stop doing what you said you would do.

Most traders don't blow up in one trade. They lose control — slowly, trade by trade. Guardian is what makes that visible — and structural.

14 days · No card required

Integrates securely with

BinanceBybit

Guardian active

Guard — live session

−1.8R
of 3R limit
Daily boundary60% used
14:12
BTC/USDT LONG opened · RSI(14) = 68 ✓
14:31
Warning: 60% of daily limit used
🔒

Session Locked

Daily limit reached. Config is frozen.
To override, type the phrase below.

"I accept I am breaking my rules."

Guard demo — session lock activates at breach, phrase required to override

The real problem

You know your rules.
You break them anyway.

You set a 3R daily limit. You know revenge trading after three red trades compounds the damage. The problem isn't knowledge — it's that at 14:30, down 2R, with the market moving, knowing doesn't stop you. Discipline only works when it's structural, not optional.

You set the limit.
A daily loss boundary you wrote yourself — in R, before the session started. Not a suggestion. A rule.
You hit it anyway.
At some point in the session, knowing the limit stops being enough. The market is moving. One more trade.
Guardian holds it.
When the limit fires, enforcement runs — not a notification, not a reminder. A structural lock.

What you enforce

Three rules.
All post-trade. All structural.

DrawLine does not pre-block entries. You trade on your exchange. Guardian evaluates each position after it's opened and enforces the rules you wrote.

📉

You never stop at the right time.

Daily Loss Boundary

You set a daily limit. Guardian forces you to face it when you cross it — not later, not after one more trade. The moment your P&L hits the line, enforcement fires. Guard locks the session. Sentinel closes the position.

e.g. Daily limit: −3R. Hit −3.1R at 14:38 → immediate lock.
🔁

You trade worse after a losing streak.

Consecutive Loss Limit

After 3 losses, you're no longer trading your system — you're reacting. Consecutive losses are the most common precursor to revenge trading. Guardian acts before the pattern compounds.

e.g. Max 3 consecutive losses → lock after the 3rd red trade.
📊

You enter when you know you shouldn't.

RSI Compliance

You set the thresholds. After each position syncs, Guardian checks the RSI at the moment of entry. A violation isn't a warning — it's a breach. On Guard: session lock. On Sentinel: position closes immediately.

e.g. Long: RSI(14, 1D) must be ≥ 40. Enter at RSI 35 → breach.

How it works

Not a reminder. Not a checklist.
Actual enforcement.

⬟

Step 01

Set your rules — freely, before the session starts.

Define your daily loss limit in R or USD, consecutive loss threshold, and RSI compliance thresholds per timeframe. Config is yours to adjust any time before a session starts. No commitment until you're ready.

☁️

Step 02

You trade. Guardian sees what you don't.

Enter positions on your exchange as normal. The moment a trade syncs, Guardian evaluates it against the rules you set. Not later. Not at end-of-day. Right then — before you open another position.

🔒

Step 03

After this many losses, you are no longer objective.

You are reacting. Guard fires a session lock — full-screen cooldown overlay, config freezes, to continue you must type 'I accept I am breaking my rules.' Sentinel skips the phrase. Positions close. Session hard-locks. No bypass.

📊

Step 04

Your breach log builds your edge.

Every session lock and enforcement event logs to your audit trail — which rule, which pair, what RSI was at entry, what time of day. Patterns surface over weeks. Which rules you break most. When. Against which instruments.

Security & trust

Without your API key,
Guardian is blind.

It cannot see your trades.
It cannot see your mistakes.
It cannot protect you.

🔐

AES-256 encrypted keys

API keys are encrypted at rest using AES-256-GCM. They are never stored in plaintext, never logged, and never transmitted to any third party.

👁

Read-only by default

Guard mode uses read-only API access — it monitors positions but never places or cancels orders. Write access is only used by Sentinel to close positions at breach.

✂️

Minimal permissions

Guardian only requests what it needs. Position sync: read. Auto-close: reduce-only market order. No deposit, withdrawal, or transfer permissions ever requested.

🗑

Delete any time

Revoke your API key from your exchange at any time. All stored data can be exported or deleted from Settings. No lock-in, no retention after deletion.

Pricing

One bad session costs more
than a year of Sentinel.

Monthly
Annual Save 21–25%

Sentinel

No override. No exceptions.

At breach: positions close automatically server-side, even if the app is closed. RSI violation at entry triggers immediate auto-close. Set your lock period once — Guardian runs 24/7.

$79/mo
✓Everything in Guard
✓Auto-close positions at breach via exchange API
✓RSI compliance — auto-close on entry violation post-trade
✓Hard session lock — no override, no phrase
✓Full account lockdown server-side
✓Exchange API write access
✓Priority support
Recommended

Guard

Friction, not a wall.

Every breach triggers a session lock: config freezes, a full-screen overlay activates, and to continue you must type your acknowledgment out loud. For traders who respond to deliberate friction.

$19/mo
✓Session lock on breach — full-screen overlay, config freeze
✓Override phrase required to bypass lock
✓Daily R loss boundary
✓Consecutive loss limit
✓RSI compliance check — flags non-compliant entries post-trade
✓Full breach audit log
✓Push alerts approaching limit
✓Exchange sync (read-only)

You will probably break at least one of these rules.

That's the point.

14-day trial on all plans · No credit card required · Cancel anytime

FAQ

Questions traders actually ask