| Where the data comes from | The homepage calls real model APIs. Human tests for specific website or app experiences are arranged separately. | The provider says it collects directly from consumer interfaces rather than API outputs. | Collects from browser interfaces; most platforms primarily use signed-out experiences. | Mainly collects from public web interfaces; Claude uses the API. |
|---|
| What you can observe | Custom questions, answers from multiple models, domain-based brand understanding and competitors; original answers and returned sources are retained. | AI visibility, citations, question demand, crawler activity and traffic analysis. | Brand and competitor trends, cited sources, and opportunities for content and source coverage. | Brand mentions, cited links, prompt monitoring and GEO audits. |
|---|
| Deployment and control | Apache-2.0 open source; self-host, configure model accounts and customize workflows. | Hosted platform; configuration and access features depend on the plan. | Hosted platform; projects and monitoring conditions are configured in the product. | Hosted platform; monitoring uses the conditions supported by the product. |
|---|
| Ongoing monitoring and maintenance | The open-source project supports ongoing monitoring. Self-hosters must run the task service and maintain storage and the runtime environment. | The platform provides monitoring infrastructure and workflows. | Daily prompt monitoring and trend analysis. | Daily prompt monitoring; country and platform coverage depend on the plan. |
|---|
| Content and services | Human testing: 5 credits per person, question and AI for one submission. Articles: CNY 350 for one, CNY 8,888 for 30, or CNY 28,888 for 90 plus 5 real-person YouTube videos. | Beyond monitoring, offers content Agents and creation and publishing workflows. | Offers improvement recommendations and content opportunities; specific production and publishing integrations depend on the product. | Offers monitoring and audit recommendations. Article distribution or media publishing services need separate confirmation. |
|---|
| Team support | The current workbench is intended for trusted self-hosted use. Deployment owners handle permissions and maintenance; human services are arranged after requirements are confirmed. | Enterprise SSO, role-based access and support options depend on the plan. | Team, agency and enterprise plans; advanced integrations depend on the plan. | Team seats and enterprise support vary by plan. |
|---|
| What you pay for | The source code is free; model usage, servers and maintenance cost extra. Human tests are charged by submissions across people, questions and AIs. Articles use the published package prices. | Subscription tiers based on scale and features; content Agents consume credits. | Subscription tiers based on prompts, projects, coverage and advanced features. | Subscription tiers based on prompt allowances; some AI platforms require paid add-ons. |
|---|
| What to check before buying | Who maintains the system? What is the model budget? Which test records and article deliverables do you need? | Which engines and workflows are included? How many credits and what enterprise support do you need? | Do the prompt limits, regions, models, projects and data exports meet your team’s needs? | What is the total cost for prompt allowances, additional models, regions and team seats? |
|---|