Miguel Jacq · sysadmin & DevSecOps

Linux infrastructure for organisations where security, privacy, and reliability matter.

I'm Miguel Jacq. I help small and specialist teams run systems safely: untangling inherited Linux estates, automating change, hardening security, improving monitoring and recovery.

Security & privacy Infrastructure as code Monitoring & incident response Remote (UTC+10/11)

Working on production systems since 2007. Fully remote from Melbourne, Australia.

When to call Miguel

When I tend to be useful

The technology varies. The recurring theme is infrastructure that matters, has accumulated complexity, and needs experienced hands without a wholesale rewrite.

  • Production has become something nobody wants to touch.
  • Too much depends on one person's memory or undocumented "tribal knowledge".
  • Deployments are manual, fragile, or difficult to roll back.
  • Backups exist, but nobody is very confident about restoring them.
  • Security or compliance requirements have outgrown the current setup.
  • An incident exposed gaps in monitoring, access control, or recovery.
  • Sensitive data means the usual SaaS or outsourcing assumptions need more scrutiny.
  • A small team needs senior infrastructure depth without another full-time hire.
What the work looks like

Make important infrastructure less fragile.

More detail

Understand & stabilise

Map inherited systems, find the dangerous assumptions, fix the immediate risks, and make changes safer.

Automate & document

Turn snowflakes and manual procedures into reproducible configuration, pipelines, and playbooks.

Harden & control

Practical hardening, identity, encryption, secrets, logging, patching, and audit-friendly change.

Detect & recover

Monitoring that tells you what matters, backups you can restore, and recovery plans you can actually execute.

Good alignment

Mission matters to me, too.

I particularly value work with organisations concerned with security, privacy, human rights, civil society, public-interest technology, and open source. That isn't a requirement; it's simply where a lot of my work and interests have converged.

I also work with web agencies when the problem is a good fit. The common denominator is taking the systems, the risks, and the people affected by them seriously.

Embedding into existing ops teams
I normally join an existing organisation or technical team to solve infrastructure and operational problems. I don't intend to own the whole stack, resell you a platform, or turn every engagement into a rebuild.