Why Does Perplexity Describe a B2B SaaS Product as Cloud-Only When It Offers Self-Hosting?
Perplexity describes a B2B SaaS product as cloud-only because the pages it finds say "SaaS" and "cloud platform". Meanwhile, the self-hosted option sits behind a "contact sales" button, in installation docs on another subdomain, or under terms buyers do not search for. Perplexity searches the web for each question and answers from the top results. If none of them says "self-hosted" plainly, the answer defaults to what the word SaaS implies. Review-site deployment fields and cloud marketplace listings often show cloud only, and older articles predate the self-hosted launch. The fix is a deployment options page written in buyer language. Name self-hosting on your pricing and product pages, make the install docs crawlable, and update every listing that records deployment.
Why does the self-hosted option get missed?
- The category label. "SaaS" means software you do not host. Assistants reasonably take it at face value unless something says otherwise.
- Hidden in pricing. Self-hosting often appears only as an enterprise plan with "contact us", with no text saying what it is.
- Different vocabulary. Your docs may say "on-premises", "private deployment", "bring your own cloud" or "Helm install", while buyers ask for "self-hosted". A page that never uses the buyer's word may not be found for the buyer's question.
- Docs on another subdomain or behind a login. Installation guides that Perplexity's crawler cannot reach, or that are blocked by robots rules or bot protection, do not count.
- Listings that record deployment. Software review sites let buyers filter by deployment, such as cloud, SaaS or web-based versus on-premise. If your profile lists only cloud, that is what gets repeated.
- Marketplace listings. Cloud marketplaces distinguish delivery methods. AWS Marketplace, for example, supports AMI-based, container-based and SaaS products. A SaaS-only listing reinforces the cloud-only reading.
- Older coverage. Reviews and comparisons written before the self-hosted option launched.
How assistants put products in the wrong category more broadly is covered in why AI puts your product or company in the wrong category.
Why does Perplexity in particular get this wrong?
Perplexity answers from a small set of pages it retrieves for each question, so the answer is only as complete as those pages. For "Can [product] be self-hosted?", check which pages Perplexity actually retrieves, such as your home page, your pricing page, a review profile or a comparison article. If none of them says "self-hosted", the answer may not either, even if a detailed installation guide exists deeper in your docs. That is why the fix is to put one plain sentence about self-hosting on the pages that already rank, and to link them to the deployment page. A strong page nobody links to is rarely among the few that get retrieved. How Perplexity finds and cites sources is covered in how Perplexity retrieves and cites sources in real time.
What should the deployment options page say?
Create one page at a stable, obvious URL, such as /deployment or /self-hosted, linked from your home, pricing, security and docs pages. In text:
| Section | What to write |
|---|---|
| Summary | "[Product] is available as a cloud service hosted by us, or self-hosted on your own infrastructure." |
| Options | Cloud; self-hosted on Kubernetes, Docker or virtual machines; private cloud; air-gapped, if offered |
| Who it is for | Data residency, regulated industries, security reviews, network isolation |
| Feature differences | A table of features by deployment option, including any not available self-hosted |
| Licensing and pricing | Which plans include self-hosting, and how it is priced |
| Support and updates | Who runs upgrades, release cadence, support hours |
| Requirements | Supported platforms, minimum resources, dependencies |
| Getting started | A link to the public installation guide |
Use the buyer's words, "self-hosted" and "on-premises", in headings and the first sentence. Include your internal terms too, so both are matched.
What else should change on your site?
- Pricing page: name the self-hosted option in text on the plan that includes it, even if the price is "contact us".
- Home and product pages: one sentence near the top: "Run it in our cloud or self-host it."
- Security and compliance pages: these are often cited for data residency questions. Mention self-hosting where relevant.
- Installation docs: public, crawlable and linked from the deployment page. Check that robots rules and bot protection on the docs subdomain allow the search crawlers you want, including Perplexity's.
- Meta descriptions and titles: where deployment matters to buyers, include "cloud or self-hosted".
Which external listings should you update?
- Software review sites: set the deployment fields to include on-premise or self-hosted, and mention it in the description.
- Cloud marketplaces: if you offer a self-hosted version, consider listing it with the matching delivery method, not only as SaaS.
- Comparison articles and analyst profiles: send an update to authors whose pages Perplexity cites for your category.
- Partner and reseller pages: partners who sell or deploy your self-hosted version should describe it plainly.
- Your open-source repository, if the self-hosted edition is open source: link it from the deployment page and vice versa.
Should you state feature differences?
Yes. If the self-hosted edition lacks some cloud features, or receives them later, say so in a table. An answer that says "self-hosting is available, though some AI features are cloud-only" is accurate and still wins buyers who need self-hosting. An answer that says "cloud-only" loses them entirely. Honest differences also prevent the opposite error, where assistants promise full parity and buyers find gaps during evaluation. How total cost comparisons can mislead buyers is covered in why ChatGPT recommends a cheaper-looking SaaS vendor on total cost of ownership.
How do you test what Perplexity and others say?
Ask Perplexity, and for comparison ChatGPT, Gemini and Google's AI features, several times each:
- "Can [product] be self-hosted?"
- "Does [product] have an on-premises version?"
- "Self-hosted alternatives to [competitor]"
- "[Category] tools that can run on our own servers"
- "[Product] data residency options"
Record whether each answer mentions self-hosting, whether it describes the differences correctly, and which pages it cites. If Perplexity cites your marketing pages but not your deployment page, check that the page is linked from them and uses the question's words. If it cites review sites, check their deployment fields.
What might an illustrative case look like?
Consider an illustrative observability platform that launched a self-hosted edition, installed through a Helm chart, for regulated customers. Six months later, Perplexity answered "Can [product] be self-hosted?" with "No, [product] is a cloud-based SaaS platform". It cited the home page, a review site profile and a comparison article. The home page said "cloud observability platform". Self-hosting appeared only as "Enterprise: private deployment, contact us", and the Helm docs sat on a docs subdomain that bot protection was blocking. The company published a /self-hosted page with a feature table and added one sentence to the home page. It fixed the docs subdomain rules and updated the review profile's deployment field. Within a month, most answers said the product could be self-hosted, citing the new page.
What do people ask about deployment options and AI answers?
Should we stop calling ourselves SaaS?
Not necessarily. Say "SaaS or self-hosted" wherever deployment matters to buyers.
Does structured data help here?
There is no widely used markup property for deployment model. The visible text on your deployment page matters most.
How quickly will answers change?
Perplexity searches live, so answers can change within weeks once the new page is found and linked. Model-knowledge answers take longer.
Published by The Kovmere Team · updated Sep 29, 2026 · More resources