SignalKit operator guides

Set up your SignalKit deploy

Four sequential guides take a fresh SignalKit license from unpacked-on-disk to publicly reachable on your own domain. Read in order on a first install; cherry-pick later when you swap credentials or attach an additional domain.

1.Install SignalKit on Vercel + Supabase

30–60 minutes

Deploy the codebase to Vercel, link a Supabase project, apply database migrations, set BRAND_* environment variables, and verify /api/health.

2.Wire PayPal Subscriptions

45–90 minutes

Create a PayPal REST app, mirror your plans into the database, register the BILLING.SUBSCRIPTION.* webhook, run a sandbox subscription end-to-end before flipping LIVE.

3.Connect your Telegram bot + channels

30–45 minutes

Register a bot with @BotFather, create paid + free channels, set the webhook, configure tagged invite links, and test the chat_member kick flow on a test account.

4.Attach a custom domain

15–30 minutes + DNS propagation

Point DNS at Vercel, attach apex + www, flip NEXT_PUBLIC_APP_URL, update Supabase Auth redirect URLs, and re-register your PayPal LIVE webhook against the new domain.

Before you start

You should already have a SignalKit license file (issued at kickoff).
Have a registered domain ready, or be willing to use the Vercel-provided URL for the first deploy.
PayPal Business account in good standing (Personal accounts can't accept subscriptions).
A Telegram account on a phone you control (you'll create the bot through @BotFather).
Vercel + Supabase free accounts. We'll upgrade later only if traffic justifies it.

Stuck? Email support@signalcartel.trade with the step you're on and any error messages. Support subscribers get a response within the SLA in your contract; everyone else within two business days.