EIMS (Enterprise Infrastructure Management System) is an enterprise-grade platform engineered to centralize compute infrastructure discovery, hardware inventory tracking, automated optical character recognition (OCR) asset registration, continuous Windows log diagnostics, rules-based compliance auditing, and live operational visibility.
Important
This project is NOT an Open Source software product. EIMS is published under a strict Source-Available / All Rights Reserved proprietary licensing model (LICENSE).
| Licensing Parameter | Authoritative Project Policy |
|---|---|
| Repository Visibility | Public (Exclusively for architectural evaluation and technical portfolio demonstration). |
| Source Code Visibility | Public |
| License Type | All Rights Reserved (See LICENSE and NOTICE specifications). |
| Open Source Rights | No (Public visibility does not imply or confer any open-source usage rights). |
| Commercial Utilization | Not permitted without express prior written commercial license authorization. |
| Redistribution Rights | Not permitted under any circumstances. |
| Modification & Derivation | Not permitted unless explicitly authorized in writing by project copyright owners. |
| Trademark Rights | Strictly Reserved |
Commercial distribution and operational deployment licensing will be made available upon formal request in future product lifecycle stages.
This project is currently under active development.
- Sprint 0 – Documentation Foundation ✅
- Sprint 1 – Engineering Specifications ✅
- Sprint 2 – Backend Foundation ✅
- Sprint 3 – Telemetry Collector & Discovery Agent Ingestion ✅
- Sprint 4 – MinIO Integration & OCR Asset Registration ✅
- Sprint 5 – Windows Log Analytics & Compliance Score Engines ✅
- Sprint 6 – Operational Dashboard & Enterprise Observability ✅
- Sprint 7 – Enterprise Portal, Client Agents & UI Polish ✅
- Sprint 8 – Service Evaluation System (Admin & Mobile Form) ✅
- Sprint 9 – AI Log Analyzer (EventIQ Integration & Vector RAG Engine) ✅
- Sprint 10 – Global Search & Timeline (Next Target / Active)
- Sprint 11+ – High Availability & Public Exposure
The project is currently transitioning toward upcoming enterprise clustering operational milestones.
For detailed instructions on how to start the backend, frontend dashboard, agent simulation, and database infrastructure, please refer to the EIMS Developer Cheatsheet. (Includes a Troubleshooting section for resolving dependency and caching issues).
EIMS utilizes a Hybrid Modular Monolith paired with an Asynchronous Event-Driven Ingestion Architecture. High-frequency diagnostic telemetry and security events stream over Mutual TLS (mTLS) into real-time Redis queues, decoupling rapid network ingestion from synchronous relational PostgreSQL database writes.
flowchart LR
classDef service fill:#1E293B,stroke:#475569,color:#FFFFFF,stroke-width:2px;
classDef store fill:#1E40AF,stroke:#3B82F6,color:#FFFFFF,stroke-width:2px;
classDef agent fill:#047857,stroke:#10B981,color:#FFFFFF,stroke-width:2px;
classDef ui fill:#5B21B6,stroke:#8B5CF6,color:#FFFFFF,stroke-width:2px;
Agent[Discovery Agent] -->|mTLS HTTPS Telemetry| Collector[FastAPI Telemetry Collector]
Collector -->|LPUSH Redis Stream| Broker([Redis Event Broker])
Broker -->|Consume Batch Queue| Worker[Telemetry & Log Worker]
Worker -->|Batch SQL UPSERT| Pool[PgBouncer Pool]
Pool <-->|TCP Relational Trunk| DB[(PostgreSQL Asset Registry)]
Operator[System Administrator] <-->|WSS Real-time Feed| UI[Next.js Operational Dashboard]
UI <-->|OpenAPI / REST| Gateway[FastAPI Core Gateway]
Gateway <--> Pool
class Agent,Operator agent;
class Collector,Broker,Worker,Pool,Gateway service;
class DB store;
class UI ui;
All software implementation, database schema modeling, and API routing within EIMS strictly obey our foundational architectural specifications (Core Laws) governed under the frozen EIMS Documentation System (EDS v1.0.0):
- Core Law 1: EIMS Master Plan — Architectural vision, technology selection trade-off evaluations (FastAPI, Next.js, PostgreSQL, Redis, MinIO, Docker), and product development sprint milestones.
- Core Law 2: Product Requirements Document — Binding functional execution capabilities, operational personas (
System Administrator,Security Auditor), and verifiable Requirement Traceability IDs (REQ-DISC-01throughNFR-SCALE-02). - Core Law 3: Software Architecture Document — C4 container topology boundaries, edge sequence flows (<15ms HTTP 202 latencies), PgBouncer transaction pooling, and asset lifecycle state transition tables.
- Core Law 4: Database Design Specification — Complete PostgreSQL relational tables, Mermaid Entity-Relationship diagrams (
erDiagram), composite B-Tree/GIN JSONB indexes, declarative monthly time-series partitioning, and Volatile-LRU Redis namespace definitions. - Core Law 5: API Specification — Canonical REST / OpenAPI routing protocols, secure WebSocket channels (
WSS /api/v1/ws/dashboard), mTLS authentication parameter contracts, and RFC 7807 Problem Details error schemas.
We practice professional software engineering governance. Before interacting with our public evaluation repositories or reviewing architectural proposals, visitors must read our engineering conventions:
- Contributing Handbook: Details Git branching standards (
feature/,fix/,docs/), Conventional Commits formatting rules, and documentation-first development practices. - Security & Vulnerability Disclosure Policy: Outlines responsible private reporting channels for diagnostic vulnerability submissions.
- Community Code of Conduct: Binds evaluation community observers to professional collaborative standards under Contributor Covenant v2.1.
- Changelog Archive: Records sequential platform engineering progressions and historical milestone tagging.
Copyright 2026 EIMS Project Engineering Team & Ratthabhumi. Licensed under All Rights Reserved / Source-Available Proprietary Policy.