About Tickory
What the product does, how it works, and how to verify it before you use it.
Tickory exists for traders and operators who already know the setup they want to monitor and need the alert path to stay observable. The product keeps its scope narrow: scheduled scans, routed alerts, and proof of what happened.
Verification checklist
- 1Review the public About, FAQ, security, privacy, and terms pages.
- 2Create a test scan or TradingView source before sending any live alerts.
- 3Check the proof path: what fired, what stayed quiet, and which channels delivered.
- 4Only then decide whether Tickory fits your monitoring workflow.
What Tickory is
Tickory is a market monitoring and alerting product. You write or choose a rule, Tickory scans supported symbols on a schedule, and then it routes conditions-met alerts.
What Tickory is not
Tickory is not a trading bot, execution engine, custody product, or exchange-account connector. It does not place trades on your behalf.
How cautious users verify it
Read the FAQ, security notes, privacy policy, and terms. Then create a test scan or alert source and inspect the proof trail before routing live alerts.
How alerts work
The proof path stays close to the event
Tickory keeps the monitoring path inspectable so the result does not feel like a black box.
1. A rule runs on schedule
You define the setup once. Tickory scans supported symbols on the interval you choose.
2. The outcome stays explainable
When a symbol matches, you can inspect why it fired. When it stays quiet, the missed threshold stays visible so silence still reads like information.
3. Delivery proof stays attached
Tickory records channel outcomes so you can see what delivered, what retried, and where recovery happened.
Public trust surfaces
Read the first-party pages before you commit
Questions before you route live alerts?
Support and security questions should be answered before the product is trusted with live monitoring.