Skip to content

Your alerts.Your rules.

From price crossings to indicator combinations, customize trigger conditions, check frequency, and notification channels to fit your strategy.

  • No sign-up
  • Rules stay local
  • Runs in your browser
Alert workspace
BTC / USDTBINANCE · SPOT
1m
96,842.50+2.34%
96,80006:0012:0018:0000:00
THE MARKETS YOU KNOW
SpotPerpetuals1m — 1w charts
  • BINANCE
  • OKX
  • BYBIT
  • HYPERLIQUID
  • KRAKEN
  • BITGET
  • COINBASE

FROM AN IDEA TO AN ALERT

Your next alert, in three steps.

Choose a market. Set your condition. Wait for your moment.

  1. 01

    Pick your market

    Find your pair across Binance, OKX, Bybit, Hyperliquid, Kraken, Bitget, and Coinbase spot and perpetual markets.

    BINANCE / OKX / BYBIT / HYPERLIQUID / KRAKEN / BITGET / COINBASE
  2. 02

    Define your condition

    Combine prices and indicators, paste ARL text, or start with a ready-made template.

    PRICE / INDICATORS
  3. 03

    Choose how to hear

    Use in-page notices, enable browser notifications, or connect an external channel.

    ALERT / NOTIFY

BEYOND A PRICE THRESHOLD

Simple conditions. Your own strategy.

Combine indicators. Confirm at close.

Combine price levels and crossings with EMA, SMA, RSI, MACD, or Bollinger Bands across timeframes, then confirm conditions at candle close.

Close rules · 1m through 1h

Live prices. Your check frequency.

Receive live prices via WebSocket and check on each update, every second, or every 5 seconds. Alerts fire when a condition changes from false to true.

On update / Every 1s / Every 5s

Control when alerts fire.

Set one-time triggers, cooldowns, rearming, count limits, and expiry to fit your strategy. Receive notices in-page, in your browser, or through external channels.

In-page / Browser / Telegram / Discord / Webhook

Your rules and keys stay local.

No account needed. Rules, runtime state, trigger history, and channel keys stay in your current browser and are not uploaded to a server.

Local storage · No sign-up

HOW IT RUNS

An open tab. Your monitoring station.

Conditions are evaluated in your browser. Closing the page, browser sleep, or a network drop stops monitoring. Reopening catches up close rules and shows a summary. External notifications are not replayed.

Comparison of alert operation
FeatureTradingViewCandle Ping
Where it runsCloud alertsYour browser
After closingAlerts continueMonitoring stops
Rules and keysPlatform-managedStored locally

A FEW MORE DETAILS

Before you get started.

Open workspace
Do alerts keep running after I close the page?

No. Close alerts and realtime alerts are evaluated in the current tab, so monitoring stops when the page is closed, the browser sleeps, or the network drops. When you reopen the page, close rules catch up and show a summary, but Telegram, Discord, and Webhook deliveries are not replayed. Server-side monitoring is planned.

Where is my data stored?

Rules, trigger history, channel settings, and keys are stored in the current browser's IndexedDB. There are no accounts, and rules and keys are not uploaded to a server.

Which markets and periods are supported?

Market data covers spot and perpetual markets on Binance, OKX, Bybit, Hyperliquid, Kraken, Bitget, and Coinbase. Quote currencies include USD, USDT, and USDC, depending on the market. Charts support 1m through 1w. Alerts currently support 1m, 3m, 5m, 15m, 30m, and 1h close rules, plus realtime price alerts evaluated on each market update, every second, every 5 seconds, or at a custom interval.

Which notification channels are available?

In-page notices are on by default; browser notifications require permission. Telegram, Discord, and custom webhooks are called directly by the browser and require the target to allow cross-origin requests. Keys stay on this device.

Are channel keys secure?

Keys are written only to local IndexedDB and the interface shows the last characters. Static encryption with a passphrase is not available yet. Anyone who can use this browser profile can read the storage, so use a separate profile on a shared computer.

How do live market data and alert frequency differ?

Market data arrives via WebSocket. Price alerts can check each received update, every second, every 5 seconds, or at a custom interval, and alert when a condition turns true. Timed checks can miss brief crossings. The first update after activation or reconnection establishes a baseline without alerting. Evaluation stops after 60 seconds without fresh data. Checking each update does not guarantee that every trade is pushed or received.

How data is handled

Rules, history, channel settings, and keys stay locally and are not uploaded.