There’s growing talk of digital sovereignty as enterprises rethink past consolidation decisions made in the name of simplicity. Mozilla, developer of Firefox, argues that a “very specific, very important layer” has been mostly missing from that conversation: The browser.
There’s growing talk of digital sovereignty as enterprises rethink past consolidation decisions made in the name of simplicity. Mozilla, developer of Firefox, argues that a “very specific, very important layer” has been mostly missing from that conversation: The browser.
To that end, the company has unveiled Firefox Enterprise in a bid to diversify the browser engine to support privacy, control, and security.
The new offering combines the Firefox browser with a management console that enterprises can run on their own infrastructure using their own tooling. Companies get a full view of their data and can govern how it moves, and IT teams can manage policy, access, and set controls around AI use.
Firefox is already deployed across thousands of organizations and used by roughly 200 million people each month, Mozilla said. It is built on Mozilla’s independent Gecko engine, the only major browser engine developed outside Google and Apple.
“If all your options are built with the same technology underneath, ‘choice’ is a lie. So is control,” Mozilla CEO Anthony Enzor-DeMeo observed in the blog post announcing the product.
“Firefox is hardly the first browser vendor to offer an enterprise-optimized choice,” said independent technology analyst Carmi Levy. “But it carves out a unique value proposition for IT organizations intent on maintaining independent control over how browsers are deployed, configured, secured, and managed.”
In context
- Topic: Estrategia y Gobierno de TI — Decisiones de portafolio, costo total, gobierno y marcos de referencia.
- Source: CIO
- Published: 13/10/2026
Continue reading at the original source →
Excerpt published automatically by the site radar. The full text belongs to its publisher and is linked above.
Why it matters
There is a wide gap between a company that has technology projects and one that has a technology strategy. The first accumulates initiatives; the second decides what it will not do. Moves like this are usually the moment somebody at the top finally wrote down the list of what gets left out.
My filter is always the same: does this change a decision, or only a tool? If at the end of the quarter the same people are approving the same things by the same criteria, there was no transformation, there was a purchase. The difference shows up in the committee minutes, not in the press release.
What usually goes wrong
The classic mistake is confusing the plan with the execution. A three-year roadmap gets approved in a two-hour committee and nobody revisits it until there is a problem. Plans that work get reviewed every quarter and corrected without drama; the ones that do not get defended instead.
What to watch
- The real calendar of contracts and renewals: that is where you see whether the move was strategic or was an expiry date.
- What gets switched off to fund the new thing; if nothing does, the budget will hurt in six months.
- How the relationship with current vendors is left, which is usually where the dependency nobody measured is sitting.
How I read this entry
If this landed on my desk, the first thing I would ask for is not a plan. It is an honest inventory of what is already running and what it costs to keep it alive. It almost always turns out that the budget for the new thing comes from switching off something old that nobody wants to name, and that conversation decides whether the project lives.
This entry is an excerpt from the original source, selected by the site radar. The commentary above is the site's own and does not belong to the cited publisher.
Comments
No comments yet. Yours can be the first.
Living through this in your own team?
Open the chat and tell me how you're handling it. I'm interested in comparing notes.
