Compute
Scalable application and workload hosting
Scroll to connect the infrastructure and intelligence stack
I build secure cloud foundations, automate delivery, and develop applied AI workflows spanning model training, RAG, API serving, evaluation, and MLOps.
Adaptive copy runs locally from the section you explore. No tracking.
Scalable application and workload hosting
Subnets, routing, security, and isolation
Artifacts, backups, and data workflows
Containers, health, scaling, and GitOps
Data preparation, experiments, and evaluation
Embeddings, search, grounding, and APIs
Serving, versioning, monitoring, and rollout
Build, test, publish, deploy, and verify
Selected work
Each project is labeled by context so client delivery, engineering labs, and open-source work are never presented as the same thing.
A customized data platform packaged as a repeatable 13-service deployment with generated secrets, health probes, system startup, backup workflows, and an operator handover.
A cloud-native education platform used to demonstrate repeatable AWS provisioning, K3s orchestration, GitOps synchronization, and health-aware releases.
A standardized delivery lab comparing Docker Compose, Kubernetes, and Helm workflows with automated container builds and readiness verification.
Looking for interactive experiments, architecture utilities, or incident simulations?
Visit the engineering labExpertise
Tools matter, but only when they improve delivery speed, resilience, security, or operational clarity.
AWS VPC design, IAM boundaries, secure networking, compute, storage, DNS, and recovery-aware infrastructure.
Repeatable delivery paths that replace long checklists with versioned, testable automation.
Health checks, observability, backup workflows, rollback planning, and documentation operators can use.
Hands-on AI engineering across dataset preparation, model training, retrieval systems, evaluation, API serving, and model operations.
Services
Starting ranges are directional. A short discovery call confirms requirements, access, risk, and delivery timing.
For teams that need a secure, understandable foundation before applications are deployed.
For multi-service applications that are slow, fragile, or inconsistent to install and operate.
For teams ready to move from manual cluster changes to reviewed, observable delivery.
For teams moving an AI experiment beyond a notebook into a testable, observable application workflow.
Working process
Access, success criteria, and rollback expectations are agreed before implementation begins.
Map the current system, constraints, owners, and failure points.
Agree on architecture, risks, deliverables, and acceptance checks.
Implement in version control and validate the operational path.
Transfer documentation, recovery steps, and ownership clearly.
About
I’m Lakshay, a cloud, DevOps, and AI engineer based in Delhi. My work connects infrastructure, delivery automation, model workflows, and the people who operate what gets delivered.
I care about predictable deployments, useful health signals, realistic recovery plans, and documentation that survives the original builder. My AI engineering work includes model-training experiments, retrieval systems, evaluation, API serving, and MLOps workflows.
Technical writing
Notes on deployment design, GitOps workflows, and infrastructure trade-offs.
Dependency ordering, generated secrets, health checks, and the operator experience.
Read article GitOps · 7 minRepository structure, drift correction, readiness, and when automation should stop.
Read article Infrastructure as code · 6 minInputs, boundaries, safe defaults, cost decisions, and output verification.
Read articleContact
Share the current state, what keeps breaking, and what “done” should look like. I’ll reply with questions or a realistic next step.