Feature availability
A transparent view of what works today, what is partial, and what is not yet supported.
This page separates implemented product behavior from foundations that still need a public contract and from capabilities that do not exist today. It is intended to keep documentation, marketing, sales, packaging, and roadmap discussions anchored to the same current-state evidence.
Available does not always mean unlimited or available on every tier. Partial means code or interface foundations exist but setup, coverage, reliability, or documentation is not complete enough for a broad promise. Not supported means the capability should remain out of current product claims until implementation and verification are complete.
Update this inventory whenever a capability becomes customer-accessible, changes tier, gains a stable public contract, or is removed. Evidence should include the route, data model, authorization behavior, setup path, and verified user outcome. A hidden flag, unfinished screen, or internal service is not enough to mark a feature available. Documentation and marketing should change only after the complete customer path is validated.
Available now
These capabilities have routes, data models, or product surfaces in the current Webreport codebase.
A capability belongs here only after its complete customer path has been exercised with normal authorization and production-like data. Document tier requirements and material limits beside the feature so available is not interpreted as universal or unlimited.
- Combined SEO and GEO scans with tier-based crawl, render, performance, prompt, model, judge, and budget limits.
- Portfolio and project workspaces with SEO, GEO, source, action, agent analytics, verification, scheduling, and badge pages.
- Prompt, topic, competitor, AI answer, source, gap, action, and impact workflows.
- Editable report builder, document and presentation layouts, PDF export, share links, white-label Pro reports, and email delivery.
- Google Search Console OAuth connection and search performance queries.
- Pro API keys, a complete public REST v1 surface, OpenAPI 3.1, stable errors, cursor pagination, request identifiers, rate-limit headers, and idempotent mutations.
- Starter and Pro signed webhooks with a versioned event catalog, endpoint lifecycle, delivery inspection, deterministic retries, replay, and secret rotation.
- Durable alerts with rules, delivery preferences, and open, acknowledged, resolved, and muted lifecycle states.
- An append-only credit ledger with recurring allocations, attributed debits, adjustments, expirations, balance, and usage summaries.
- Crawl-insight connections, bounded log uploads, authenticated Cloudflare and Vercel push ingestion, AWS CloudFront S3 pull ingestion, normalized bot events, retention, freshness, and analytics.
- Read-only product MCP over stdio or Streamable HTTP, with evidence tools and native analysis prompts.
- A typed TypeScript SDK, full CLI, durable CSV and JSONL exports, and Looker Studio connector source.
- Deployment-level OpenRouter or DeepSeek routing for Sight's own LLM workloads.
- Stripe subscriptions, one-time scans, plan changes, recovery, receipts, and billing lifecycle emails.
Partial or needs product clarification
The foundation exists, but the public contract, setup flow, or coverage is not complete enough to present as a broad platform capability.
Partial capabilities need precise boundaries. State which path works, which setup or data source is missing, and what should not be promised. Move an item to available only after the public contract, documentation, error handling, and verified outcome are complete.
| Capability | Current state | Needed next |
|---|---|---|
| Model channels | Projects select provider families and the engine maps them to configured model IDs. | Stable public channel names, version policy, deprecation policy, and per-plan availability |
| Looker Studio distribution | Connector source and deployment instructions exist. | Complete the customer-controlled Google Apps Script deployment or marketplace review |
Not supported today
Do not advertise these as current product features.
Missing capabilities can inform prioritization and packaging, but they should not appear in current-feature comparisons or sales commitments. Record the user problem and likely tier separately from any delivery estimate, architecture choice, or final commercial decision.
| Missing capability | Recommended tier | Why it matters |
|---|---|---|
| Customer-managed model-provider connections | Higher tier | Lets organizations connect OpenAI, Anthropic, Google, OpenRouter, or Azure credentials and control routing |
| Bring-your-own-key billing | Higher tier | Separates platform fees from model usage and supports enterprise procurement |
| SSO, SCIM, and granular role administration | Enterprise | Required for larger organizations and regulated customers |
| Audit log and retention controls | Enterprise | Provides governance for access, exports, configuration, and deletion |
| Regional data residency and customer-managed encryption | Enterprise | Supports procurement and compliance requirements |
| Native Slack, Teams, email digest, and ticketing integrations | Starter and above | Turns alerts and actions into an operational workflow |
No roadmap dates are promised
This page records current implementation status and product opportunities. It does not commit to delivery dates or final packaging.
Roadmap sequencing, packaging, and dates remain separate decisions. Update the status only when implementation evidence changes, and avoid wording that can be read as a delivery commitment.