An independent Keragon research example
A buyer asks about enterprise access controls. The answer depends on which of your pages they read.
BrandAnchor checks product facts across official sources and observed AI answers, then prepares consistent corrections for approval.
Open access. No account, email, or prospect details.
A comparison page is one surface. The brand's product, pricing, security, machine-readable records, and AI answers belong in the same review.
This example covers selected sources. Help-center pages, private trust documents, and other AI engines are outside this review.
Fact review
One source disagreement, two questions for the product owner, and three aligned or compatible findings. A missing definition is not automatically a product error.
Showing all six findings.
The comparison page assigns all enterprise controls to every plan. The pricing sources reserve SAML/LDAP identity and granular access controls for Enterprise.
Use the plan-specific pricing record as a provisional reference. Ask Keragon to approve the scope before publishing any correction.
Keragon vs. Zapier · Plans & pricing · Machine-readable pricing
The security page describes roles on every plan. That wording could refer to basic roles rather than the granular Enterprise feature.
Keep this distinction unresolved until the product owner defines standard permissions and granular RBAC. Generic SSO is not automatically Enterprise SAML/LDAP.
The reviewed pricing, security, comparison and llms.txt sources describe a standard BAA on paid plans. Custom BAA terms have a separate Enterprise scope.
Preserve this supported distinction. The review records vendor statements; it does not certify the product or review an executed agreement.
Plans & pricing · Security & compliance · Keragon vs. Zapier · llms.txt
The pricing page, machine-readable pricing and llms.txt agree on a 14-day trial without a credit card.
Keep the trial statement separate from paid-plan entitlements and BAA terms.
Machine-readable pricing uses a 300+ lower bound. The product and llms.txt sources use 400+. Both statements can hold at the same time.
Treat this as a possible freshness improvement, not an exact-count disagreement. A count alone does not establish integration depth or plan access.
The comparison describes dedicated onboarding on paid plans. Pricing describes tiered support. Those services may differ.
Ask the owner to define onboarding separately from recurring support. Do not label the two statements a confirmed contradiction.
Official evidence
Short source excerpts support inspection. Capture details preserve dates and content hashes. Full third-party pages are not republished here.
Plan-specific scope for enterprise identity and granular access.
Granular permissions by role (Enterprise).
Checked 2026-10-22T23:09:26.146722+00:00
SHA-256
2a76174c7ff7e8917548638337e33541959ef5744bedcd4490fac0b38990d024
Public HTTP capture. Exact text verified locally. CSS visibility was not evaluated.
Broad access-control wording needs a distinction between standard and enterprise controls.
role-based permissions on every plan
Checked 2026-10-22T23:10:08.212088+00:00
SHA-256
e0f79ecdca2142f2cb62975ac241b2171f3e04aeada99f55f2791aa3a460b79d
Public HTTP capture. Exact text verified locally. CSS visibility was not evaluated.
The page assigns all enterprise controls to every plan.
All enterprise controls
included across every plan with no tier restrictions
Checked 2026-10-22T23:10:10.638009+00:00
SHA-256
1bcc133aa480f35676662f523557b6bcb4df2b3b8e64f9695db02ea9b8c04aca
Public HTTP capture. Exact text verified locally. CSS visibility was not evaluated.
The pricing record separates Google login from Enterprise SAML/LDAP and RBAC.
Google SSO on all plans.
RBAC, and invoice billing are Enterprise only.
Checked 2026-10-22T23:10:17.995631+00:00
SHA-256
b66f1fcfb21efc15a3da5c477f415b7b0fa548f499fcf877985b59c9b5236ca5
Public HTTP capture. Exact text verified locally. CSS visibility was not evaluated.
An index links to product, pricing and security sources. Its BAA and trial summaries align.
Checked 2026-10-22T23:10:15.615158+00:00
SHA-256
b1c642ebb95e3f46382ce3303f1cba4ed25dcf5a253d34874c4132b5612d9b3f
Public HTTP capture. Exact text verified locally. CSS visibility was not evaluated.
Product and integration descriptions provide context for the buying question.
Checked 2026-10-22T23:10:13.106704+00:00
SHA-256
2a7f0e29af9433dc18aa0d532163f6c30e7461fb6c2212e9c40a9b5d5f4a22db
Public HTTP capture. Exact text verified locally. CSS visibility was not evaluated.
Zapier states that HIPAA-regulated PHI is unsupported on its platform. It also states that it cannot sign BAAs or equivalent agreements for handling PHI.
Checked 2026-10-22T23:12:41Z
Official FAQ reviewed with the web tool. The raw HTTP response omitted this FAQ. No raw-page hash supports this observation.
A comparison backed by both sides
The comparison module uses each vendor's own statement. This is one scoped commercial criterion, rather than a complete product ranking.
| Criterion | Keragon's published position | Zapier's published position |
|---|---|---|
| BAA for paid healthcare workflows | Standard BAA included on paid plans; custom terms on Enterprise. Keragon security source | The official privacy FAQ says Zapier cannot sign a BAA for handling PHI. Zapier's own source |
| Scope of this finding | The review records the vendor's offer. It does not examine an executed agreement. | The FAQ excludes HIPAA-regulated PHI. That does not exclude every healthcare-adjacent workflow. |
Native Google AI Mode observation
Captured 22 October 2026, 17:38 UTC. One run. Model version was not displayed.
The answer reserves SAML/LDAP and granular RBAC for Enterprise, then describes standard roles on paid plans.
The distinction may be valid. The reviewed sources do not settle what standard roles include. This example does not label that answer a proven hallucination.
Enterprise single sign-on (SSO) via SAML or LDAP and granular role-based access control (RBAC) are exclusive to the Enterprise plan on Keragon. Here is a breakdown of how identity management and access control features differ across their plan tiers: Keragon Security & Access Control Features Feature Starter, Professional, & Scale Up Plans Enterprise Plan Authentication (SSO) Google SSO login SAML & LDAP Enterprise SSO Access Control (RBAC) Standard role-based permissions Granular permissions by role Multi-Factor Auth Two-factor authentication (2FA) Two-factor authentication (2FA) While all paid plans include basic security measures like standard role-based permissions, 2FA, and a signed Business Associate Agreement (BAA) for HIPAA compliance, large organizations requiring corporate identity provider integrations and strict, custom permission mapping must opt for the Enterprise tier.
One unified correction package
This proposed reference record uses the published plan-specific evidence. The product owner must approve unresolved scope before any source changes.
| Affirmative Canonical Truth | Explicitly Invalidated Assertions |
|---|---|
| identityKeragon's published pricing assigns Google SSO to every plan and SAML/LDAP SSO exclusively to Enterprise.Published plan scope; brand approval pending | SAML/LDAP SSO across every plan |
| granular-accessKeragon's published plan matrix assigns granular role-based permissions exclusively to Enterprise.Granular roles; standard-role scope remains unresolved | All enterprise controls across every plan |
| standard-baaKeragon's reviewed official sources provide a standard BAA on every paid plan and reserve custom BAA terms for Enterprise.Vendor-published commercial terms | Aligned control; no conflicting assertion observed. |
The second column identifies assertions excluded by the proposed record. It does not claim that each assertion appeared in every reviewed source.
| Surface | Proposed action | Review status |
|---|---|---|
| Comparison page | Replace the all-plan enterprise-control claim with approved plan-specific SAML/LDAP and granular-role scope. | Proposed edit |
| Security page | Define standard permissions separately from granular RBAC. Add the approved identity-provider scope. | Owner clarification first |
| Product & pricing | Preserve the plan matrix. Add a shared definition for basic roles after the owner confirms it. | Preserve + clarify |
| Machine-readable pricing | Keep the same approved plan scope and link to the reviewed human-readable explanation. | Consistency check |
| llms.txt | Optionally link to the approved identity and access record. Retain its aligned BAA and trial summaries. | Optional proposed addition |
| AI answer | After approved source updates, rerun the same buyer question and compare the captured answer. | Recheck not run |
Inspect the source record and proposed edits—no form, account, or domain disclosure required.
BrandAnchor captured six public Keragon sources using bounded HTTP requests. The source text and selected quotations were checked locally. HTML capture does not establish CSS visibility or private product behavior.
The review separates source disagreement, unclear scope, compatible lower bounds, and aligned claims. The plan-specific pricing record is a proposed reference, not a fact approved by Keragon.
One historical native Google AI Mode answer is included separately. The record preserves the exact prompt, capture time, and visible source links. A follow-up measurement remains pending.
An optional llms.txt addition complements the public source edits. Google does not require a special AI text file for inclusion.
Keragon is not represented as a BrandAnchor customer or endorsing party. No website changes were made. Optional Microsoft Clarity replay starts after consent on the official domain. Page text is masked. This page has no contact form.
The platform vision is Canonical Brand Truth & AI Accuracy across official product, pricing, help, documentation, security, comparison, and machine-readable sources, plus observed AI answers.
This review connects the source record, unresolved scope decisions, observed AI answer, and coordinated correction package.