"I was interested in doing it, there was an opportunity, so I just did it." — Barbara Liskov

AGI, one linear layer at a time.

Systems engineer and fractional CTO based in Madurai, India. I build infrastructure, developer tools, and systems software with a focus on simplicity, security, performance, and long-term maintainability.

Building BlackLoverTech — technology that builds, understands, and protects systems.

I believe good engineering starts with understanding the problem, choosing the right abstractions, and keeping the implementation as simple as possible.

I build from first principles when it provides meaningful control or insight. I reuse proven solutions when they already solve the problem well.

Build from first principles. Reuse what works. Own what matters.

• Open source first. Prefer transparent, auditable software and open standards.
• Simplicity over complexity. Build the smallest architecture that solves the problem well.
• Proven over fashionable. Choose mature tools and validated approaches over novelty without evidence.
• Understand the stack. Learn how systems work beneath their abstractions.
• Own the critical path. Implement core components when control, security, or performance justifies the cost.
• Minimal dependencies. Prefer compact systems, predictable deployments, and standalone binaries.
• AI-friendly architecture. Keep codebases consistent and easy for humans and AI tools to understand.
• Measure before optimizing. Use profiling, benchmarks, and repeatable tests.
• Security by design. Minimize attack surfaces and define clear trust boundaries.
• Build, ship, improve. Validate software in real environments and iterate.

My main interests are systems programming, Linux infrastructure, virtualization, cloud engineering, and AI infrastructure. The icons represent technologies of interest, not necessarily equal levels of experience.

Exploring how to build infrastructure platforms from the ground up:

• Simple control planes and reliable automation.
• Lightweight virtualization with Firecracker MicroVMs.
• Secure workload execution and isolation.
• Efficient build and deployment systems.
• Practical observability and operational tooling.
• AI inference systems and the infrastructure around them.

The goal is not to rebuild everything. It is to understand the important parts, remove unnecessary complexity, and build only what provides real value.

A short snapshot of what I'm actually working on — updated when things change.

Last updated: October 2026

• Building BlackLoverTech — tooling that builds, understands, and protects systems.
• Writing infrastructure and control-plane code around Firecracker MicroVMs.
• Shipping small, focused tools: porter, nammapush-rs, tally-web.
• Writing about systems, infrastructure, and security on Medium.
• Open to fractional CTO engagements and infrastructure work.

I am interested in systems with clear boundaries, small components, and explicit communication between layers.

flowchart TB
    U["Users and Developers"]
    C["Control Plane"]
    A["Host Agent"]
    R["Runtime and Isolation"]
    N["Networking and Storage"]
    O["Observability"]

    U <--> C
    C <--> A
    A --> R
    A --> N
    R --> O
    N --> O

    classDef control fill:#172554,stroke:#60A5FA,color:#FFFFFF
    classDef runtime fill:#052E2B,stroke:#2DD4BF,color:#FFFFFF
    classDef observe fill:#312E81,stroke:#A5B4FC,color:#FFFFFF

    class C,A control
    class R,N runtime
    class O observe

Conceptual architecture illustrating my infrastructure interests, not a claim that every component belongs to one deployed system.

These cards use external services. Their availability and displayed statistics depend on GitHub data and each service.

Explore my repositories for systems engineering, infrastructure, developer tooling, and experiments.

I value systems that are easy to understand, operate, debug, and maintain. Good software should not require unnecessary complexity to remain reliable.

I am interested in the intersection of systems engineering, infrastructure, security, and AI — especially where a small, well-designed implementation can replace a much larger and harder-to-maintain system.

Keep it simple. Keep it sovereign. Keep it running.

GitHub · Website · LinkedIn · Medium