Alternative to Squiz

Squiz runs hundreds of sites from a single instance and boasts one of the most complete enterprise search engines on the market. Both things are true. What you will not find on its website is what it costs, or how long your team needs to learn a model where every page is an “asset” with nine possible states.

Squiz has spent 12 consecutive years in the Gartner Magic Quadrant for DXP as a Niche Player, with more than 500 declared customers, strong in government and higher education across Australia, New Zealand and the UK. It is not a minor competitor: it runs genuinely large university ecosystems, and its search engine, Funnelback, is among the best we have reviewed.

This comparison is not out to say Squiz is a bad DXP. It is about what happens when you compare it with Griddo point by point — including the points where Squiz genuinely wins, and the ones where it only appears to.

Let us start with where Squiz is genuinely strong.

Squiz handles multisite governance at scale. Clients run hundreds of websites from a single installation, with shared component libraries and per-site permissions — an established pattern in university networks and public administrations. It is one of its best-scoring capabilities among independent analysts.

And it works the same way Griddo does: site-level isolation within one instance. Shared global content, isolated local content, centralized governance. The underlying architecture is the same idea.

Griddo does exactly this, and is doing it today. IE University runs 43 websites and more than 60,000 pages from a single instance. Universidad Pontificia de Comillas has 60 people across 31 departments, faculties and institutes publishing concurrently on 8 sites. Universidad Europea operates five distinct brands — IPAM, IADE Portugal, IADE Spain, UDDI and Centro de Estudios Garrigues — with 16 people covering all five instances. A single Griddo client runs 60 websites in 8 languages from one installation.

None of those figures is a ceiling: they are where the largest installation stands today, not the limit of the architecture. The same structure that holds 43 websites holds 100 without a redesign.

Honest conclusion: on governance at scale, they tie. Squiz has proven it in government and higher education across ANZ and the UK for longer. Griddo is proving it right now in private universities in Spain, Chile and Portugal. Neither platform has a documented scale ceiling. The difference is not whether you can scale — it is what each new website costs and how long it takes at that scale, which is what comes next.

Funnelback, Squiz’s search engine, is genuinely its best feature: full-text search with more than 70 ranking factors, machine-learning tuning, faceting, typo tolerance and multi-source indexing that federates content from external systems. It is the highest-scoring capability in its entire platform in the independent evaluation we consulted, above any other Squiz feature or that of its direct competitors.

We are not going to play that down. It is mature search, built over nearly two decades.

Griddo also does faceted search, corrects typos and tunes results with machine learning. The technical difference is the approach: Griddo AI Search turns content into embeddings to do vector and semantic search — it connects concepts, not just keywords, so someone typing “help so my child can study abroad” finds the scholarship and Erasmus pages even though those words never appear on the site — and weights answers according to what each university actually cares about, with no manual rules for anyone to maintain. It indexes itself, needs no training data from the institution, and every answer carries verifiable citations to real content. It goes live in 48 hours.

There is one point where Griddo has a documented advantage: Squiz personalization remains rules-based, not machine learning — the same independent evaluation scores it as one of the weakest areas of its platform. Griddo Personal Experience (GPX), Griddo’s personalization engine, infers each visitor’s interest in real time, with no segments or rules configured by anyone.

Honest conclusion: on search capabilities, both platforms cover the essentials — facets, typo tolerance, ML tuning. Squiz has more years of accumulated enterprise tuning in Funnelback. Griddo has a more modern approach (vector, semantic) and personalization that is genuinely ML rather than rules. It is not a point where Squiz simply wins — it is a point where each chose a different path.

squiz.net/pricing returns a 403 error. It is not an oversight: independent aggregators such as SaaSworthy, G2, GetApp, Capterra and Software Advice all agree — custom quote, no public rates, no indicative range.

Squiz describes its model as “one single price” bundling licence, usage, platform and support into a 12-month subscription, billed according to the capabilities actually used. As a concept it is predictable. Without published rates or usage tiers, the variable component cannot be modelled before signing.

What we do know for certain, because Squiz’s own subscription agreement confirms it: billed annually in advance, with auto-renewal, no monthly option, and no free trial or self-service sandbox of any kind. Evaluation means going through sales from the first minute.

With Griddo, all four plans carry a public price from the outset: from €1,500/month (Institute, 1 site) to €5,000/month (University, 9 sites), with additional sites at €150/month. Implementation is variable, depending on scope and delivery partner; the Cloud Enterprise model adds a one-off €7,500 cloud setup fee. Published discounts for quarterly, annual and biennial billing. One invoice for platform, AI and add-ons.

This is what sits underneath Squiz’s opaque pricing, and it explains much of why implementation costs what it costs.

Squiz Matrix organizes pages, images, workflows and users in the same hierarchical tree — the “everything is an asset” model — with a lifecycle of nine possible states (Under Construction, Live, Safe Edit, Archived, and several more), plus Paint Layouts, Contexts and HIPO Jobs layered on top. It is a mental model some distance from how a standard web developer works, and the independent evaluation we consulted describes it that way: Squiz’s “concept complexity” score is among the lowest in the set of platforms compared.

In practice: there are no official starters for Next.js, Nuxt or Astro; deploying a component requires a multi-step CLI flow with console access provided by the Squiz team; and in G2 reviews, ease of setup drops to 6.9 out of 10 — the weakest figure in its whole profile, against 9.5 for content authoring once the system is running.

With Griddo, the Live Author Experience shows the real result as you edit, with no code and no proprietary learning curve to clear before publishing the first page. A faculty coordinator builds the page, sees it and publishes it on day one.

