Skip to content
Free to use, read, and build on

We build in the open

Most of what we build for clients starts as a real problem in a real business. When the solution is useful beyond one company, we generalize it and publish it. These are the apps, modules, plugins, and infrastructure we use every day, across Frappe and ERPNext, Odoo, WordPress, NixOS, and Jx. Read the code, use it, and send improvements back.

Browse on GitHub (opens in a new tab)Start a project

Built to work together

Some projects are designed to work together across platforms.

Cloudflare Email

Email for business systems without SMTP credentials, IMAP polling, or a separate mail provider. Outbound mail goes straight to Cloudflare Email Sending. Inbound mail is stored by a relay and pushed to the right system with durable retries, so an outage can delay a message but not lose one.

Inbound message

Relay

Received and stored

9:41:02

Pushed to ERPNextDelivered
Pushed to OdooRetrying

The Nix platform

One declarative way to develop, test, and host each platform we support. The same pinned inputs build the developer's shell, CI, containers, and the NixOS production server, and all three share logging conventions so one query spans every system.

One design language for business software

Whether a client runs ERPNext or Odoo, their team gets the same clean, accessible interface. We implement both on IBM's Carbon Design System, so screens, tables, and forms look and behave consistently across the systems we build.

ERPNext

Order

Status

SO-0418

To deliver

SO-0419

Draft

Odoo

Order

Status

S00231

Confirmed

S00232

Quotation

Frappe & ERPNext

Apps for Frappe and ERPNext, from project portals and billing to themes and integrations.

10 projects

A project and task workspace for ERPNext, with timers and hour budgets for staff and a portal where customers follow and work on their projects.

Simpler customer, contact, and address management for ERPNext, with address validation, geolocation, and a map of your customers.

Automatic billing for ERPNext Subscriptions, with payment requests, billing anchors, proration, consolidated invoices, and credit notes.

A complete IBM Carbon Design System theme for Frappe and ERPNext, covering the desk, website, login, email, charts, and tables.

eSign

Stable

Collect electronic signatures on any Frappe or ERPNext document through web forms, with signed PDFs and a full audit trail.

Messaging

Stable

A unified chat-style inbox for email and SMS in Frappe and ERPNext, with Twilio texting, group broadcasts, and mail-merge newsletters.

Connects ERPNext to Mercury bank for client billing, payroll and vendor ACH, bank sync, reconciliation, and GL-coded journal entries.

Mail printed Frappe and ERPNext documents as physical letters through PostGrid, by hand or automatically from Notifications.

Jailbreak

Stable

Power-user tools for Frappe and ERPNext admins, including bulk merge, item-to-variant conversion, and version restore, each gated behind a setting.

Odoo

Odoo 18 Community modules, built on and alongside OCA, with no Enterprise dependencies.

5 projects

Avunu's Odoo 18 Community modules for email and SMS, document import, AI providers, and the backend and shop-floor UI, built to work alongside OCA.

AGPL-3.0-or-later · LGPL-3.0-or-laterGitHub

Odoo 18 modules that turn vendor emails, PDFs, and printed documents into Odoo records, with templates, structured extraction, previews, and routing.

AGPL-3.0-or-laterGitHub

Odoo 18 modules that send and receive email through Cloudflare and run two-way Twilio SMS and MMS conversations inside Discuss.

AGPL-3.0-or-laterGitHub

Odoo 18 modules for a Carbon-styled backend, a live timesheet timer in the navbar, and camera scanning and social sign-in for the OCA Shopfloor app.

AGPL-3.0-or-later · LGPL-3.0-or-laterGitHub

Adds Cloudflare Workers AI as a MuK AI provider in Odoo 18, optionally routed through a named Cloudflare AI Gateway for usage tracking.

AGPL-3.0-or-laterGitHub

WordPress

Plugins configured in wp-config.php, built to be managed across many sites.

3 projects

Replaces WordPress logins with single sign-on through an OIDC provider or an identity-aware proxy, configured entirely in wp-config.php.

Stores and serves the WordPress media library from S3-compatible object storage, with direct browser uploads and document thumbnails.

GPL-3.0-or-laterGitHub

Routes all WordPress email through the Cloudflare Email Sending API and keeps a searchable log of every message, with no settings screen.

NixOS

Declarative, reproducible infrastructure for hosting business systems and running dedicated devices.

6 projects

Reproducible Nix infrastructure for Frappe and ERPNext, from the development shell to OCI containers and a multi-site NixOS module.

odoo-nix

Active

Reproducible Nix infrastructure for Odoo Community (OCB) and OCA projects, from scaffolding and development to containers and NixOS.

A fast FrankenPHP WordPress stack built with Nix, deployable as OCI containers or a NixOS module, with MySQL, Cloudflare D1, or Turso databases.

Web Kiosk

Stable

A USB-booting NixOS image that turns an x86 computer into a locked-down Firefox kiosk for a single web page.

A NixOS module and Rust daemon for rclone mounts and two-way sync that pushes local changes in seconds, with Markdown-to-docx conversion built in.

A low-maintenance NixOS desktop inspired by openSUSE Aeon, set up once and then managed through GNOME Software and Flatpak.

General

Tools that work across platforms.

2 projects

Jx

Active

A full-stack web framework and visual editor built on plain JSON and Markdown, compiling sites to fast, static HTML.

A multi-tenant Cloudflare Email Routing Worker that stores every inbound message and pushes it to the right Odoo or Frappe instance with durable retries.

Why open source

No lock-in, by design

Our clients own their systems: the code, the data, and the right to take both anywhere. That only means something if the pieces we build are open too. Everything here is published under an open license, so any qualified developer can read it, support it, or fork it, whether or not you keep working with us.

Building in the open also keeps us honest. Public code gets read, tested by strangers, and judged on its own merits. Generalizing a fix for publication tends to make it simpler and better documented, and that's the version our clients run.

You own it. Nothing here needs a license key or a subscription to keep working.

You can see it. Every line is reviewable before it touches your business.

It outlives us. If we disappeared tomorrow, your system would keep running and someone else could pick it up.

Need one of these running in your business?

We wrote these tools, and we implement, host, and extend them for clients. Tell us what you're working on and we'll tell you honestly whether one of these fits, or whether you need something else.