I work on the problems that show up once software has to run somewhere. A deployment breaks, a service slows down, an API behaves differently than expected, or a server needs to survive something its original setup never anticipated. I like figuring out what went wrong and fixing the underlying problem.

Most of my work involves Linux, Python, Docker and backend systems. I also build web applications, automation tools and software around multiplayer games.

• Linux infrastructure: VPS administration, containers, reverse proxies, backup and restore workflows, CI, monitoring and production troubleshooting.
• Web platforms and automation: publishing systems, operational dashboards, bots, API integrations and internal tools.
• Game servers: operating Minecraft and Rust environments, dealing with performance, configuration, plugins and service reliability.

Some of these systems are private or tied to specific projects, so their source code isn't here. The public projects and contributions below are easier to inspect.

Wisp MCP lets MCP-compatible clients interact with WISP game panels. It's a Python integration covering server resources, files, console commands, backups and database operations, with permissions for sensitive actions. The code is public under the PolyForm Noncommercial license.

A few upstream changes I've contributed:

• LinuxGSM: support for Debian's deb822 APT source files.
• Neovide: hardening Neovim restart handling.
• tailcat: use SFTP when SCP supports it.

I'm interested in good ideas, especially when there's a difficult technical problem to untangle. I'm happy to review an approach, share a second opinion or contribute a fix to a project I find worthwhile, even when there's no paid work involved.

For infrastructure work, backend integrations or agency subcontracting, find me at vitrine.bar.