Thyris GEO Platform
Thyris GEO Platform is a workspace-based operating system for Generative Engine Optimization. It measures how a brand, website, product, service, campaign, topic, claim, person, market, and channel asset appears in generative engines; turns evidence into prioritized work; publishes approved changes; and connects those changes to AI referral and conversion signals.
GEO is not a checkout-readiness score and it is not limited to a single model vendor. OpenAI-compatible systems, Anthropic Claude, Perplexity, Google Gemini, custom agents, MCP components, RAG sources, routers, and workflows can be observed or simulated without mixing synthetic results with observed evidence.
Closed-loop workflow
Platform topology at a glance
Capability map
| Area | Capabilities |
|---|---|
| Portfolio | Projects, markets, languages, targets, competitors, aliases, relationships, ownership, versions |
| Research | Topics, prompts, prompt sets, intent, market/language coverage |
| AI systems | Workspace providers, models, custom agents, MCP/RAG/workflow components, dependency graph, evaluations |
| Monitoring | Manual and scheduled runs, repetitions, budgets, raw evidence, answer snapshots, latency, token and cost data |
| Usage | Workspace provider requests, normalized tokens, web searches, configured/provider-reported cost, pricing coverage and operation provenance |
| Intelligence | Visibility, share of voice, citations, entities, prompt demand, narratives, accuracy, safety and anomalies |
| Optimization | Technical/citability diagnostics, findings, recommendations, roadmap, approval, execution and rollback |
| Activation | Knowledge, evidence-backed content, machine artifacts, channels, publishing and verification |
| Simulation | Organic, ads, sponsored-agent, custom-agent, MCP/RAG and workflow scenarios; experiments and calibration |
| Performance | AI referral tracking, trends, campaign impact, attribution, source influence and product visibility |
| Operations | Alerts, reports, exports, scheduled delivery, share links, integrations, privacy and retention |
| External access | Workspace API keys, REST API, MCP, TypeScript SDK, browser/Next.js tracking SDK, GTM and WordPress |
Recommended reading order
- Platform overview
- Architecture and service topology
- Getting started
- Tenants, workspaces, projects, and targets
- Data model and lifecycle
- Providers and AI systems
- Configuration reference
- Research and monitoring
- Provider Usage and Cost Management
- Metrics and intelligence
- Diagnostics and Action Center
- Knowledge, content, channels, and publishing
- Simulation and experiments
- Tracking, impact, and attribution
- Tracking installation
- Brand, website, product, and campaign scenarios
- Integration selection guide
- Implementation and operations playbooks
- Domain service reference
- Dashboards, reports, and exports
- API, SDK, and MCP
- Security, privacy, and governance
- Deployment and configuration
- Testing and troubleshooting
Product boundary
The dashboard is the complete operational surface. Public APIs expose selected workspace-safe datasets and workflows; they do not mirror every internal dashboard mutation. Publishing and external actions require a configured connection, appropriate scope, approval, and policy result. A simulation is always labeled synthetic and never becomes an observation.