Deep dives on building software — from the cluster up to the agent.
I’m Raveesh, a full stack builder. I run a Kubernetes cluster on my desk, build with MCP and agentic AI, and write down what I learn — in depth, with the code. More about me →
Kubernetes and Cloud Native
Kubernetes, homelabs and the CNCF landscape — run for real.
MCP and Agentic AI
The Model Context Protocol and AAIF projects.
Becoming a Full Stack Builder
The craft, and what it means if you are just starting out.
Experiments with Distributed Systems
Scale, and deep dives into how distributed systems behave.
Commerce and Agentic Commerce
Commerce systems, and what changes when agents become the buyers.
Latest
-
![[dedo] 5/5: Multi-Tenant SaaS Auth](https://raveesh.me/wp-content/uploads/sites/2/2026/10/dedo-05-hero.png)
[dedo] 5/5: Multi-Tenant SaaS Auth
A scope says what a caller may do. A tenant says where. dedo now declares the tenant boundary in the proto, checks it in lint, and enforces it on every transport before your handler runs.
More writing
-
![[dedo] 4/5: House Rules, Your Conventions as Lint](https://raveesh.me/wp-content/uploads/sites/2/2026/10/dedo-04-hero.png)
[dedo] 4/5: House Rules, Your Conventions as Lint
Every organisation has conventions no public standard knows about. dedo lets you write them as CEL checks in rules.yml, share them from…
-
![[dedo] 3/5: Adding dedo to an Existing Service](https://raveesh.me/wp-content/uploads/sites/2/2026/10/dedo-03-hero.png)
[dedo] 3/5: Adding dedo to an Existing Service
dedo installs one layer at a time: annotations, lint, generators, runtime. Each layer pays for itself. Audit before you enforce.
-
![[dedo] 2/5: Getting Started: Todo Good and Todo Bad](https://raveesh.me/wp-content/uploads/sites/2/2026/10/dedo-02-hero.png)
[dedo] 2/5: Getting Started: Todo Good and Todo Bad
Two to-do services with the same interface. One follows every rule. One breaks every rule, and its tests show what each mistake…
-
![[dedo] 1/5: Define Once, Deploy Everywhere](https://raveesh.me/wp-content/uploads/sites/2/2026/10/dedo-01-hero.png)
[dedo] 1/5: Define Once, Deploy Everywhere
One .proto file can carry an API’s contract and its operational rules. A linter can make good architecture the easy path. This…
-
Why Is It v1 for a Namespace but apps/v1 for a Deployment?
If you’ve written more than a couple of Kubernetes manifests, you’ve probably copy-pasted these lines without thinking too hard about them:
-
Why a thousand containers weigh almost nothing
Docker can run a hundred copies of the same image without storing it a hundred times. The trick is copy-on-write — and…
-
Stop Naming Your Servers: The Pets vs. Cattle Metaphor That Changed Infrastructure Forever
Somewhere in a server room, there is a machine called gandalf. It has been running for 1,400 days. Nobody remembers exactly what’s…
-
Multi-Tenant ERPNext on a Local Kubernetes Cluster
Running three independent businesses on one homelab K8s deployment — with replicated storage, automated cloud backups, and zero vendor lock-in.
-
Longhorn on MicroK8s: Replicated Storage for a 4-Node Homelab Cluster
Skip NFS-in-a-pod, skip Ceph. Longhorn gives you distributed, replicated storage on bare metal in under 10 minutes.