Full Stack & Source
Project Brahmanda
A Hybrid-Cloud Universe Manifested through Code. Orchestrating complexity into a singular, resilient cosmic dance.
The Philosophy
Asanga Shastra: The Weapon of Detachment.
In the Brahmanda ecosystem, infrastructure is not a permanent monument; it is a transient state. By leveraging Infrastructure as Code (IaC), we treat our entire stack as a sword that can strike down the old and manifest the new in milliseconds.
Detachment from hardware allows for absolute reliability. We do not patch; we destroy and recreate. This is the ultimate form of digital evolution.
The Cosmology
Three interconnected planes forming the infinite loop of the Brahmanda universe.
The system separates responsibilities into practical planes: cloud ingress and durable services, local compute on Proxmox, and automation loops that continuously reconcile desired state.
Nebula provides the private mesh between AWS and on-premise workloads, while GitOps keeps Kubernetes workloads aligned with the repository.
Kshitiz (The Edge)
Where the digital meets the physical. Distributed gateways providing low-latency entry points into the cosmic grid.
Vyom (The Compute)
The central void where logic resides. Massive, elastic compute clusters residing in high-availability zones.
Samsara (Automation)
The cycle of birth and rebirth. CI/CD pipelines and self-healing mechanisms ensuring eternal uptime.
Security
Zero-Trust Chakravyuha
A multi-layered Nebula Mesh where identity is the only perimeter. Like the legendary battlefield formation, every packet must navigate a complex web of mTLS encryption and cryptographic verification.
Like the legendary battlefield formation, access is layered: mTLS protects transport, identity defines trust, defense-in-depth absorbs mistakes, and rebuildable state keeps the platform resilient.
mTLS
End-to-end cryptography for the private mesh and service-to-service paths.
Identity
Explicit trust boundaries built around nodes, certificates, and workload intent.
Defense-in-depth
Independent network, identity, storage, and rebuild controls reduce blast radius when one layer fails.
The Manifested Stack
Terraform
Ansible
Redis
Cloudflare R2
Longhorn
ArgoCD
K3s
Linkerd
Grafana
Loki
AWS Lightsail
Proxmox
Nebula
PrometheusExecution
Deployment terminal
root@brahmanda: ~/deployment
[SYSTEM] Initializing Srishti Protocol...
$ make srishti
brahmanda@root: > Initializing Terraform provider: aws...
brahmanda@root: > Fetching state from remote backend...
brahmanda@root: > Plan: 14 to add, 0 to change, 0 to destroy.
brahmanda@root: > Creation in progress: vpc-brahmanda-core...
brahmanda@root: > Creation in progress: k3s-cluster-vyom-01...
brahmanda@root: > Provisioning Samsara-Automation-Pipeline...
brahmanda@root: > Deploying Asanga-Shastra-IaC Manifests...
brahmanda@root: > Configuring Nebula mTLS mesh network...
brahmanda@root: > [SUCCESS] Srishti manifested in 42.18s.
brahmanda@root: > Cluster health: 100% | Latency: 4ms
brahmanda@root: > Brahmanda is online and detaching from old instances...
The Loop Closes: Live Execution
You are currently interacting with a system served directly from the Vyom core.
Every byte of this experience is delivered through the very Kshitiz gateway and Samsara pipelines documented above—proving that detachment from the cloud doesn't mean detachment from performance.
Project Brahmanda • Built by Abhishek Kashyap
Open Source Blueprint
The core architecture is Open Source, providing a complete blueprint from void to manifestation. Internal iterations continue beyond the public MVP to refine the celestial machinery.
View Repository (opens in a new tab)Architectural Clarity
The GitHub repository serves as a complete architectural blueprint. Even at the MVP stage, the provided manifests and guides are sufficient for anyone to replicate this entire cosmic setup on their own hardware.