Wibenson.com

DevSecOps, day to day. Container workloads that reschedule themselves, infrastructure declared in code and reviewed before it ships, relational databases carrying data someone would miss, and enough telemetry to know what broke before a ticket arrives.

Security and ISO 27001 compliance are part of the work, not a separate project. Running a cloud ops team mostly means unblocking other people before they get stuck.

• Container orchestration
• Infrastructure as code
• Database operations
• Observability
• Incident response
• ISO 27001

Scope

Production

On call

Yes, the real kind

SLA

Contractual

A handful of Linux boxes stitched together over a private mesh network, self-hosting more than they reasonably should: the blog, DNS filtering for the whole house, and a memory service so my agents remember what we did last week.

Permanently degraded. That is not a bug report, that is the operating model.

• Linux
• Mesh networking
• Self-hosting
• DNS filtering
• Service uptime

Scope

Everything personal

On call

Also me

SLA

None, obviously

Coding agents and a setup of my own, pointed at real operational work instead of demos. They handle the parts I would otherwise forget, which is a long list.

Supervised. Mostly. The memory service exists because I do not trust my own recall either.

• Agent workflows
• Ops automation
• Context and memory
• Human review

Scope

Real ops tasks

On call

Supervised

SLA

Improving