We bet on Joomla in 2012 and never moved
One platform, fourteen years, every major version.
Most vendors hedge across three CMSs and know none of them to the floor. We went the other way. Everything below is the argument for that choice — first for the platform, then for the kind of team that stays on one.
- 2012
- Shipping Joomla products since
- 2.5 → 6
- Joomla versions carried through
- 1
- Platform, the whole time
- Dhaka
- Where the team sits, GMT+6
The case has not changed, and it is still not fashionable
Joomla is not the platform that wins the pitch on brand recognition. It is the one that keeps being right four years in, when the site has grown editors, languages and a permissions model nobody planned for.
Multilingual without a plugin
Joomla ships language handling in core. On the platforms that do not, multilingual is a paid extension you inherit responsibility for — and the first thing to break on a major upgrade.
Real access control in core
Groups, access levels and per-item permissions are part of the CMS. For anything with editors, contributors and a client who should not see the billing settings, this is the difference between configuring and building.
GPL, and genuinely open
No seat pricing, no licence audit, no vendor deciding your roadmap. A site you hand to a client stays a site they own.
A predictable upgrade path
Joomla telegraphs its major versions and supports them for years. That is unglamorous and it is exactly what you want when the site has to still be standing in 2031.
Depth is the only thing breadth cannot fake
A generalist agency can learn a platform in a quarter. What it cannot do in a quarter is accumulate the fourteen years of edge cases that make the difference between a confident answer and a plausible one.
01
We have already hit it
Fourteen years on one platform means most problems arriving in a support ticket are ones we have seen. The reply is usually the fix, not the first question of four.
02
We build on our own stack
The page builder, the templates and the extensions are ours, so a bug is something we patch rather than something we report upstream and wait on.
03
We have done the migrations
Every major Joomla version since 2.5 has been carried across on real sites. Knowing what breaks in a version jump is not something you can read up on the week you need it.
04
We are still here
Plenty of Joomla vendors from 2012 are not. The bet an agency makes on a vendor is really a bet that they will answer the ticket in three years.
Four things, all of them Joomla
What this bet costs you, and what it does not
If you need WordPress, we are the wrong vendor and will say so on the first call — our Services team works on both, but the products are Joomla and only Joomla. What you get in exchange is a team that has never had to divide its attention, and that has answered the same ticket queue since 2012.
We are a small team in Dhaka working with agencies across a lot of time zones. Live chat is open while Dhaka is, and everything else runs on a written ticket trail with published response times — so a question asked at 3am in another time zone is answered against a clock you can hold us to, not left in a chat window nobody is watching.