Getting Started
For beta testers: sign up, complete onboarding, and start tracking AI visibility in minutes. For developers: explore the implementation patterns.
Beta Testers — Start Here
- Create an account at /auth/sign-up. A personal workspace is created automatically.
- Complete the 3-step onboarding (profile, workspace, optional team invites).
- Go to Settings → AI Providers and add an OpenRouter key (or direct keys).
- Open Monitor, add 5–10 brand-relevant prompts, and run visibility checks.
- Explore Models, Competitors, and the dashboard.
Full step-by-step instructions, troubleshooting, and invite flows are in the Beta Testing Guide that ships with the repository (docs/BETA_TESTING_GUIDE.md).
What you get out of the box
- Multi-tenant auth + organization plugin (Better Auth)
- Strict org scoping on every query and server action
- Design system (3 themes + dark, semantic tokens, chart primitives)
- Dashboard shell, notifications, and a tool-calling workspace chat assistant
- Two-tier deletion (scheduled + grace, immediate via email token)
- AI with prompt versioning, usage metering, and per-org budgets
- Jobs, exports, webhooks (Stripe pattern), R2 presigned storage
Explore the live surfaces
After you sign up you land in a personal workspace. The dashboard, Monitor, Settings, Notifications, and Chat are all live surfaces — and you join the read-only showcase workspace, so there is real data to explore before your first scan.
The /dev/visual route is the component gallery — the single source of truth for how every primitive should look and behave across themes. It ships with self-hosted and local installs (hidden on this hosted showcase).
Next steps (developers)
Running AEO Explorer yourself — locally or self-hosted:
- Go through Setup and get a clean local environment running.
- Read Tenancy & Organizations to internalize the golden rules of org isolation.
- Skim Production before deploying to your own infrastructure.