Skip to content
Aditya Dalmia
All projects

BNC Cloud

The cloud behind the things I build.

My work
Platform architecture and operations
Status
Independent platform
Built with
k3s, ArgoCD, NetBird, Temporal, Postgres
BNC CloudArchitecture map
One platform. Many independent projects.

A shared foundation

The platform brings together cloud workers and a dedicated Hetzner server, with reusable data services, observability, secrets management, and a private image registry. It is designed for independent projects with explicit availability and capacity tradeoffs.

Access by responsibility

WireGuard provides the administrative path. NetBird connects private applications and agent tools. Separate ingress paths distinguish public applications from internal services.

Durable work

I deploy and integrate upstream Temporal, then build application workflows above it. The earlier ExplainLM rendering prototype provided a real consumer for queue routing, failure handling, and capacity fallback.

What the inventory proves

The repository snapshot reviewed on September 22, 2026 contains 68 top-level GitOps Application definitions. This is configured inventory, not a verified count of currently healthy services. The live cluster count is pending network access.

The build, in writing.

4 notes on the architecture, experiments, and tradeoffs.

Read the series
  1. 01Building the cloud behind my projectsA small Hetzner Kubernetes platform with shared services, repeatable deployments, and explicit operational tradeoffs.3 min
  2. 02Two network planes, two different responsibilitiesWhy WireGuard protects cluster administration while NetBird connects applications and agent tools.3 min
  3. 03Self-hosting Temporal and putting it to workThe infrastructure integration and application workflows behind our self-hosted Temporal deployment.3 min
  4. 04When every small app brings its own connection poolThe shared Postgres limit, the rollout that reduced idle connections, and why a green dashboard is only one kind of evidence.3 min