In the independent evaluation we consulted, Squiz’s AI category scores 33.8 out of 100 — the lowest of the ten categories assessed, and by a wide margin.

What is missing, according to that same evaluation: no MCP server, no support for bringing your own model (BYOM/BYOK — Squiz chooses and manages the model, not the customer), no AI image generation, no native machine translation, and personalization that remains rules-based rather than machine learning. In May 2026 Squiz launched an AI content auditor (Content Intelligence), which is a real step, but it arrives late and covers auditing only, not content production.

With Griddo, AI is built into the editor from day one: AI Booster translates with DeepL, generates SEO metadata with OpenAI and tags images with Amazon Rekognition, all on a single invoice. AI Search turns the site into a question-and-answer experience with verifiable citations. GPX personalizes each page in real time according to each visitor’s actual interest, with no manual rules. None of the three requires contracting or paying an AI vendor separately.

Squiz says it has more than 500 customers. On G2 it has 27 reviews — a very small base for that figure, and the independent evaluation itself flags it as a striking discrepancy.

Specialist Squiz Matrix/DXP talent is concentrated in a handful of agencies in Australia and the UK; there is almost no presence on Stack Overflow or Reddit, and hiring Squiz developers outside those geographies means, according to a review cited in that same evaluation, a cost premium “firmly at the high end (50%+)”. And it is not just theory: in one documented university project, the delivery team changed four times before the platform was operational.

For a university outside ANZ or the UK — which is most of those reading this page — that is a real implementation risk, not a hypothetical one.

There is a nuance here worth explaining properly, because the sources are not consistent.

Squiz DXP, the modern product (“Matrix 6”), is pure SaaS, hosted on AWS and managed entirely by Squiz. There is no on-premises installation route for the current feature set: CDP, Content Intelligence, conversational search.

Squiz Matrix, the legacy CMS with open source roots, does support on-premises or private cloud deployment — but it is precisely the product Squiz has been pushing customers to migrate away from, onto Matrix 6 SaaS, through a two-to-four-week programme with customer UAT, largely complete by mid-2026. If the buying argument today is “we need on-premises”, the real Squiz answer is a product the vendor itself is retiring.

Squiz does offer a region choice within its own cloud — UK, North America and Australia — with no explicit EU region and no public subprocessor map.

Griddo can be deployed under two different sovereignty models: its architecture is MACH (microservices, API-first, cloud-native, headless) by design. In Griddo Cloud, the infrastructure is managed by Griddo. In the Enterprise model, the university contracts its own cloud directly (with AWS or another provider), chooses the region — Europe by default for European universities — and keeps ownership of the infrastructure contract, with Griddo handling deployment, monitoring and platform evolution end to end. It is the difference between “choosing a region inside the vendor’s cloud” and “owning the infrastructure contract”.

Griddo also requires an implementation. Standing it up at a university is a project, with a variable implementation cost. And three things are always customized.

The design system. It is created exclusively for the university’s brand. That is not a product gap: it is a decision. An institution’s reputation is its most valuable asset, and its visual identity is part of that reputation.

Taxonomy and catalogue. Every university offers different programs, with different academic structures. Content types are modelled on their reality.

Integrations. Every institution has its own CRM, ERP and student system. That connection is configured for each one — and here we should be fair to Squiz: it has no official connectors for Banner, PeopleSoft, Workday Student, Moodle, Canvas or Blackboard either. Neither platform solves the student system out of the box.

Notice what is not on Griddo’s list: how you edit, approval workflows, technical SEO, and visibility in AI search engines. All of that comes done, with a public price, from day one. With Squiz, on top of the three unavoidable customizations, you add the proprietary asset model and a quote that only appears after talking to sales.

What the project has to build	Griddo	Squiz
Brand design system	Yes, exclusive	Yes (within the Component Service)
Taxonomy and program catalogue	Yes	Yes
CRM, ERP and student system integrations	Yes	Yes
Project price	Public from day one	Only after talking to sales
How you edit and publish	Comes done	Comes done, with a proprietary learning curve
Editorial approval workflows	Comes done	Comes done
AI to translate, tag and personalize	Comes done, one invoice	Rules-based personalization; no BYOM
Try before you buy	—	Does not exist (no trial, no sandbox)

Griddo is a platform built only for universities. Not for government. Not for utilities. For institutions with non-technical communications teams, many websites, and the need to publish fast without depending on an agency specialized in a proprietary model.

Governing the whole estate, with no ceiling. Websites are managed together from one installation. Global content is shared and local content is isolated. IE University already runs 43 websites and more than 60,000 pages; the architecture imposes no upper limit.

Real search and personalization, not rules. AI Search does semantic search over embeddings, with facets and typo tolerance. GPX personalizes each visit by inference, with no manual segments for anyone to maintain.

AI built in. AI Booster translates, generates metadata and tags images inside the editor, on a single invoice, with no separate AI vendors to contract.

Public pricing from day one. Four plans, add-ons with public rates, and no sales call needed to find out whether it fits the budget.

Stability and sovereignty. SaaS managed by Griddo, or the Enterprise model where the university contracts its own cloud directly (AWS or another provider) and chooses the region, with a 99.99% availability agreement.

Universities such as IE University, CUNEF, Universidad Pontificia de Comillas, Universidad de Nebrija, Universidad Europea and Universidad Católica del Maule work on a platform that evolves without them having to manage that evolution.

Data last verified: August 2026.

Squiz is a registered trademark of Squiz Pty Ltd. Griddo is not affiliated with Squiz.