Solutions
Below are the solution types we actually sell, described with their limits. The projects underneath are real builds from our own and our partners' repositories — named, dated, and linked where the code is public.
Solution types
We connect the systems you already pay for, automate the re-keying between them, and leave you a measured before and after. Nothing new to buy, nothing new to learn: the deliverable is the pipe and the number that proves it.
A small real build that settles the one thing you cannot decide by reading a vendor deck. It runs on your own data or on a representative sample, it is measured, and it is deliberately short enough to fail cheaply.
Short sessions for your staff or your clients, plus the measurement framework that lets them prove an automation gain themselves — the one that survives a board meeting without us in the room.
Deployment, updates, backups and monitoring on infrastructure inside the Union, behind Cloudflare. We take the on-call rotation, publish the abuse channel with its 72-hour first-response commitment, and write down the retention limits.
Builds
Five Rust crates and services behind citizen-science compute funding: a provider comparator that ranks offers by price, CPU, GPU and grid carbon intensity, and a telemetry service that turns container heartbeats and donated computing hours into a public feed. The design constraint that shaped everything: no personal data is collected, so there is nothing to leak and nothing to redact.
A Go service over PostgreSQL with PostGIS, fronted by a React and deck.gl map that turns public datasets into something a municipality can argue with. The rule that matters: the whole repository is auditable, and any deployment that removes the attribution notice is a licence violation rather than a matter of preference.
The Epson Perfection 3170 speaks a proprietary protocol that needs a 32-bit interpreter stack, while every modern app is 64-bit. We packaged the bridge — old library shim, systemd unit, firmware blob — into an amd64 package and verified it on Ubuntu 26.04. Small work, concrete outcome: a scanner that works again.
Contact requests, data subject requests and abuse reports go to three webhooks on a server we run in the Union, each tagged with the page, the language and the timestamp. If the server is down the form says so and keeps your text in the page instead of losing it.
This site, built as its own case study. Day mode is an offset-print grammar — screened paper, misregistered ink, hard shadows. Night mode runs Conway's cellular automaton on a full-window canvas, with the colour of a cell encoding its age and the brightness of the three lamps driven by the live population of the grid. Six languages, no cookie, and a contrast budget measured rather than guessed.
How we work
Four steps, written down before the work starts, and the same four steps whether the project is a four-week pilot or a two-year platform.
One workshop, three questions: which task is repeated, how many people pay for it, and what a good result looks like. The answer becomes the number we will try to move.
Processing time, error rate, cost per operation. Without a baseline there is no result, only an impression — so the baseline comes first, even when it is inconvenient.
A pipeline or a pilot, on infrastructure inside the European Union, with the human decision kept in the loop. If it needs a proprietary platform to run, it is the wrong design.
Same indicators, same method. You get the code, the runbook and the rights to present the result without us. If the gain is small, we say so in writing.
Pipelines
These are the diagrams of pipelines built for real clients and for our own projects. Hover a block to see the tool behind it; open the details for the reasoning. The Mermaid source for each one is on the site, so you can read the pipeline rather than take a picture of it.
SourcesRSS/Atom · SearXNG · RSSHub
A real feed where one exists, a self-hosted metasearch where it does not; we don't pay an aggregator for what can be read directly.
Read & extractn8n
The page is fetched, the noise stripped and clean text exported. Nothing is paraphrased before it is stored.
Agent on cronLiteLLM · Tela wiki
A scheduled agent reads the day's new material and ranks it, grounded in the wiki so it reuses what we already validated.
Wiki + memoryTela · OpenViking
The approved sources and the subject pages live in the wiki; the durable memory of what we already concluded lives beside it.
Human gate 1
The candidates are posted as a numbered list and people choose. This is where taste lives.
Deep researchAgent, per subject
Only the chosen subjects get a full treatment, with sources and citations, and a page each.
Human gate 2
If the material is thin the loop restarts and we keep searching. Nothing is published on a first pass.
Episode + notesAI draft, humans sign off
The agent drafts the show notes and the presentation; the hosts rewrite and speak.
This pipeline is only as good as the sources that exist and are read carefully. We cannot invent primary research we do not have.
Discovery & setup — 2 weeks
Feed and source list, one cron, one pick channel, wiki structure, handover doc.
The graph, the lane names and the two human gates are one plain-text file you can read, fork and re-render yourself.
Invoices & expensesOdoo
Your documents are captured where they already are, rather than re-keyed into a second tool.
Workflow enginen8n · Windmill
Usually n8n; Windmill when a longer-running, versioned Python job is needed. The engine follows the task, not the habit.
Match & reconcileOdoo
Payments matched to invoices, discrepancies surfaced instead of buried.
LedgerOdoo
The single book of record. Everything downstream reads from here.
ObligationsScheduled actions
Recurring reporting and filings are generated and dated. Every deadline has a named owner.
Watch for changen8n fetch
A scheduled check of official legal sources and of your providers' legal documents — bank, cloud, accounting software.
Agent on cronLiteLLM
The documents are diffed against the stored version and the agent judges whether the change matters to you.
Alert the right personMatrix · Teams · email
The finding goes to whoever owns that obligation; if they are out of office it goes to their cover, so nothing waits on a holiday.
Accountant signs offHuman
We automate the gathering and the watching; a human books and signs.
We do not file anything without a human signature. Automated filing is a legal risk we will not take on your behalf.
One workflow pilot — 2 to 3 weeks
A single document flow end to end, in your own Odoo, on your own server, with the handover doc.
The whole document chain is the file. Change a provider, add a jurisdiction, and the diagram follows.
Your constraints
Residency, scale, budget, skills. The entry node is your situation, not the size of a logo.
Where does it run?
Each fork has a default we say out loud, and the condition that would make us move.
Dedicated serverHetzner · OVH
Cheapest per unit of steady load, one operator to reason about, less elasticity.
VPSHetzner · OVH · Hostinger
Right for small teams and bursty work. The usual starting point.
World cloudAWS · Azure · GCP
When users are global or load is genuinely elastic. Most expensive per unit, and the lock-in risk is real.
Source & CIGitLab CE · Gitea · Jenkins
Git and CI only when they earn their place. A forge without backups is a single point of failure.
Test before it shipsCI pipeline
Automated tests on every change, staging, a restore drill and a load check. This is the node most providers skip.
DeployDokploy Solo → Swarm → K3s
One service, then several, then a platform only when a service genuinely needs it.
Edge & securityCloudflare · Kong
A WAF in front, a gateway behind it, and Open-appsec or CrowdSec for the app-level attacks a WAF does not catch.
AccessCassdoor · Keycloak
Single sign-on and per-service permissions, so leaving is a config change rather than a migration.
BackupsMixed EU + global
Copies across mixed providers so one provider failure is not your outage; retention and residency follow the law that applies.
Mail & officeEU-hosted
Email in a GDPR-clean, auditable place. This is a legal obligation, not a preference.
HandoverDocs + training
A documented system, a walkthrough and training, so maintenance never depended on us being reachable.
You own it
Documented, self-hostable, maintained by you after we go.
We do not sell Kubernetes to a five-person company, and we do not run black-box SaaS-only integrations you cannot leave.
Architecture review — 1 week
Your constraints, three honest options with prices, a recommendation, and the risk written down.
Every fork on this diagram is a decision, not a preference. The file records both the choice and the condition that would change it.
Reflect
The need, the buyer and the regulation the product falls under — checked before the first sketch, not after the first batch.
Design
Form, material, and the one property a competitor cannot copy easily.
Prototype toolsJig · fixture · mould
The dedicated tool that makes the difference repeatable. This is where the margin is protected.
Connected hardwareESP32 · Raspberry Pi
Only when the product genuinely needs to sense or report. No gadgetry for its own sake.
Make & shipSmall series first
A first series tested in real conditions before anyone talks about volume.
Use & measureReturns · waste
What actually happens to the product, including what comes back. Measured, then fed back.
Accounting & complianceThe patterns above
Sales, costs and obligations flow straight into the accounting and compliance patterns, already automated.
We do not start a physical product before the compliance question is answered. A beautiful object with the wrong certification is a liability.
Feasibility & compliance — 3 weeks
The regulation map, a first prototype plan and a realistic costed path to market.
The loop is a file, not a slide. Fork it for your own product and the compliance step stays visible at every revision.