Support the Work
Most of what I build ships the same way: open source, self-hosted, and yours the moment you have it. No account, no login wall, nothing held back for a paid tier.
Atelier is an AI-native CMS you run by talking to it — create, find, update and publish content through an operator console instead of admin forms. GPL-2.0-or-later, built on Drupal, shipped as a signed container you install on your own machine. You keep the content, the server, and your own AI keys.
FlowDrop is a visual workflow editor for Svelte — MIT-licensed, on npm, and built to get you a workflow editor in minutes rather than months. It’s a pure editor by design: you bring the backend, so your data and your orchestration stay yours. The Drupal module suite that wires it into Drupal is GPL, on drupal.org.
Behind both is a long tail of Drupal contribution work going back to Storm and Drupal PM.
And this blog. No ads, no tracking scripts, no newsletter wall, no “sign in to continue” — see the privacy policy for exactly how little it collects.
In a world where everything interesting hides behind a login, I’d like this to feel different. Keeping it that way is funded by evenings.
There are two ways to chip in. GitHub Sponsors is a small monthly amount — the more useful of the two, because steady beats spiky when you’re deciding whether to keep maintaining something. Buy Me a Coffee is a one-off, for when a specific post or fix earned it.
Back the work behind the writing
These posts come out of building things in the open — Atelier, FlowDrop, and a long tail of Drupal contributions. Free to use, self-hosted, and yours to run. If any of it saved you time, you can help keep it going.
What it goes toward
- Keeping things online and free — domains, hosting, registries, the boring recurring bills behind the projects and this archive.
- Time on the unglamorous parts — issue triage, upgrade paths, release engineering, documentation. The install that just works is most of the work and none of the fun.
- Tools and experiments — licences, test hardware, model credits and throwaway accounts behind the posts and features that involve actually trying things.
Other ways to help
Money is the least interesting option, honestly. These help just as much:
- Run it and tell me where it broke. A good bug report is worth more than a coffee — Atelier’s issue queue for the CMS, drupal.org for the FlowDrop Drupal modules.
- Tell me where the docs lost you. The gap between “it works” and “a stranger can install it” is documentation, and I’m too close to it to see the gaps.
- Share a post, or a project, with someone it would help.
- If you write, link back. The open web runs on people bothering to link.
The fine print
Payments are handled entirely by third parties — GitHub Sponsors or Buy Me a Coffee. Nothing on this page contacts either of them until you click through: there is no embedded widget, no sponsor button iframe, and no script loaded from their servers. Once you follow a link you are on their site, under their own privacy policy and terms, and I never see your card details.
Support is a gift, not a purchase — including the recurring kind. It buys no support contract, no priority on your issue, and no influence over a roadmap — the projects stay open and the queue stays fair, which is rather the point. A GitHub sponsorship can be cancelled any time from your own settings, and there is no invoice by default; if you need one for accounting, email me and we’ll sort it out.
Commercial work is a separate thing entirely, and doesn’t run through this page. If your organisation needs customization, integration or guarantees built on top of these projects, that goes through the companies behind them — Factorial GmbH for the FlowDrop and Drupal side, AIncient Labs for Atelier. It’s work shaped to a specific client on top of the open source, never a feature carved out of it: that funds the free product, it never shrinks it. Happy to point you the right way — the address is in the imprint.