Neat Things I Do
Four things I do. One way I do them: honestly, thoroughly, and with code you can read. Whether you’re a government agency, a research institution, a foundation, or a development team — the approach is the same. I assess your situation, tell you what I actually think, and build something that works. No vendor lock-in, no black boxes, no surprises.
1. Free Software for Public Good
Governments, foundations, and research institutions deserve infrastructure they can inspect, audit, and modify. I build it with GPL-licensed tools — not because the client asked, but because it’s the right thing to do.
What this looks like in practice:
- Puppet-managed infrastructure with fully auditable manifests
- Open-source alternatives to proprietary platforms — evaluated honestly, not sold to you
- Documentation that stays with the organisation, not the consultant
- Handovers that leave you genuinely independent
2. The Right Tool for the Right Job
Puppet for configuration management and compliance. Ansible for automation. Containers for ephemeral workloads. Every problem deserves its own solution — neatly applied.
What this looks like in practice:
- A technology selection process grounded in your actual requirements, not my preferred stack
- Puppet for deterministic, auditable state management across fleets
- Ansible for workflow automation, provisioning, and one-shot tasks
- Container strategies that match your operational maturity — not over-engineered for the sake of it
- Honest assessment of what you already have and whether it’s worth keeping
3. We Watch. We Fix. You Sleep.
Self-hosted monitoring and alerting — Zabbix, Prometheus, and Grafana, running on your infrastructure, under your control.
What this looks like in practice:
- Monitoring stacks deployed on your hardware, in your network — no data sent to third parties
- Alert routing that reaches the right person at the right time
- Dashboards built for operators, not for slide decks
- Runbooks and escalation procedures that survive staff turnover
- Ongoing support — I stay in the picture when things go sideways
4. Neatly Innovative AI
I believe AI should earn trust, not demand it. Rosett-AI leads the way — with more tools coming. Governance, transparency, and confidence for AI-assisted development, all open-source.
What this looks like in practice:
- AI tooling assessed for your actual use case — not whatever the vendor is pushing this quarter
- Rosett-AI integration for development teams that want governance built in from the start
- Transparent AI workflows: what the model does, what it doesn’t, where the human stays in the loop
- Open-source by default — you can read every line of the tools I build
How an Engagement Works
- We talk. You tell me about your situation. I ask questions — probably more than you expected. No charge for the initial conversation.
- I assess. I look at what you have, what you need, and what’s realistic. If I think you’re solving the wrong problem, I’ll say so before you’ve spent a euro.
- I propose. A clear scope, a realistic timeline, and a fixed engagement structure. No open-ended retainers.
- I build. At your table or from mine — but always in direct communication with you.
- I hand over. Everything I build, you own. GPL-3.0-only for software, CC BY-SA 4.0 for documentation. Full knowledge transfer.
What you won’t get
- A 40-page slide deck before any real work starts
- Surprise invoices for scope that wasn’t agreed
- Deliverables you can’t inspect, modify, or redistribute
- A consultant who vanishes after the contract ends
Step 1 starts with a conversation.