Linux servers
Provisioning, hardening and maintaining Ubuntu and Debian boxes. Web servers, PHP-FPM pools, MySQL, Redis, queues, backups, log rotation, ... The unglamorous half is the half that decides whether a server survives its third year.
Sheet 02 ยท Process line
The consultancy isn't a separate skill set. It's the same servers, the same framework and the same pager, pointed at your stack instead of mine.
Stations 01 to 06
Provisioning, hardening and maintaining Ubuntu and Debian boxes. Web servers, PHP-FPM pools, MySQL, Redis, queues, backups, log rotation, ... The unglamorous half is the half that decides whether a server survives its third year.
Building Laravel applications, and dragging old ones forward. If you're stuck three major versions behind because nobody wants to touch it, that's a job I've done more than once. Tests, static analysis and CI come with it, they aren't a line item.
Zone design, migrations between providers, DNSSEC, certificate automation, and the SPF, DKIM and DMARC records that decide whether your mail lands in an inbox or a spam folder. I ran a DNS monitoring service for five years, so this is home turf.
Uptime, certificate expiry, broken links, cron jobs that stopped running without telling anyone. The hard part isn't collecting the data, it's deciding what deserves to wake someone up. An alert everyone ignores is worse than no alert.
Finding out why a page takes four seconds. Query profiling, caching layers, Varnish, HTTP/2 and HTTP/3, CDN configuration, and load testing before a launch rather than during it.
Reviewing an app and its servers for the boring failure modes that actually get sites defaced: outdated packages, a database bound to 0.0.0.0, missing rate limits, a forgotten staging box. And when it already went wrong, working out what happened and closing it.
Operating procedure
If it turns out somebody else is a better fit, you hear that on the call rather than three invoices later. I'd rather lose the work than take a job I'm the wrong person for.
Billed in euro, 30 day terms. I work remotely from Belgium and I'm happy to be on site around Antwerp when a project genuinely needs it, which is less often than people expect.
Server changes land as committed configuration, not as a shell session nobody recorded, and the repository is yours when we're done. Nothing I build should need me to keep it alive.
Bill of materials
It's a boring list on purpose. I reach for something exotic when the boring option genuinely runs out, and not a moment before.
Mail mattias@robotstudios.be with what you're running and what's going wrong. You'll get a straight answer on whether I'm the right person for it.