We build on open source. We intend to give some back.
Odoo Community is open source and we rely on other people's work every day. It would be poor form to take from that and publish nothing. So this page exists to state the position plainly rather than to advertise a library we do not yet have.
Nothing published yet.
Everything we have written so far has been specific to how one client trades — a booking flow for one site, a handover inspection for one hire fleet, a QA sequence for one roofing contractor. Published, those would be curiosities rather than tools. Releasing code nobody can use is a marketing exercise, and we would rather not.
What we are watching for is repetition. The second time we build something the same way for an unrelated client, it stops being bespoke and starts being a module. That is the point at which publishing it costs us little and saves someone else a fortnight.
What would get released.
Three conditions. A module needs all three, not one.
It is useful beyond the client who paid for it
General enough that another business in the sector could install it and recognise their own process, rather than needing it rewritten first.
There is demand for it
Asked for more than once, by people who are not us. A published module carries a maintenance obligation, and we will not take that on for something nobody needs.
The client is content for it to go out
Nothing is published over a client's head. Where a module is genuinely part of how they compete, it stays private regardless of how useful it would be to others.
When it happens, it will be listed here
With the licence, the supported Odoo versions and a repository link. If you want telling, say so and we will.
Why it matters to you either way.
The open platform is part of what you are buying, whether or not we ever publish a line of it.
Your system survives us
Odoo is open source and widely implemented. If Saxon Digital disappeared tomorrow, your system is not orphaned — another practice can read it, run it and carry on. That is the whole point of building on an open platform rather than a proprietary one.
Written to be read
We write custom modules as proper modules against the framework, documented, with the expectation that somebody else will eventually open them. That discipline is the same whether the audience is the public or your next supplier.
What stays private
Your data and configuration, always. Modules specific to how you trade, by default. The ownership routes are set out on Pricing.