Public Tools

We build tools for clients. Some of those tools solve problems that go beyond a single organization. When they do, we open them up.

Our public tools aren't side projects. They're generalized from real use, born from actual engagements, tested in operational environments, then made available to the institutions and communities that need them.

This is how we practice what we preach: impact funded by profit, not charity.

Tools

Partijplein

partijplein.nl

ZonOpJeBakkes

zonopjebakkes.nl

Rechtlerzer

rechtlezer.nl

Fluenta

getfluenta.com

How client work becomes public tools

Not every client project produces a public tool. But the pattern is consistent:

We build for a specific client and context.

A pipeline, a framework, a component, designed to solve a real problem in a real organization.

We recognize what's reusable.

Some solutions address challenges that many institutions share, but that no one has built open infrastructure for.

We generalize and release.

We strip out client-specific logic, document thoroughly, and publish. The tool becomes shared infrastructure.

The result: Public tools grounded in reality, not built on assumptions about what institutions might need.

What's coming

We're currently working on tools in the following areas:

Open frameworks for institutional AI governance
Reusable data pipelines for public health data
Training materials for AI literacy in public institutions

Why we do this

The institutions working on society's hardest problems often have the smallest technology budgets. Open tools help level that playing field, not with charity, but with infrastructure that works because it was built from real use.

Every tool on this page exists because a client engagement surfaced a problem worth solving for everyone.

Want to collaborate?

If you're building in the public interest and think our tools could help — or if you want to contribute — we'd love to hear from you.