Frequently asked questions

SignalKit is a self-hostable trading-signals platform. It bundles a Next.js marketing site, subscriber dashboard, PayPal subscription billing, Telegram delivery (paid + delayed-free), an admin console, and license management. Operators bring their own trading logic and FSP license; the platform handles everything else.

Prop firms running internal signals informally to 20+ subscribers, signal sellers currently using Whop or Cornix who want their own branded site, and trading educators productizing a strategy into a recurring subscription. It is not for retail subscribers — those people are your customers, not ours.

Three tiers. Self-hosted: $5,000–$8,000 one-time setup plus $300/month support. Managed hosting: $1,500–$2,000/month all-in, no setup fee. Strategy-to-Server engineering builds: $3,000–$8,000 per strategy (50% upfront, 50% on delivery). All prices in USD. Final quotes depend on audience size and complexity.

Yes, if your jurisdiction requires one for publishing trading signals to paid subscribers — South Africa, the UK, the US, and Australia generally do. SignalKit exposes BRAND_FSP_NUMBER fields and disclaimer hooks throughout the codebase, but you are responsible for filing and maintaining your own license. We can’t and don’t do regulatory paperwork on your behalf.

Yes. Twelve BRAND_* environment variables drive your display name, tagline, hero copy, accent color, support emails, legal entity, registration number, and risk disclaimer. End users see your brand on every page; SignalKit branding does not appear publicly. The Telegram bot, PayPal merchant account, and custom domain are all yours.

No. SignalKit is infrastructure, not edge. You bring the trading logic — an MT5 EA, Python script, Pine indicator, or written rules. If you need a strategy implemented as a production bot, see the Strategy-to-Server build offer (engineering only — we don’t design profitable strategies on commission).

No. SignalKit publishes signals (entry, exit, risk parameters) to Telegram. Subscribers execute manually or through their own broker-side automation. Copy-trading or auto-execution introduces a much bigger regulatory surface and is deliberately out of scope.

PayPal is the live, supported billing provider. Stripe scaffolding exists in the codebase (src/lib/stripe/*) but is dormant. PayPal was chosen because it serves emerging markets, including African and South-Asian subscribers Stripe doesn’t support. We can switch a deploy to Stripe on request as part of a Strategy-to-Server engagement.

Telegram is the only supported delivery channel today. The gating logic (chat_member webhook, tagged invite links, auto-kick on cancel) is Telegram-specific. Discord and WhatsApp adapters can be built as Strategy-to-Server engagements but are not part of the standard platform.

WhatsApp Business API supports broadcast but doesn’t expose the equivalent of Telegram’s chat_member webhook for automatic kick on subscription cancel. Membership reconciliation has to be done manually or via an unofficial bridge. Not recommended as the primary channel.

Each strategy operates two Telegram channels. The paid (private) channel receives signals in real time; only active subscribers have invite links. The free (public) channel mirrors the same signals on a 30-minute delay (configurable). The delay creates the paid/free differential — free subscribers see the strategy works; paid subscribers act on it first.

Yes. The Next.js app needs Node 22+ and Postgres connectivity; the bots are standalone Node processes. PM2, Docker, or systemd all work. Vercel is recommended only because it minimises ops work (auto-SSL, zero-config deploys). For a real VPS install we update OPERATIONS.md with the Caddy reverse-proxy config and the cron-poller setup.

Managed: 3–5 business days from contract signature to public launch. Self-hosted: under one week typically, dependent on how quickly you can register PayPal Business, create Telegram channels, and point DNS. The bottleneck is usually external services, not the install.

Two to three hours per month of email support, security patches within 72 hours of upstream release, minor config or copy adjustments, and major-version platform upgrades. Strategy debugging, new feature builds, or operational on-call beyond email response are out of scope and charged separately.

Yes. Existing Whop subscribers can be re-onboarded via a one-off campaign to the new domain; the SignalKit codebase ships a /run-your-own-signals/start signup flow and we provide a migration script to backfill historical performance data. Cornix migrations are similar but require swapping subscribers from Cornix’s Telegram setup to your own bot — typically a one-week transition with overlap on both channels.

You do. The Supabase project lives in your account on self-hosted; on managed we operate it under a DPA on your behalf. Either way the data export is yours to take at any time as plain SQL or CSV. We don’t resell, share, or train models on subscriber data.

Thirty days’ notice cancels the managed engagement. On exit we hand over a full data export (subscribers, subscriptions, performance history), assist with pointing your custom domain at a host of your choice, and optionally convert the engagement to a self-hosted license (setup fee credited against months already paid).

No. Self-hosted is a one-time setup plus month-to-month support. Managed is month-to-month with 30 days’ notice. Annual prepayment gets a 10–15% discount on either tier; refunds for the unused portion are prorated.

SignalKit is operated by Mind Money Movement (Pty) Ltd, registration 2024/350331/07, a South African private company. For sales or partnership inquiries, email support@signalcartel.trade.