A real-time, AI-driven infrastructure monitoring and orchestration platform for visualizing infrastructure health, detecting incidents, simulating failures, analyzing telemetry, and coordinating real-time recovery workflows.
Live Production Application
👉 https://nexus-frontend-xveb.onrender.com
Use the live frontend to access the complete NEXUS infrastructure monitoring and orchestration interface.
Production Backend
👉 https://nexus-backend-vv37.onrender.com
👉 https://nexus-backend-vv37.onrender.com/health
Expected response:
{
"status": "ok",
"service": "NEXUS backend"
}👉 https://github.com/atulsharma47/Autonomous-Infrastructure-Orchestration-System
Autonomous Infrastructure Orchestration System is a modern full-stack platform designed to simulate how distributed infrastructure environments can be monitored, analyzed, visualized, and stabilized in real time.
The system combines:
- Real-time telemetry
- Infrastructure topology visualization
- Incident management
- Event-driven workflows
- Socket.IO real-time communication
- Infrastructure health monitoring
- Operational analytics
- Failure and threat simulation
- Authentication and protected sessions
- Live infrastructure orchestration
The platform is designed as a portfolio-grade infrastructure operations system that demonstrates how frontend dashboards, backend services, real-time communication, telemetry processing, and incident workflows can work together as one system.
The main dashboard provides a centralized operational view of the infrastructure environment.
- Live infrastructure telemetry
- CPU and system utilization monitoring
- Traffic monitoring
- Latency monitoring
- Infrastructure health overview
- Service status visualization
- Real-time orchestration activity
- Animated infrastructure state changes
- Operational event visibility
The Infrastructure section provides a visual representation of the distributed infrastructure environment.
- Infrastructure topology visualization
- Service dependency tracking
- Node health monitoring
- Service status monitoring
- Critical service detection
- Infrastructure relationship visualization
- Real-time state updates
The goal is to provide an operator-friendly representation of the infrastructure rather than relying only on raw logs and metrics.
The Incident Command Center is responsible for monitoring and managing infrastructure incidents.
- Incident creation
- Incident lifecycle tracking
- Infrastructure risk evaluation
- Incident severity visualization
- Operational logs
- Incident state changes
- Escalation tracking
- Recovery state monitoring
- Real-time incident updates
The system uses event-driven communication to propagate infrastructure state changes across connected clients.
The Analytics section provides a visual representation of infrastructure performance and operational activity.
- Real-time telemetry analytics
- Traffic visualization
- Latency analysis
- Service health tracking
- Infrastructure performance metrics
- Operational trend visualization
- Infrastructure activity monitoring
Charts and visualizations are implemented using Recharts.
The system includes a simulation environment for testing infrastructure failure and recovery workflows without requiring real production infrastructure.
- DDoS-style traffic spikes
- Infrastructure failures
- Service degradation
- Incident propagation
- Recovery workflows
- Infrastructure stability testing
- Real-time failure visualization
The simulation engine allows infrastructure events to propagate through the application and be reflected in dashboards and incident workflows.
⚠️ Simulations are intended for demonstration, testing, and educational purposes. They do not perform real-world DDoS attacks or infrastructure disruption.
The application includes an authentication layer for protecting infrastructure operations.
- User registration
- User login
- Protected application sessions
- JWT-based authentication
- Password hashing
- Authorization headers
- Client-side token persistence
Authentication requests are handled by the backend API while protected requests automatically attach the JWT token through the frontend API service.
One of the core parts of NEXUS is its real-time communication architecture.
The application uses Socket.IO to synchronize infrastructure state between the backend and connected frontend clients.
┌──────────────────────┐
│ User Browser │
│ React + Vite App │
└──────────┬───────────┘
│
REST API + Socket.IO
│
▼
┌─────────────────────────┐
│ Node.js Backend │
│ Express + Socket.IO │
└────────────┬────────────┘
│
Telemetry / Events
│
▼
┌─────────────────────────┐
│ Infrastructure │
│ Simulation / Processing │
└────────────┬────────────┘
│
▼
┌───────────────────┐
│ MongoDB Atlas │
└───────────────────┘
This architecture allows the frontend to receive infrastructure events without repeatedly polling the backend.
┌─────────────────────────────────────────────────────────────┐
│ NEXUS PLATFORM │
├─────────────────────────────────────────────────────────────┤
│ │
│ React Frontend │
│ │
│ Dashboard │ Infrastructure │ Incidents │ Analytics │ Sim │
│ │
├───────────────────────────┬─────────────────────────────────┤
│ │ │
│ REST API │
│ │ │
│ Socket.IO │
│ │ │
├───────────────────────────▼─────────────────────────────────┤
│ Node.js Backend │
│ │
│ Express │ Authentication │ Incidents │ Telemetry │
│ │
│ Simulation Engine │ Metrics Engine │ Socket Layer │
│ │
├─────────────────────────────────────────────────────────────┤
│ │
│ MongoDB Atlas │
│ │
└─────────────────────────────────────────────────────────────┘
| Technology | Purpose |
|---|---|
| React.js | Frontend UI |
| Vite | Frontend build tooling |
| Tailwind CSS | Styling |
| Framer Motion | UI animations |
| GSAP | Advanced animations |
| Recharts | Analytics visualization |
| Axios | REST API communication |
| Socket.IO Client | Real-time communication |
| React Router | Application routing |
| Technology | Purpose |
|---|---|
| Node.js | Backend runtime |
| Express.js | REST API |
| Socket.IO | Real-time communication |
| MongoDB Atlas | Database |
| Mongoose | MongoDB ODM |
| JWT | Authentication |
| bcryptjs | Password hashing |
| CORS | Cross-origin communication |
| dotenv | Environment configuration |
Autonomous-Infrastructure-Orchestration-System/
│
├── backend/
│ ├── src/
│ │ ├── routes/
│ │ ├── controllers/
│ │ ├── models/
│ │ ├── services/
│ │ ├── simulation/
│ │ ├── sockets/
│ │ ├── telemetry/
│ │ └── server.js
│ │
│ ├── package.json
│ └── ...
│
├── frontend/
│ ├── public/
│ │ └── screenshots/
│ │ └── screenshots/
│ │
│ ├── src/
│ │ ├── ai/
│ │ ├── animations/
│ │ ├── assets/
│ │ ├── auth/
│ │ ├── components/
│ │ ├── context/
│ │ ├── layouts/
│ │ ├── pages/
│ │ ├── services/
│ │ ├── styles/
│ │ └── widgets/
│ │
│ ├── package.json
│ └── ...
│
├── .gitignore
└── README.md
Make sure you have the following installed:
- Node.js
- npm
- Git
- MongoDB Atlas account
Recommended:
Node.js 20+
npm 10+
git clone https://github.com/atulsharma47/Autonomous-Infrastructure-Orchestration-System.gitNavigate into the project:
cd Autonomous-Infrastructure-Orchestration-SystemNavigate to the frontend:
cd frontendInstall dependencies:
npm installCreate:
.env.local
Add:
VITE_API_URL=http://localhost:5000/api
VITE_SOCKET_URL=http://localhost:5000Start the development server:
npm run devFrontend will normally be available at:
http://localhost:5173
Open another terminal.
Navigate to the backend:
cd backendInstall dependencies:
npm installCreate:
.env
Configure:
PORT=5000
MONGO_URI=your_mongodb_atlas_connection_string
JWT_SECRET=your_jwt_secret
FRONTEND_URL=http://localhost:5173Start the backend:
npm startFor development with automatic restart:
npm run devBackend will normally run at:
http://localhost:5000
Health check:
http://localhost:5000/health
VITE_API_URL=http://localhost:5000/api
VITE_SOCKET_URL=http://localhost:5000For production:
VITE_API_URL=https://nexus-backend-vv37.onrender.com/api
VITE_SOCKET_URL=https://nexus-backend-vv37.onrender.comPORT=5000
MONGO_URI=your_mongodb_connection_string
JWT_SECRET=your_secret
FRONTEND_URL=http://localhost:5173For production:
FRONTEND_URL=https://nexus-frontend-xveb.onrender.comNever commit
.envfiles or database credentials to GitHub.
The backend exposes API routes under:
/api
/api/auth
Handles authentication-related operations such as registration and login.
/api/users
Handles user-related operations.
/api/incidents
Handles infrastructure incident operations.
/health
Used to verify backend availability.
The production application is deployed using Render.
React + Vite
↓
Render Static Site
↓
https://nexus-frontend-xveb.onrender.com
Node.js + Express
↓
Render Web Service
↓
https://nexus-backend-vv37.onrender.com
MongoDB Atlas
Frontend
https://nexus-frontend-xveb.onrender.com
│
│ HTTPS REST API
│
▼
Backend
https://nexus-backend-vv37.onrender.com
│
├──────── REST API
│
├──────── Socket.IO
│
▼
MongoDB Atlas
The frontend uses environment variables to communicate with the production backend.
The backend uses FRONTEND_URL to configure CORS for both Express and Socket.IO.
Run the frontend linting:
cd frontend
npm run lintBuild the production frontend:
npm run buildStart the backend:
cd backend
npm startVerify the backend:
http://localhost:5000/health
Expected:
{
"status": "ok",
"service": "NEXUS backend"
}A typical infrastructure event follows this flow:
Infrastructure Event
│
▼
Telemetry / Simulation Engine
│
▼
Incident / Metrics Processing
│
▼
Socket.IO Event
│
▼
Connected Frontend Clients
│
▼
Dashboard / Analytics / Incident UI
This allows infrastructure state changes to be reflected across the application in real time.
The repository excludes sensitive and generated files through .gitignore.
Ignored files include:
.env
.env.*
node_modules/
dist/
coverage/
*.log
.vscode/
.DS_Store
Thumbs.db
- JWT-based authentication
- Password hashing with bcrypt
- Environment-based secrets
- MongoDB credentials stored outside source control
- Production CORS configuration
- No database credentials in frontend code
The infrastructure simulation functionality is designed for:
- Educational demonstrations
- Portfolio demonstrations
- Infrastructure testing concepts
- Failure-recovery workflow visualization
- Software development and testing
It does not perform real-world attacks or intentionally disrupt external infrastructure.
Potential future improvements include:
- AI-powered anomaly detection
- Machine-learning-based threat prediction
- Kubernetes integration
- Docker-based infrastructure environments
- Cloud infrastructure integrations
- Distributed telemetry streaming
- Advanced role-based access control
- Alert notification integrations
- Prometheus/Grafana integration
- Infrastructure-as-Code integration
- Automated remediation workflows
- Multi-region infrastructure visualization
- Advanced audit logging
- Production-grade observability
The current platform supports:
- ✅ Real-time telemetry synchronization
- ✅ Infrastructure health monitoring
- ✅ Incident state tracking
- ✅ Service dependency visualization
- ✅ Infrastructure risk visualization
- ✅ Live operational logging
- ✅ Event-driven updates
- ✅ Socket.IO real-time communication
- ✅ Infrastructure simulation
- ✅ Authentication
- ✅ JWT authorization
- ✅ Analytics dashboards
- ✅ Production frontend deployment
- ✅ Production backend deployment
- ✅ MongoDB Atlas integration
Backend-focused developer interested in building real-time systems, scalable APIs, full-stack applications, infrastructure tooling, and intelligent automation platforms.
👉 https://github.com/atulsharma47
👉 https://www.linkedin.com/in/atul-sharma-ab03882b6/
This project is intended for educational, portfolio, demonstration, and research purposes.
If you find this project interesting, consider giving the repository a ⭐ on GitHub.
Repository: https://github.com/atulsharma47/Autonomous-Infrastructure-Orchestration-System
Live Application: https://nexus-frontend-xveb.onrender.com
| Resource | Link |
|---|---|
| 🌐 Live Application | https://nexus-frontend-xveb.onrender.com |
| ⚙️ Backend API | https://nexus-backend-vv37.onrender.com |
| ❤️ Backend Health | https://nexus-backend-vv37.onrender.com/health |
| 📦 GitHub Repository | https://github.com/atulsharma47/Autonomous-Infrastructure-Orchestration-System |
| 👨💻 GitHub Profile | https://github.com/atulsharma47 |
| https://www.linkedin.com/in/atul-sharma-ab03882b6/ |
Autonomous Infrastructure Orchestration System
Monitor. Analyze. Simulate. Orchestrate. Recover.





