Joomla development by people who build Joomla software
Most agencies that take Joomla work are generalists who learned it for one client. We have shipped Joomla products since 2012 — templates, extensions, and Quix, a page builder other developers build client sites on.
- Building Joomla since
- 2012
- Websites running our work
- 50,000+
- Our own Joomla products
- Quix, templates, extensions
The work Joomla sites actually need
Not a menu of everything — the six kinds of project that make up most of what comes to us, and where knowing the platform properly changes the outcome.
Builds from scratch
A Joomla site designed and built to your brief — information architecture, templating, the extensions it genuinely needs and none of the ones it does not.
Version migrations
Joomla 3 to 4 to 5 to 6, the upgrade most sites stall on. Extension compatibility mapped first, overrides rebuilt, content migrated with URLs preserved.
Custom extensions
Components, modules and plugins written when an off-the-shelf extension is close but wrong, or when the integration you need does not exist yet.
Template development
Templates built to your design rather than bought and bent — including Quix-native layouts your team can edit after we hand over.
Performance work
Caching, query and asset work against Core Web Vitals, on sites where the fix is architectural rather than a plugin.
Rescue and handover
Inheriting a site nobody documented: an audit of what is installed, what is patched, what is abandoned, and a plan to make it maintainable.
We hit these problems before you did
Building products on Joomla means supporting them across every version, hosting setup and extension conflict our customers run into. That is a different kind of knowledge from having delivered a handful of Joomla sites — and it is most of what you are paying for on a migration or a rescue.
How Quix compares to other builders- 01
Scope
A call and a look at what exists. You leave with a written scope, a fixed price and a delivery date — not an hourly estimate that drifts.
- 02
Build
Work happens on staging with a link you can watch. Feedback in writing against the staging site, not reconstructed from a call.
- 03
Hand over
Deployed, documented and handed to your team. Where you want it kept up afterwards, that moves onto a care retainer.
Before you get in touch
Do you work with agencies or only direct clients?
Both. A large share of our work is white-label delivery for agencies building on Joomla for their own clients, where we stay behind your brand and report to you rather than to the end client.
Can you take over a Joomla site somebody else built?
Yes, and it is a common starting point. We audit what is installed, what is patched, what has been abandoned upstream and what has been customised in ways that block updates, then give you the plan before any work starts.
Is upgrading from Joomla 3 still worth it?
Joomla 3 reached end of life, so it no longer receives security fixes — an unpatched CMS is the risk, not the upgrade. The real question is whether your extensions have Joomla 6 equivalents, which is what the compatibility audit answers before you commit.
Do I have to use Quix?
No. Quix is our own page builder and we use it where a client wants their team editing pages after handover, but plenty of projects are built with plain Joomla templating instead. The build should suit who maintains it.
What does a project cost?
Projects are quoted fixed-price after scoping, because the honest answer depends on what exists and what has to move. Scoping is where that gets settled, and it happens before you commit to a build.
Do you maintain the site afterwards?
If you want us to. Ongoing updates, security, backups and performance run as a monthly care retainer — the detail is on the services page.