About
Infrastructure Engineers Building Real Systems.
We design, build and hand over production infrastructure for AI platforms, blockchain systems and cloud-native applications. The systems on this site are ones we run, not slideware.
Mission
Make infrastructure boring again.
Most infrastructure problems are not exotic. They are the accumulated cost of decisions that were reasonable in isolation: a load balancer that cannot see the protocol it balances, a Terraform state that grew into a single blast radius, an observability stack that produces dashboards nobody opens.
Our job is to make those systems predictable, legible and cheap to change — and then to leave, having documented why every part is the way it is.
Core expertise
What we are asked for
The disciplines the work actually falls into. The three that are also service pillars link through to how we approach them.
- Platform Engineering
- Cloud Architecture
- Infrastructure as Code
- CI/CD Engineering
- Kubernetes Platforms
- High Availability Systems
- Performance Engineering
- Infrastructure Scalability
- Infrastructure Modernization
- AI Infrastructure
- LLM Infrastructure
- AI Agent Infrastructure
- GPU Infrastructure
- AI Routing
- AI Platform Engineering
- Model Serving Infrastructure
- MCP Infrastructure
- Blockchain Infrastructure
- Ethereum Infrastructure
- RPC Infrastructure
- Blockchain Node Operations
- High-Performance RPC Routing
- Archive Node Management
- Blockchain Observability
- Reliability
- Site Reliability Engineering
- Disaster Recovery
- Capacity Planning
- Incident Response
- Observability Engineering
- Monitoring & Alerting
- Distributed Systems
- Security
- DevSecOps
- Infrastructure Security
- Supply Chain Security
- Secrets Management
- Compliance Automation
- Networking
- Traffic Engineering
- Layer 4 / Layer 7 Load Balancing
- Reverse Proxy Architecture
- Zero-Downtime Deployments
- Edge Infrastructure
- Automation
- Infrastructure Automation
- Configuration Management
- Workflow Automation
- Release Automation
- Platform Tooling
Philosophy
How we work
Six principles that decide most arguments before they start.
Engineering first
We are engineers who consult, not consultants who subcontract engineering. The person who designs your system is the person who writes it.
Automation by default
If a change can be made by clicking, it will eventually be made by clicking at 3am by someone guessing. Infrastructure belongs in version control and is applied by machines.
Reliability over hype
A consistent 30 tok/s beats a spiky 45. Predictability is what everything downstream is built on, and it is usually what people mean when they ask for speed.
Production-grade quality
Health checks, metrics, failure handling and runbooks are part of the deliverable, not a follow-up phase that never gets scheduled.
Open-source mindset
We build on open source, contribute where we can, and write internal systems as though someone else will read them — because someone will.
Long-term maintainability
The measure of an engagement is whether your team can change the system confidently six months after we leave.
Open source
What we give back
Infrastructure MCP is MIT-licensed and public: a self-hosted Model Context Protocol server that gives AI agents audited access to real infrastructure instead of raw SSH.
Other systems described on this site run on private infrastructure and are not published. We still document how they work, because the engineering reasoning is the transferable part.
Technology
What we actually use
Not a list of everything we have heard of — this is the set we work in regularly.
- Cloud & virtualisation
- AWS
- OpenStack
- VMware
- Infrastructure as code
- Terraform
- Terragrunt
- Ansible
- Packer
- Delivery
- GitHub Actions
- FluxCD
- Runtime & traffic
- Docker
- k3s
- HAProxy
- Observability
- OpenTelemetry
- Prometheus
- Grafana
- Loki
- Tempo
- Languages & systems
- Go
- Python
- Bash
- Linux
Let's talk about your infrastructure.
Or email us directly at hello@holits.com.