After SimpoLab closed, I carried on its spirit on my own infrastructure: a cloud VPS plus a few machines at home, connected by a private mesh VPN. It’s where I learn system administration and DevOps hands-on, and where my own projects live.

How it works

  • OS: Arch Linux (ARM) on the VPS, so everything is built for arm64
  • Containers, the declarative way: every service is a Podman container managed by systemd through Quadlet. No Kubernetes, no Docker Compose
  • GitOps: the configuration lives in a git repository, and what’s on the main branch is what runs. A small deploy tool I wrote applies each push, restarts only what changed, runs health checks, rolls back on failure and reports to Telegram
  • Updates: Renovate proposes image updates as pull requests, and merging one deploys it
  • CI/CD: self-hosted Woodpecker CI builds the images of my projects and pushes them to a private container registry (Zot)
  • Networking: Traefik as reverse proxy with Let’s Encrypt certificates, Authentik for single sign-on, and a NetBird mesh VPN between the VPS and the home machines
  • Secrets: encrypted in git with SOPS and age
  • Backups: nightly with restic

Services

Mail and DNS

  • a complete mail server with Mailu (Postfix, Dovecot, Rspamd, webmail) for my domains, continuing what I started in SimpoLab
  • authoritative and recursive DNS with Technitium, the successor of my old BIND setup

Development

Productivity and home

Web

My own projects

  • Moon: the volunteer management system of ESN Milano Statale, with production, staging and a public demo
  • Mailroom: a multi-user webmail-like app for mail filtering and organisation, with an MCP interface for AI assistants. Its filtering engine grew out of imap-thingy
  • SimpoDuck: a meta search engine with DuckDuckGo-style bangs
  • ContactsMCP: a self-hostable MCP server for Google Contacts, with multi-account read and write support
  • MCP servers that connect AI assistants to my messaging apps, including my fork of telegram-mcp