It calls your phone when your money is unprotected.

Wachly watches your trading account read-only, 24×7 — and rings your phone the moment something is wrong. No orders. No advice. Just the alarm you wish you'd had.

Get early access at ₹499/mo Free 14-day trial at launch · founding-member price locked for life

The dread

Three things that happen silently — while everything looks fine

While you sleep

Your stop-loss order got REJECTED at 3:25 pm.

Margin block, price band, whatever — rejections happen every day. Nobody reads every order confirmation. You find out tomorrow morning, after the gap.

While your bot runs

Your algo showed “connected” — its data feed had been dead for 33 minutes.

The process is green. The websocket is a zombie. It's trading yesterday's world with today's money.

While you forget

Your short option expires tomorrow. You forgot it exists.

Expiry-day surprises, margin creep, a position your bot thinks is closed but the broker says is open. Silent, until it's expensive.

A true story

Why Wachly exists

On 25 August, my live NIFTY engine silently stopped receiving market data for 33 minutes — while showing “connected.” It filled a stale signal half an hour late and blocked the trade that would have paid for the day.

I've been a software engineer for 18 years. I run production trading systems. It still happened to me — because the watchdog I needed didn't exist: one that lives outside my own server, so it can't die with it.

So I built it. Wachly is that watchman — for your account too.

— Srikanth, founder

How it works

Three steps. Ten minutes. Then it never blinks.

Connect your broker — read-only

A read-only API key that cannot place orders. We verify it at connect time. The order-placement code path doesn't exist in Wachly — not disabled, absent.

Choose your tripwires

Trade with stop-losses? We alarm when one is missing or rejected. Run stop-less overnight strategies? Set a loss line instead. Multiple strategies? Rules attach per position. Your strategy stays yours — we never see the logic.

Get the call

Danger state → your phone rings within seconds, and keeps ringing until you acknowledge. Still no answer? It calls the person you chose. Like a smoke detector, it's loud on purpose.

We never place orders. We never give advice. We only watch — and we scream.

Brokers

Works with the account you already have

Dhan · free API Fyers · free API Angel One · free API Upstox · free API Zerodha · supported* Alpaca · US IBKR · global Tradier · US

*Zerodha charges ₹500/month for its Kite Connect API — that fee goes to Zerodha, not us. Partnership in progress to remove it.

Early access

Founding-member pricing — locked for life

Founding member

₹499/month

or $12/month outside India

All alarms: no-stop-loss, rejected orders, loss lines, margin, expiry
Algo watchdog: bot heartbeat, feed staleness, position drift
Real phone calls that ring until you answer
Escalation to a second contact
Read-only. Always. By construction.

14-day free trial at launch · cancel anytime · price never increases for founding members

You're on the list ✓

Check your inbox for a confirmation. One favour: reply to that email and tell me what almost burned you once — it directly shapes what gets built first.

Questions

Fair questions, honest answers

Can Wachly touch my money or place orders?

No — structurally. We connect with read-only API access and verify it at connect time. Wachly's codebase contains no order-placement path at all. We can see positions and orders (which your broker already sees); we cannot act on them.

My strategy doesn't use stop-losses. Will it false-alarm all day?

No. You choose your tripwires. Switch off the stop-loss check for that strategy and set what actually matters to you instead — “call me if this position's loss crosses ₹25,000” or “if margin use crosses 90%.” Even a no-stop strategy has a line in your head; Wachly makes that line loud.

I run multiple strategies in one account — with different rules.

Rules attach per position, three ways: order tags (if your algo tags orders, rules map automatically), scope rules (“short options → no-SL expected”), or a one-tap question when an unknown position appears. Five seconds, and that position carries its rules until it closes.

How is this different from kill-switch tools like TradeGuard?

Kill switches protect you from yourself — they square off your positions when you breach your own daily-loss limit. Wachly protects you from what breaks: the rejected stop-loss, the frozen bot, the stale feed, the forgotten expiry — and we never touch your positions. Different dangers. Many traders will want both.

I'm an engineer — can't I build this myself?

Yes — and your watchdog will die with your server, silently, which is the exact failure it's supposed to catch. A real guard must live on separate infrastructure with its own broker connection and its own watchdog watching it. That second system is what you're paying ₹499 for — same reason 650+ developers pay Healthchecks.io to watch their cron jobs.

Do you see my strategy?

No. We see positions and working orders — the same data your broker shows. Your entry logic, signals, and reasons stay in your head. The only “strategy” data we hold is the tripwire settings you chose.

Is this investment advice?

No. Wachly never recommends buying or selling anything. Alerts describe the state of your account against rules you set — like a smoke detector describes smoke. We are a technology tool, not a SEBI-registered adviser, and we don't need to be one because we give no advice.