Learn
What Sphere is, how it helps, and how it works
Sphere Desktop is a chat-first architect/orchestrator (Windows/macOS) for checked delivery against Architecture as Code - differentiated autonomy, equal-outcome ROI (tokens / scope / human interactions), a BA/Dev/Architect/QA control plane (Chat, Plans, Runs, Diagram), and a living SCAN blueprint. app.spherescan.io is the free SCAN whiteboard only - not the main product.
Assistants can also read the Markdown corpus at /llms.txt.
What is Sphere
Four-pillar narrative — differentiated autonomy, ROI shape, control plane, Architecture as Code.
How Sphere works
Blueprint metaphor and delivery loop from system model through plan, build, verify, and fix.
Sphere Desktop
Primary product — chat-first architect/orchestrator on Windows and macOS; Chat, Plans, Runs, Diagram; not the SCAN whiteboard.
SCAN open notation
Architecture-as-Code notation, what it describes, SCAN vs Sphere Desktop, where to try the free whiteboard.
Sphere vs a coding harness
Harness writes code vs Sphere delivers checked change; ROI KPI framework.
ROI and evaluation
Equal-outcome KPIs — tokens, scope, human interactions — and how to pilot.
Ways of working
BA, Dev, Architect, QA on one control plane; daily rhythm and habits.
Benefits by role
Value for BA, leaders, architects, developers, QA, product, founders, enterprises.
Capabilities
Functional capabilities with availability wording (available / in development / planned).
Autonomy and Autoplay
Delivery autonomy vs harness edit loops; Sphere-built-Sphere proof; human control.
Illustrative use cases
Example scenarios (not customer references or guarantees).
Trust and governance
Approvals, safety, deployment options, BYO model credentials (high level).
Plans and pricing structure
Plan structure without prices; point to spherescan.io or the team.
FAQ
Common product questions including autonomy, ROI, and persistent context.
Glossary
Plain-language definitions of Sphere terms.