Projects
GitOps, HA databases, reverse proxy, tunnels, and self-hosted services in production
Network fabric between internal and external clusters
Dedicated tunnels so private networks and remote clusters reach each other — without publishing every service on the public internet.
A custom cluster from scratch — no packaged platform
Control plane, node agent, process runtime, scheduler, and networking written in-house — every layer is code you can read, not a black-box orchestrator.
Scalable non-relational database with failover
A document store that stays online when a node dies — multiple replicas, automatic failover, and load balancing across the cluster.
Self-hosted app backend
Auth, database, storage, and APIs on your own infrastructure — a private backend platform instead of a public BaaS.
AI automation for support and back-office work
Customer answers and staff workflows that run themselves — conversation and process on your infrastructure, not a rented chatbot.
Organizational chat inside the applications
Real-time rooms injected into the products people already use — messages stay on your document cluster, not in a public messenger.
Scalable enterprise file sharing
Private file sync and collaboration on your own infrastructure — full control over data, cost, and compliance without depending on a public cloud.
One pipeline for dozens of enterprise apps
Shared build, test, and deploy templates so a new app or environment does not mean redesigning CI/CD from scratch.
Self-hosted organizational email
Send and receive mail on your own infrastructure — control over identity, delivery, and data instead of a public mailbox provider.
Scalable reverse proxy for the whole cluster
One entry for HTTP and HTTPS — routing, TLS, and load balancing so every service is reachable without a public port per app.
High-availability relational database
Keep transactional data online when a node dies — replicas, automatic failover, and a connection pool in front of the cluster.
Role-separated infrastructure, steered by GitOps
Production, development, CI jobs, cluster, database, and backup on dedicated hosts — desired state in git, not on a snowflake server.
Real-time monitoring across a hundred services
One board for apps, APIs, and databases — know what is down before the customer does, without a custom check per team.
High-availability cache with automatic failover
Keep cache and sessions online when a node dies — automatic promotion instead of a single point of failure.