Products & Platform Surface

1. What Conservatory Is

Conservatory is built to close the gap between finding website issues and shipping safer fixes. The current product centers on three connected ideas:

• Deterministic evidence first: semantic HTML, accessibility, technical SEO, and AEO readiness findings stay grounded in the analyzed page output
• One operating workflow: analyze a public URL, review the report, export what your team needs, then decide whether to stay manual or move into repository-backed remediation
• Review-first changes: Conservatory helps you prepare supported fixes, but you stay in control of what gets copied, accepted, or opened as a draft PR

Scope note: the current public scope is intentionally narrower than the long-term vision. The product today is optimized for deterministic website analysis, not for every possible automation or enterprise workflow.

2. Current Public Workflow

1. Run an analysis against a public URL from the dashboard
2. Review the report across semantic structure, accessibility signals, technical SEO, and AEO readiness
3. Use exports when you need JSON, Markdown, CSV, or PDF outputs for teammates or stakeholders
4. Open Manual Fix Mode to inspect deterministic fix previews from the analyzed markup
5. Connect GitHub when you want repository-backed review and draft PR creation on supported issue types

The current analysis scope is strongest on static HTML and SSR-friendly sites. That keeps the public workflow honest, fast enough to operate, and easier to support while the product hardens in production.

3. Live Now

3.1 Analysis and reporting

• Public URL analysis: analyze accessible websites without requiring a local setup
• Deterministic report categories: semantic HTML, accessibility, technical SEO, and AEO readiness
• Unison Metrics: one weighted score to summarize the report while the underlying findings remain the source of truth
• Exports: JSON, Markdown, CSV, and PDF are available in the current public workflow

3.2 Review-first remediation

• Manual Fix Mode: preview deterministic fix suggestions from the analyzed markup
• Free plan preview: Free can review supported manual fixes before upgrading
• Paid workflow: Starter, Premium, and Enterprise unlock Copy Code, GitHub-backed review, and draft PR creation
• Accepted patches only: draft PRs are created from the fixes you keep, and PRs never auto-merge

3.3 Plans, branding, and support

• Free: report review, exports, and default Conservatory branding
• Starter and Premium: the same core remediation workflow, plus custom branding on report surfaces and PDF exports
• Enterprise: a sales-assisted rollout, not a different product truth
• Billing fallback: if self-serve checkout does not open from Plan Management, the support backup path runs through support@conservatory.app

4. Planned for V1.1

V1.1 should be read as the next layer of refinement after the current public rollout, not as a second product with a different story. The likely improvements are:

• Broader supported remediation coverage: expand the list of issue types that can move cleanly through the review-first fix flow
• Stronger GitHub guidance: clearer repository setup, sync expectations, and remediation troubleshooting
• More polished report surfaces: cleaner summaries, better handoff copy, and sharper export ergonomics
• Clearer onboarding and billing touchpoints: reduce buyer confusion between report review, paid remediation, and support fallback paths

Important: these are near-term product improvements we can responsibly point toward, but they still depend on what users validate in production.

5. Planned After the Current Public Scope

Conservatory is meant to become more than the current public workflow. The long-term direction is real, but it should stay clearly separated from what ships today.

• Rendered-page analysis: deeper browser-based inspection for dynamic apps and more complex frontend behavior
• Public API: programmatic analysis and export workflows after the web product is stable
• CLI and GitHub Actions: CI-oriented automation once the core workflow is reliable enough to support it
• Broader collaboration: richer team workflows, automation controls, and larger rollout patterns over time

That future direction matters because Conservatory is not only a reporting tool. The product is heading toward an operating layer for website quality, but the current public rollout focuses on the narrowest version we can support well.

6. Plans and Packaging

Founders billing note: if self-serve checkout does not open from Plan Management, choose the target plan first and then email support@conservatory.app with your workspace ID, account email, billing email, and selected plan.

7. Who It's For

• Founders and solo operators: validate public marketing pages or launch-ready websites before shipping
• Agencies and consultants: run repeatable analyses and turn findings into cleaner handoffs or draft PR workflows
• Product and engineering teams: move from report review into accepted repository-backed fixes without auto-merging changes
• Teams that care about trust: use a narrower but more honest workflow now, rather than a broader platform that overpromises

Not the best fit yet: teams that need a public API today, CI gating on every commit, or guaranteed browser-rendered analysis for private authenticated applications.

8. One Platform. Nine Integrated Instruments.

Symphony is the orchestration platform brand. Inside it, the product lineup is structured as instruments: focused products that work alone today and compound together over time.

The strongest public story right now is simple: Anthology is the semantic and AI-first framework for modern and conversational interfaces, Conservatory is the flagship live product, Strauss AI is the ecosystem AI layer, and Unison Metrics is the scoring system already active in the workflow.

Together they support an analyze -> review -> improve -> re-check workflow. Conservatory tells you what to fix and why it matters, Unison Metrics summarizes health, Strauss AI helps explain and prioritize, and Anthology helps when the right answer is a cleaner semantic foundation for conversational interface work instead of a minimal patch.

9. Get Started

1. Start with a public URL and run a free analysis
2. Review the report and determine whether you only need exports or also want remediation support
3. Use Manual Fix Mode first, then connect GitHub when you want repository-backed review
4. Upgrade to Starter or Premium when you want Copy Code, accepted patches, and draft PR workflows
5. Use support@conservatory.app if billing or plan activation needs the support fallback path

• Read the docs: Documentation
• Create an account: Run Free Audit
• Contact support: support@conservatory.app