← Back to Risk Radar

Risk Radar Setup Guide

Estimated time: 20-30 minutes

Before You Start — Request Beta Access (Concierge)

Risk Radar’s beta is concierge — I set you up personally. Before you install, email office@bionex.ro and request: (1) your install bundle, (2) your backend access token (CF_ACCESS_CLIENT_ID / CF_ACCESS_CLIENT_SECRET), and (3) dashboard access for your email. You can finish Telegram + IBKR setup and get Telegram alerts without the token — but your account won’t appear on the dashboard until it’s issued and your email is allowlisted. Request these first so you’re not blocked later.

Risk Radar runs as a local agent on your machine, next to your IB Gateway or TWS. Your IBKR credentials never leave your machine. The dashboard and alert history are hosted at risk-radars.com.

1 Create a Dedicated IBKR Monitor User

How to create the monitor user

1. Log in to IBKR Account Management
2. Go to Settings → Users & Access Rights
3. Create a new user (e.g., “RiskRadar Monitor”)
4. Assign minimum permissions: read-only, trading disabled, access to account values/portfolio/positions
5. Wait for IBKR approval (1-2 business days)

Once approved, launch IB Gateway and log in as your monitor user. Keep it running.

Required IB Gateway / TWS Settings

Open the API settings in your IB Gateway or TWS (Edit → Global Configuration → API → Settings) and configure:

Then go to Configure → Lock and Exit:

2 Prerequisites

• Python 3.10+ — check with python3 --version
• IB Gateway running and logged in as your monitor user
• Telegram account

3 Install the Agent

During onboarding, you will receive two files:

• risk_radar-0.1.0-py3-none-any.whl — the agent package
• .env.example — configuration template

# Create a directory for Risk Radar
mkdir risk-radar && cd risk-radar

# Create virtual environment (first time only)
python3 -m venv .venv

# Activate
source .venv/bin/activate   # macOS/Linux

# Install the agent from the .whl file you received
pip install risk_radar-0.1.0-py3-none-any.whl

After install, the risk-radar command is available in your virtual environment.

4 Create Your Telegram Bot

1. Open Telegram, search for @BotFather
2. Send /newbot and follow the prompts
3. Copy the bot token (looks like 123456:ABC-DEF1234ghIkl-zyx57W2v1u123ew11)
4. Send any message to your new bot
5. Get your chat ID: open https://api.telegram.org/bot<YOUR_TOKEN>/getUpdates and find "chat":{"id":123456789}
6. If the page shows {"ok":true,"result":[]} (empty), you didn’t message the bot first. Send your bot a direct 1:1 message, then reload the URL within a minute. The bot must be messaged directly — not just created, and not only added to a group.

5 Configure .env

cp .env.example .env

Edit .env with your values:

# IBKR Connection (your local IB Gateway)
IBKR_HOST=127.0.0.1
IBKR_PORT=4001
IBKR_CLIENT_ID=100

# Telegram (your own bot)
TELEGRAM_BOT_TOKEN=your_bot_token_here
TELEGRAM_CHAT_ID=your_chat_id_here
TELEGRAM_ENABLED=true

# Backend (provided during onboarding)
BACKEND_URL=https://risk-radars.com/api
CF_ACCESS_CLIENT_ID=provided_during_onboarding
CF_ACCESS_CLIENT_SECRET=provided_during_onboarding

6 Test Telegram

Before connecting to IBKR, verify Telegram works:

source .venv/bin/activate
risk-radar --test-alert

Success: You receive a test message in Telegram.

7 Start the Agent

Make sure IB Gateway is running with your monitor user logged in:

source .venv/bin/activate
risk-radar

You should see:

• Connected to IBKR in the terminal
• Account poll successful messages
• Dashboard at risk-radars.com shows your account
• Telegram sends connection notification

If you open the dashboard and see account data that is not yours (an account number, positions, or P&L you don’t recognise), stop and contact me immediately — your dashboard was not set up correctly. Do not continue.

8 Run Persistently

macOS / Linux (tmux)

tmux new-session -d -s risk-radar \
  'cd /path/to/risk-radar && source .venv/bin/activate && risk-radar'

# Reattach anytime:
tmux attach -t risk-radar

Linux (systemd)

[Unit]
Description=Risk Radar Agent
After=network.target

[Service]
Type=simple
User=youruser
WorkingDirectory=/path/to/risk-radar
ExecStart=/path/to/risk-radar/.venv/bin/risk-radar
Restart=always
RestartSec=10

[Install]
WantedBy=multi-user.target

During beta, we’ll help you configure persistent operation during your onboarding call.

Troubleshooting

What Risk Radar Does NOT Do

• No trading — read-only, cannot place or cancel orders
• No IBKR credentials stored server-side — your login stays on your machine
• No trading signals — no predictions, informational only
• No kill switch — cannot shut down your trading system

Need Help?

This is early beta. If setup fails at any step, contact the founder directly. We’ll walk you through it.

← Back to Risk Radar