Appearance
Go-live checklist
Work through this list before you announce your exchange. Every item is something that's easy to forget during setup and hard to fix once real users and real money are on the platform.
Security
Server and configuration
-
APP_DEBUG=falseandAPP_ENV=productionin.env -
READ_ONLY_MODE=false. Read-only is a demo mode: it blocks every change, skips deposit detection, and lets any signed-in user give themselves the staff roles (everything except superadmin) at/demo-mode. -
SESSION_DRIVER=redis,CACHE_DRIVER=redis,QUEUE_CONNECTION=redis,BROADCAST_DRIVER=pusher. The.env.examplevalues (array,sync,log) don't work on a live site. - HTTPS works on
yourdomain.comandsocket.yourdomain.com, andAPP_URLstarts withhttps:// - Firewall allows only SSH, 80 and 443 (see Ports & processes)
- SSH uses keys, not passwords. Root login is disabled.
- The
.envfile is readable only by the web server user:chmod 640 .env - The Horizon dashboard (
/horizoncctech) is only open to the first account. Make sure that account is yours.
Secrets you must replace
- WebSocket credentials: your own random
id,keyandsecretinsocket-config.jsonand thePUSHER_*values. The repository ships with sample values. - Database password: long and random
-
APP_KEY: generated on this server withphp artisan key:generate, and backed up - Hot-wallet keys: wallets created only for this exchange, never reused from tests (Hot wallets)
Accounts
- You registered the first account yourself (it became superadmin)
- Two-factor authentication is on for every staff account
- Every staff member has only the roles they need (Roles)
- Test accounts and test balances are removed
Money
- Hot wallets funded with working balances, plus fee coins (ETH, BNB, TRX, POL, SOL, TON) for every network you offer
- Cold storage rules set, so excess funds leave the hot wallets (Cold storage)
- Explorer API keys set:
APP_ETHERSCAN_KEY,APP_BSCSCAN_KEY,APP_POLYGONSCAN_KEY(Bridges) - Paid node endpoints for each network, and
APP_ETHEREUM_NODEis set if you offer Ethereum - For every network: one real test deposit and one real test withdrawal, with a small amount
- Withdrawal approval routine agreed: who approves, how often (Approvals)
- Withdrawal limits set (General settings)
- XRP or TON offered? Their deposit monitors are added to the scheduler (Bridges → XRP and TON)
Business setup
- Name, logo and colours (General settings)
- Favicon: put your icon at
public/favicon.png(PNG, at least 42×42). The file isn't part of the code repository, so add it on every server; there is no admin setting for it - Trading fees set (Trading fees), and the Fees page lists the same numbers
- Currencies and networks reviewed: deposit and withdrawal minimums, fees and confirmations (Currencies)
- Markets reviewed: precision, minimum order sizes, liquidity bots (Markets)
- Default trade and futures pairs point to markets that exist
- Legal and info pages rewritten for your company. The starter pages are: Privacy Policy, Terms of Service, Risk Disclosure Statement, Support Center, KYC Verification, Referrals, Fees, Trading Rules, Contacts and About (Pages). Have the legal ones checked by a lawyer.
- KYC decided: built-in review or Sumsub, and what requires verification (KYC)
- Email delivers: test from System Monitor, and send yourself a password reset (Email)
- Admin notification email set, so you get new appeals and System Monitor alerts (Notifications)
- Captcha (Cloudflare Turnstile) on for sign-up, sign-in and password reset (Captcha)
- Sign-in buttons work: Google is always shown, so set it up (or remove it); Apple and Telegram only if you want them (Sign-in & SMS setup)
- Passkeys:
PASSKEYS_RP_IDis your final domain (changing it later breaks every passkey), a passkey sign-in tested; for the app,/.well-known/assetlinks.jsonand/.well-known/apple-app-site-associationopen (Passkey sign-in) - SMS sends: Twilio upgraded from trial, your countries allowed, a phone sign-up tested (SMS with Twilio)
- Social links point to your accounts (Social)
- Languages: only the ones you support are active, and their texts are checked (Languages)
Remove demo content
db:seed creates demo staking products and launchpad sales so those pages aren't empty. Before going live:
- Delete or rewrite every product in Admin → Staking
- Delete or rewrite every sale in Admin → Launchpads
- Check Articles for sample announcements
Operations
- Scheduler cron entry for
www-data(Scheduler) - All processes online in
pm2w status, andpm2w save+pm2 startupdone, so they come back after a reboot. Reboot once to prove it. - Automatic, encrypted, off-server backups running, and one restore tested (Backups)
- System Monitor alerts on (System Monitor)
- PM2 log rotation installed:
pm2w install pm2-logrotate - Uptime monitoring from outside (any uptime service) on
https://yourdomain.comandhttps://socket.yourdomain.com - Disk space alert at 80%
- Someone on call for the first week, who knows this documentation
Final check
Open the site in a private browser window, as a new user:
- Register, verify your email, enable 2FA
- Deposit a small amount
- Place and cancel a limit order, then place a market order
- Withdraw a small amount, and approve it as admin
- Check the trade page shows Stable connection and a moving chart
If all five work, you're ready to open.
