An infrastructure portfolio. A foundation to build on.

The portfolio includes virtual infrastructure, monitoring, scheduled operations, client web hosting, and SIP telephony. Many services use Zero Trust access. The experience pages describe professional work; the technical practice page sets out the engineering principles.

The ambition: an open-source company.

An infrastructure company could help organizations run their systems with more control over the software, access, and recovery process. What it would offer is still undecided; the current work is a starting point, not a promise of future services.

01

Open source first.

Build on open-source software, credit the projects behind it, and contribute improvements where possible. Independence still comes with a responsibility to those communities.

02

Privacy by design.

Decide who can access systems and how data is handled before building them. Grant only the permissions needed and make responsibility for that data clear.

03

Security as a discipline.

Work within explicit permission, reduce unnecessary exposure, and report vulnerabilities responsibly. Security should be part of the daily work, not a sales claim.

There is no product for sale, pricing, or delivery schedule. For now, the focus is on building and maintaining the systems that could support that ambition.