If you expose the backend endpoint, restrict access to trusted IP addresses only. Use firewall rules, a reverse proxy, or VPN/SSH tunneling to whitelist specific IPs. Never leave the port publicly accessible, or unauthorized users could gain control of your servers.

This is a personal project I built to help manage multiple RDP servers more easily. I'm not particularly skilled at frontend development, so this is primarily a backend-focused tool with a functional interface for monitoring and controlling my servers. It started as a test for myself but became quite useful for managing multiple RDP connections.

• Real-time CPU, RAM, and network usage tracking
• Live screen capture from connected agents
• Active process monitoring with kill capability
• Performance history usage

• Create and manage tasks
• Set priorities (critical, high, medium, low)
• Track task completion status

• View active processes
• Terminate processes remotely
• Monitor server status (online/offline)

• Runs as a background service on target machines
• Collects system metrics (CPU, RAM, network, processes)
• Captures screen for remote viewing
• Responds to remote commands (like killing processes)

This project uses GitHub Actions for automated testing, security scanning, and staged deployment.

• Backend tested on Python 3.8–3.11
• Frontend tested on Node.js 18–22
• Linting (flake8 & ESLint)
• Dependency vulnerability scanning (safety)
• Secret scanning (TruffleHog)
• CodeQL analysis
• Dev → Prod staged deployment on push to main

Workflows are located in: .github/workflows/

The system consists of two parts:

1. Backend Server (written in Python/FastAPI) - runs on your main control machine
2. Agent (written in Python) - runs on each server you want to monitor

The agent connects to the backend via WebSocket and continuously sends system metrics. The frontend provides a dashboard to view this information and send commands.

• Python 3.8+
• Node.js and npm (for the frontend)
• Windows/Linux/macOS (agent works on all platforms)

1. Clone the repository
2. Navigate to the backend directory
3. Install Python dependencies:

   pip install -r requirements.txt

4. Set up environment variables in .env file:

   SECRET_KEY=your-very-secure-secret-key
   AGENT_SECRET=your-agent-authentication-secret
   

1. Navigate to the frontend directory
2. Install dependencies:

   npm install

3. Start the development server:

   npm run dev

1. Start the backend server:

   cd backend
   python app.py

   Or with uvicorn:

   uvicorn app:app --reload --host 127.0.0.1 --port 8000

2. Start the frontend:

   cd frontend
   npm run dev

3. Run the agent on each server you want to monitor:

   cd backend
   python agent.py

   Make sure to update the BACKEND_URL in agent.py to match your backend server's address.

By default, the backend server listens on 127.0.0.1:8000. This is intentional for security. Do NOT expose this port publicly. If you need remote access, use VPN or SSH tunneling.

The CORS configuration in app.py should be reviewed to only allow origins you trust:

CORS_ORIGINS: list[str] = ["http://localhost:5173", "http://localhost:3000"]

1. Access the frontend at http://localhost:5173 (or wherever your frontend is hosted)
2. The dashboard will show connected servers and their metrics
3. Use the Process Manager to view and kill processes
4. Manage tasks using the task manager panel
5. View live screen feeds from your servers

• This is a personal project, not enterprise-grade software
• Frontend design is basic and functional rather than polished
• Designed for single-user personal use
• Requires Python on monitored servers to run the agent
• Screen capture feature may not work on some locked sessions (expected behavior)

You can modify:

• The agent to collect different metrics
• The frontend to display additional information
• The backend to store data differently
• Authentication mechanisms to fit your needs

• If agents can't connect: Check that the BACKEND_URL in agent.py matches your server address
• If screen capture fails: This is expected on locked sessions or with certain security configurations
• If metrics aren't updating: Check WebSocket connections and firewall settings

Personal project for educational purposes. If using this code, please respect any applicable licenses for the dependencies used.