Expertise

DevOps & Infrastructure

I ship and operate what I build — pipelines, servers, containers, and the monitoring that proves it works.

I'm not a dedicated DevOps engineer and I don't present myself as one. I'm a backend engineer and architect who has spent twenty years staying responsible for what happens after the merge: provisioning VPS boxes by hand, tuning Nginx in front of production traffic, moving projects onto container-based deploys, and standing up monitoring that makes a problem visible before a user reports it. I'd argue that makes me a better architect rather than a second-rate SRE — when I design a system, I already know how it will be deployed, what it will cost to run, and which parts will be unpleasant to operate.

Evidence

What that looked like in practice

Deployment automation across ecosystems

Shipped production applications through Kamal, Capistrano, Mina, Gigalixir, Fly.io, and Heroku, alongside container-based deploys built on Docker, docker-compose, and private registries.

Servers and web tier

Provisioned and configured Ubuntu and Debian VDS/VPS environments by hand, and tuned Nginx and Apache for production: routing, caching, and performance. AWS EC2 and S3 where managed infrastructure was the better fit — including the GPU instances behind the LLM inference work.

CI/CD adoption

Introduced and maintained pipelines on GitHub Actions and GitLab CI, moving teams off manual release steps onto automated, repeatable delivery.

Observability and error tracking

Deployed and operated Prometheus, Grafana, Grafana Alloy, and Zabbix for infrastructure and application monitoring and integrated Sentry, Rollbar, and Bugsnag so failures arrive with context instead of as user complaints.

Tools & practices

Docker docker-compose Kamal Capistrano Fly.io Heroku Gigalixir GitHub Actions GitLab CI Nginx Apache AWS EC2/S3 Prometheus Grafana Zabbix Sentry Ubuntu / Debian

Where this came from

Awaken Protocol (2024–present)
Easy8 Software (2020–2024)
Agency & contract era (2010–2020)

Full work history

Contact

Want the detail behind any of this?

Happy to talk through the specifics — what worked, what didn't, and what I'd do differently.

panov.eduard.k@gmail.com