Open Source
Infrastructure and plugins we needed for client work and could not find, published under our own name so anyone can run them. Free, and not a trial for something else.
5 repositories · Go, TypeScript, PHP · github.com/webloomlabs
Self-hosted uptime monitoring and status pages
Watches websites, servers, and services, tells you when they break, and shows your customers a status page that says so. One Docker container, no database server to set up.
A form backend for static sites that does not lose enquiries
Takes form submissions from static sites, commits them to Postgres before acknowledging, then delivers the email alert from a retrying queue — so a failed notification is visible and replayable rather than silent.
A TypeScript client for the WordPress REST API
Framework-agnostic, with zero runtime dependencies in the core and an optional Next.js cache adapter. Handles the parts of the WordPress REST API that everyone re-implements badly: pagination, relations, and cache keys.
A product features catalogue for Medusa v2
Adds the icon-title-subtitle list most product pages need — managed once as a global catalogue, assigned and ordered per product, and read by the storefront through a public store route.
A WooCommerce category tree that maintains itself
Drop one placeholder into a WordPress menu and it expands on render into the live WooCommerce product-category hierarchy — so adding a category never means re-editing the navigation.
Everything else we publish, including the work still finding its shape, is on GitHub.
github.com/webloomlabsHow we work in the open
Open sourcing something is a maintenance commitment, so we only publish what we are already running. That is the filter, and it is why this list is short.
A repository nobody can legally use is a portfolio piece, not open source. Ours ship with a licence, an install guide, and the caveats stated up front.
What is missing is written down next to what works, so you can rule something out before installing it rather than after.
Every one of these exists because a project needed it. They are maintained because we are still running them.
Work with us
Small enough to care about the details. Experienced enough to build the difficult parts. Tell us about the problem and we'll come back with a technical direction, scope, and timeline.
You work directly with the people building your product.
