Technology projects built because I wanted something better.

Where the name came from

Smurftech grew out of a long-standing nickname tied to blue hair and an equally long-standing interest in technology. The name stuck; the focus is still the same: understand how something works, improve it, or build the version I wish already existed.

What I build

The projects here are deliberately varied. A small utility that fixes an annoying Linux workflow belongs beside a larger desktop application, hardware controller or automation system if each solves a real problem.

I tend to build around the tools and platforms I actually use, particularly Linux, open-source software, self-hosted services and practical integrations between devices and systems.

How I approach projects

The goal is useful software rather than complexity for its own sake. I prefer clear architecture, maintainable components and the freedom to replace one part of a system without rebuilding everything around it.

Projects usually start as personal tools. If one becomes useful enough to share publicly, Smurftech provides a stable home for releases, documentation and installation information while the project itself keeps its own repository and identity.

The lab keeps growing

SmurfDeck and SmurfPanel are the first projects being brought under the public Smurftech identity. More will follow as existing experiments mature and new problems seem worth solving.