Proxmox + ZFS Architecture
HA design, multi-site patterns, storage tuning, performance and capacity planning.
- Cluster health and upgrade strategy
- ZFS layout, tuning, scrubs, replication
- Backup/DR (PBS), recovery runbooks
I’m Adrian Jon Kriel. I help teams design, harden, and operate real infrastructure: Proxmox + ZFS clusters, cloud exit (moving away from hyperscalers), custom SaaS infrastructure, on-prem AI, DNS/email, automation, observability, and emergency recovery.
HA design, multi-site patterns, storage tuning, performance and capacity planning.
Kernel, I/O, network, and application tuning with measurable outcomes.
Web, proxy, DB, and platform improvements that cut cost, reduce risk, and raise uptime.
Turn “slow and fragile” into “fast and boring” with safe tuning, observability, and HA patterns.
Move away from the cloud safely — and run a custom SaaS platform with predictable cost and performance.
Authoritative + recursive DNS, deliverability, anti-spam, and continuity.
Build once, run forever: provisioning, hardening, lifecycle ops, runbooks.
When the solution needs hardware: ESP32/Arduino projects and custom automation workflows.
When it’s down, I get it back up — and make sure it stays up.
Build AI that actually works in production: on-prem or private cloud, with guardrails, audit trails, and zero “mystery box” dependencies. Ideal for US/EU teams that care about data residency, cost, and reliability.
Run modern LLM capabilities where your data lives — not the other way around.
Automation that executes, documents, and escalates — with human approval where needed.
Turn internal docs into an answer engine (without leaking private data).
This isn’t “buzzword consulting”. It’s the boring, production-grade stack I’ve used to build and operate clusters, hosting platforms, and custom SaaS infrastructure.
I specialize in the infrastructure behind stores that must stay online: performance tuning, scaling, hardening, migrations, and “it’s broken right now” recovery.
Speed, stability, and security for WooCommerce at scale.
Production operations that keep checkout fast and predictable.
Pragmatic ops and performance improvements for real-world stores.
If you want to see how I think, the repos and runbooks are public.
Sanitized examples of Proxmox VE / Proxmox Backup Server dashboards from real deployments (50+ clusters). Drop
images into assets/screenshots/ and update manifest.json.
Tip: export as PNG/WebP and blur/redact hostnames, IPs, and client names.
This is a sanitized timeline generated from private repositories (last 4 years), filtered for Proxmox, clusters, deployments, storage, databases, and related infra work.
Quick intake call, define the problem, align on outcomes, and get access safely.
Baseline, risks, bottlenecks, and “what breaks next” — documented and prioritized.
Hands-on fixes, automation, hardening, and monitoring. Changes are reversible and tracked.
Runbooks, diagrams, and clear next steps so your team isn’t dependent on me.
On-call, ongoing improvements, and “keep it boring” operations.
Email me and I’ll reply with available slots and next steps.
Email: admin@extremeshok.com
Send: a 2–3 sentence problem statement, your stack, urgency, and what “done” looks like.
$ printf "Need help: %s\n" "your problem here" | mail admin@extremeshok.com
Both. A short audit can produce a high-ROI plan, and we can then execute the top items.
Yes. I prefer least-privilege access, audit trails, and explicit scopes. You’ll get documentation, not mystery.
Neither. I build the right mix: on-prem, colocated, cloud, hybrid — whatever makes sense for cost, latency, and risk.
Yes. Retainers are ideal when you want stability, predictable improvements, and fast incident response.
No trackers. No ad pixels. No “growth hacks”. If you contact me, I only use your details to reply and deliver the work.
Privacy questions or deletion requests: admin@extremeshok.com.