Deploy sentinel-selfbot
Railway

Deploy sentinel-selfbot

The core for the Sentinel ecosystem, a Discord intelligence platform.

Deploy sentinel-selfbot

Just deployed

Sentinel Selfbot – Railway Template Overview

Deploy the Sentinel selfbot on Railway in one click. This template runs the selfbot as a cloud‑based data collection engine for the Sentinel ecosystem, storing all data in a cloud Supabase database for persistent, always‑available analytics.


# Deploy and Host

One‑click deployDeploy on Railway
Hosting platformRailway (https://railway.app)
RegionsChoose any Railway region (US, EU, Asia‑Pacific)
Resource requirements~256 MB RAM, 0.1 vCPU – fits within Railway’s free $5/month credit
Persistent storageNot used (data lives in Supabase)

After deployment, Railway automatically builds and starts the selfbot. No server maintenance required.


## About Hosting

Railway is a modern application hosting platform that handles infrastructure, auto‑restarts, SSL certificates, and scaling. When you deploy this template:

  • Ephemeral filesystem – The selfbot container has no permanent disk. That’s why we require Supabase for database storage.
  • Auto‑restart – If the selfbot crashes, Railway restarts it immediately.
  • Public URL – Railway assigns a *.up.railway.app HTTPS domain, or you can add a custom domain.
  • Logs – Real‑time logs are available in the Railway dashboard.
  • Environment variables – All secrets are encrypted and can be updated without redeploy.

This template is optimised for Railway’s free tier – the selfbot runs 24/7 without extra cost.


## Why Deploy

Deploying the Sentinel selfbot on Railway gives you:

BenefitDescription
Always onlineNo need to keep your local computer running 24/7
Zero maintenanceRailway auto‑restarts on failure, applies OS updates, and manages SSL
Global accessConnect your Sentinel web panel from anywhere – home, office, mobile
Free tier eligibleRuns entirely within Railway’s $5/month free credit
ScalableAs you add more targets, Railway can upgrade resources automatically
SecureAll traffic is HTTPS by default; secrets are environment variables
No VPS managementNo SSH, no firewall rules, no systemd or PM2 setup

Compared to a local or VPS deployment, Railway removes operational overhead so you can focus on using Sentinel.


## Common Use Cases

This selfbot is designed for monitoring and analytics. Typical use cases include:

Use CaseDescription
Personal researchStudy online behaviour patterns, activity cycles, or community engagement
Server moderation assistanceDetect unusual activity from problem users (requires proper consent/notice)
Activity logging for friendsWith explicit permission, track when friends are online, playing games, or listening to music
Security auditingMonitor for compromised accounts by detecting anomalous login times or devices
Academic / social scienceCollect de‑identified activity data for research on digital behaviour
Self‑hosted alternative to commercial trackingReplace third‑party bots with your own data‑sovereign solution

Important: Only track people you have a legitimate reason to monitor and where it complies with Discord’s Terms of Service and applicable privacy laws.


## Dependencies for

The selfbot requires three external dependencies to function on Railway:

DependencyPurposeRequired?
Discord account + tokenThe selfbot logs in as a user account to observe data✅ Always
Supabase projectCloud database for persistent storage (Railway’s disk is ephemeral)✅ Always
Railway platformHosting environment (provided automatically when you deploy)✅ Always

These are runtime dependencies – you must provide the Discord token and Supabase credentials before the selfbot can start.


### Deployment Dependencies

The following configuration values must be set as environment variables in Railway before the selfbot will run successfully. No additional software installation is needed.

VariableDescriptionHow to obtain
DISCORD_TOKENDiscord user token for a dedicated alt accountExtract via browser DevTools (Network tab → Authorization header). Never use your main account.
API_AUTH_TOKENBearer token for API authenticationGenerate a strong random string (e.g., openssl rand -hex 32). Keep it secret.
SUPABASE_URLURL of your Supabase projectIn Supabase dashboard → Settings → APIProject URL
SUPABASE_SERVICE_KEYSupabase service_role key (not the anon key)Same API settings page → service_role key (starts with eyJ...)
API_PORT (optional)Port the API listens onDefault 48923 – Railway automatically detects and exposes it

Steps to set dependencies during Railway deploy:

  1. Create a free Supabase project at supabase.com.
  2. Copy the Project URL and service_role key.
  3. Click Deploy on Railway button above.
  4. In the Railway variable form, paste:
    • DISCORD_TOKEN (your alt account token)
    • API_AUTH_TOKEN (your own generated token)
    • SUPABASE_URL
    • SUPABASE_SERVICE_KEY
  5. Click Deploy – Railway builds and starts the selfbot automatically.

After deployment, the selfbot connects to Discord, creates the required tables in Supabase, and starts the API. You can verify it works by visiting https://your-railway-url.railway.app/api/status with the Authorization: Bearer YOUR_API_AUTH_TOKEN header.


Full Environment Variable Reference

VariableRequiredDefaultDescription
DISCORD_TOKENDiscord user account token
API_AUTH_TOKENBearer token for API authentication
SUPABASE_URLSupabase project URL (e.g., https://xxxx.supabase.co)
SUPABASE_SERVICE_KEYSupabase service_role key
API_PORT48923Port the API listens on (Railway auto‑maps)
DB_MODEcloudFixed to cloud for Railway – do not change
LOG_LEVELinfoSet to debug for troubleshooting
RANDOM_JITTERfalseRandomise polling intervals (increases stealth)

After Deployment – Connect the Sentinel Web Panel

  1. Get your Railway public URL – In Railway dashboard → your service → SettingsNetworkingGenerate Domain. Copy the HTTPS URL.
  2. Open your Sentinel web panel (e.g., https://sentinel-panel.vercel.app/settings).
  3. Fill in:
    • Sentinel API URL → your Railway URL
    • API Token → the API_AUTH_TOKEN you set
  4. Save – the panel will connect and show the selfbot status.
  5. Add your first target from the Dashboard.

Support & Links


License: PolyForm Noncommercial License 1.0.0


Template Content

More templates in this category

View Template
N8N Main + Worker
Deploy and Host N8N with Inactive worker.

jakemerson
View Template
Postgres Backup
Cron-based PostgreSQL backup to bucket storage

Railway Templates
View Template
Prefect [Updated Apr ’26]
Prefect [Apr ’26] (ETL & Automation alternative to Airflow) Self Host

shinyduo