Cloud · DevOps · Enterprise AI Infrastructure

Cloud platforms, Kubernetes clusters, and private AI systems for availability-critical work.

Royal Technology is the engineering practice of a cloud and infrastructure engineer with more than a decade in enterprise IT. I move organizations to Azure without losing data, run Kubernetes the way production demands, and get large language models serving fast on hardware you own.

15+organizations migrated to Azure
500TB+moved with zero data loss
75%+Azure footprint cut in one audit
24/7Talos Linux cluster in production

About

Daniel King, infrastructure engineer

I'm Daniel King, an infrastructure engineer focused on machine learning, hyper-converged infrastructure, distributed systems, and automation. I enjoy building the declarative, scalable, and secure systems your business needs to operate.

Based in Jackson, Mississippi. Cloud engagements run nationwide; hardware work is limited to Mississippi and the immediately surrounding states.

Capabilities

Every change goes into version control first, gets measured before and after, and ships behind tests written before the code.

Cloud platforms and DevOps

Design, migration, and operation of cloud environments, with the automation to keep them reproducible.

  • Azure IaaS/PaaS architecture and organization-wide migrations, from planning through cutover
  • Terraform and OpenTofu modules for multi-tenant infrastructure under version control
  • Azure DevOps and GitHub Actions pipelines for hands-off releases
  • Entra ID and Microsoft 365: identity, conditional access, and Intune at fleet scale
  • Azure FinOps reviews that find waste; one audit cut a client's footprint by 75%+
  • Azure Virtual Desktop with FSLogix profiles and hosts that scale to zero after hours

Kubernetes and platform engineering

A Talos Linux cluster runs around the clock as the proving ground for everything that ships to clients.

  • Immutable Talos Linux nodes, Flux GitOps, and Flagger canary rollouts
  • Istio service mesh with mTLS over Cilium, zero anonymous routes
  • LINSTOR and ZFS distributed storage; CloudNativePG with failover and WAL archiving
  • Velero backups to S3, External Secrets Operator, and Bitwarden Secrets Manager
  • Kyverno policies, Falco runtime detection, and Trivy image scanning
  • LGTM observability: Loki, Grafana, Tempo, and Mimir with alert routing

Local AI inference and optimization

Enterprise-grade language model serving on your own hardware, so sensitive data never leaves the building.

  • Models quantized to W4A16 AWQ and served with SGLang
  • Tensor parallelism and variable context lengths, scaled to what your hardware allows
  • MTP/NEXTN speculative decoding and context-pool tuning, gains up to 30% in single-stream throughput
  • Benchmarks before and after every change; long-context configs probed past 90% load before shipping
  • GPU power capping tuned per deployment to minimize power draw and heat with minimal impact on inference speed
  • Centralized self-hosted API gateway: per-user keys, spending caps, and token-level tracing. Adds RBAC and centralized logging across all usage and access
  • Speech-to-speech stacks on pipecat with Silero VAD and on-prem ASR
  • Guardrails on every request path, at both the gateway and model level
  • Fine-tuning on distilled, curated datasets; adapters gated on holdout tests written first

Selected work

Clients have ranged across healthcare, government, financial services, real estate and title work, and industrial distribution. Who they are, and how their environments are built, stays confidential; several operate under regulatory and contractual obligations that require it.

Cloud migrations without data loss

15+ organizations moved to Azure IaaS/PaaS with 500TB+ of data delivered intact. The largest single migration moved 30TB, and every runbook stayed in the client team's hands.

Virtual desktop platforms

VDI pools with role-based least-privilege access, roaming user profiles on managed file storage, and session hosts that scale to zero when idle. Compute cost drops to nothing outside working hours.

Hybrid data integration

Self-hosted integration runtimes feeding on-prem operational databases into cloud analytics. Every pipeline definition lives under version control, so connection changes are reviewable.

Endpoint management at fleet scale

Policy design and onboarding automation across thousands of endpoints on macOS, Windows, and Linux for 100+ clients.

Identity isolation at 100+ tenant scale

Tenant separation, scoped administrative units that cap blast radius, and hybrid identity sync with cloud-based single sign-on across multi-organization estates.

Security and cost audits

I have found exposed remote-management paths in client estates, locked them down, and redesigned the environments around least privilege. One audit cut cloud footprint by 75%+ and took thousands off the monthly bill.

Case studies

Four engagements, described from the work itself.

30TB electronic health records migration to Azure

Situation. A client's entire EHR platform had to move off on-premises infrastructure into a new Azure region: 30TB of live healthcare data, where data loss was not an option.

Approach. I migrated the estate with a mix of image-level, SQL, and file-level backups, moving data over SFTP and image restores into the new region. Cutover was phased, with validation gates between phases.

Result. All 30TB landed in Azure with zero data loss, verified by SHA256 checksum comparison, phased cutover validation, and post-migration audits plus smoke testing of system functionality.

Handover. The client team kept the full cutover and rollback runbooks.

Local LLM serving: W4A16 AWQ on SGLang

Situation. Large-model inference on owned hardware where the data stays in-house, at context lengths and concurrency consumer-grade setups cannot reach.

Approach. I quantized the model to W4A16 AWQ and served it with SGLang, running tensor parallelism across an NVLink-paired dual-GPU rig with weights and KV state split across cards. MTP/NEXTN speculative decoding and context-pool sizing were tuned under concurrent load. Benchmarks ran before and after every change, and long-context configurations were probed past 90% of the target window before anything shipped.

Result. +30% single-stream throughput from speculative decoding, with 96k-token parallel contexts coexisting with a realtime audio stack on the same GPUs.

Handover. The benchmark-first methodology is documented and repeats on every model-serving deployment I build.

75%+ Azure footprint reduction

Situation. An estate audit requested by the client's security leadership surfaced unrestricted RDP reach into every VM, and a cloud bill that looked wrong.

Findings. Not one resource carried a cost-saving reservation. Numerous resources sat idle, and several were completely unneeded: compute, storage, public IPs, VPN gateways.

Approach. RDP was locked down to the client's own addresses, then I redesigned the environment and cut over to it completely, data and endpoints included. Several months end to end.

Result. Azure footprint reduced 75%+ and monthly billing down by thousands of dollars.

Handover. Cost and security reviews are now a standing part of how I maintain client estates.

Scale-to-zero Azure Virtual Desktop

Situation. A financial-services client needed tightly controlled access to internal records without paying for idle session hosts.

Approach. A three-host Azure Virtual Desktop pool: RBAC decides who reaches what, FSLogix roams profiles on Azure Files, and host VMs scale to zero outside working hours.

Result. Compute spend for the pool dropped by roughly $900 a month. Users reported the environment performed far better than its predecessor: more responsive, user friendly, and cost effective.

Handover. Built entirely from managed Azure services with the configuration documented, so the client team operates it day to day.

How engagements work

Scope is agreed up front, work lands in your repos, and you keep the runbooks.

Fractional platform engineering

Architecture, deployment, and operations for Azure estates and Kubernetes clusters, owned end to end.

Migration delivery

Cloud, identity, and email migrations, with documentation your team can keep and reuse.

AI infrastructure

Assessment, buildout, and tuning of on-premises LLM serving, from GPU selection through serving benchmarks.

Every engagement ships with documentation. If any of these sound like a gap you're trying to close or a problem you need to solve, please get in touch via the form below.

Contact

Tell me what you're working on and I'll get back to you by email.