SignalKit explained
How SignalKit works
A self-hostable platform that turns your trading logic into a branded subscription business. You bring signals and an FSP license; the codebase handles delivery, billing, gating, and reporting.
The 60-second version
A SignalKit deploy is a Next.js app on Vercel (or your own host) backed by Supabase Postgres, plus one or more bot processes you run alongside it. The web app handles marketing pages, sign-up, PayPal subscriptions, the subscriber dashboard, and the operator admin console. The bots produce signals, post them to your Telegram channels (paid + delayed-free), and stream performance back to the web app every five minutes. Your brand, your billing, your bots — our codebase and ongoing updates.
The six moving parts
1. Signal source (yours)
You bring the trading logic — an MT5 EA, a Python script, a Pine indicator, or a manual rules-based system. SignalKit runs the bot process, captures each closed trade, and exposes per-strategy performance via an internal API. The platform stays agnostic about whether your edge is breakout, mean-reversion, ICT, or discretionary entries logged through a webhook.
2. Telegram delivery
Paid signals push in real time to your private Telegram channels. Free signals mirror to public channels on a configurable delay (30 minutes by default). The Telegram bot gates access — subscribers receive a one-time invite link tagged to their account, and a webhook handler kicks expired or cancelled subscribers automatically on chat_member events.
3. Subscription gating + billing
PayPal Subscriptions handle recurring revenue. Plans, prices, and entitlements live in your database; the BILLING.SUBSCRIPTION.* webhooks flip the gate. Annual prepay applies a configurable discount. The codebase ships scaffolding for Stripe too, but PayPal is the live path because it serves emerging markets better.
4. Public marketing surfaces
Out of the box: a homepage with strategy cards and aggregated performance, per-strategy pages with equity curves and trade logs, a pricing page, a free-signals page listing your public Telegram channels, an upcoming-strategies waitlist, and the legal triplet (terms, privacy, refunds). Every surface is brandable via environment variables.
5. Operator console
Admin pages (IP-gated by default) for managing tenants, attaching custom domains via the Vercel Domains API, rotating per-tenant PayPal and Telegram credentials, and issuing or revoking SignalKit licenses. A signed-bundle revocation endpoint lets you disable a self-hosted instance without a network call from the buyer side.
6. Performance dashboard
Pro subscribers get a logged-in dashboard with equity curves, summary stats (total R, win rate, R:drawdown), and a live-positions widget that polls each strategy bot every 30 seconds. Performance writes flow from the bot to a JSONL file to a 5-minute cron that hydrates a Supabase performance_cache row read by the public pages.
What runs where
- Web app: Vercel (recommended) or any Node 22+ host. Next.js 16, React 19, TypeScript.
- Database: Supabase Postgres (free tier covers most launches). Auth, storage, and PostgREST included.
- Bots: your VPS, your home server, or a beefier Vercel/Render service depending on broker requirements. Each bot is a standalone Node process with a local JSONL performance store.
- Telegram: one bot token per tenant; channels you own.
- PayPal: your merchant account, your plans, your payouts. We never touch end-user money.
What you still own
SignalKit is infrastructure. The pieces below are deliberately outside the box because they vary per operator and per jurisdiction:
- Your edge.We don't generate strategies. If you need one built, see Strategy-to-Server builds.
- Licensing. FSP / FCA / SEC / ASIC paperwork is your responsibility. The codebase exposes FSP-number fields, disclaimer hooks, and per-jurisdiction geo-blocking but does not file paperwork for you.
- Distribution. You bring the audience. Signup forms, free channels, and pricing pages are shipped — paid acquisition is yours.
- Trade execution. SignalKit publishes signals; it doesn't auto-trade for subscribers. End users execute manually or through their own broker-side automation.