All Zooly applications use subdomains under the zooly.ai apex domain. The following domains are used across environments:
| Domain | Purpose | Local Port |
|---|---|---|
zooly.ai | Public website and landing pages | 3005 |
auth.zooly.ai | Single entrypoint for authentication across all Zooly applications | 3003 |
app.zooly.ai | Main application for authenticated users and Experiences (mini-apps) | 3004 |
docs.zooly.ai | Documentation application | 3006 |
Local Development: When running applications locally, it's recommended to use the suggested ports listed above. If you need to use different ports, make sure to update the corresponding URLs in your .env.local file.
See setting up local environment for detailed setup instructions.
auth.zooly.ai - Single entrypoint for all authentication across all Zooly applications (localhost:3003)zooly.ai - Public-facing content application for landing pages, marketing materials, and other non-authenticated contentapp.zooly.ai - Full-featured application for authenticated users and Experiences (mini-apps)app.zooly.ai - Shared backend API for all applications, handling read/write operationsapi-readonly.zooly.ai - Read-only API service for statistics and metricsSeveral applications use reverse proxy routing to provide dedicated domains while maintaining a single deployment:
merch.zooly.ai - Routes to app.zooly.ai/merch-appphotobomb.zooly.ai - Routes to app.zooly.ai/photobomb-appbackstage.zooly.ai - Routes to app.zooly.ai/backstage-appBenefits of this approach:
dev.zooly.ai/merch-app without requiring separate domain deploymentsThe product applications under *.zooly.ai share the same authentication session, providing seamless user experience across domains. The machine agent at z-claw.zooly.ai is separate and does not use that login.
stage.zooly.ai - Staging environmentdev.zooly.ai - Development environmentz-claw.zooly.ai - The machine BizDev's agent (codex/Claude) can hand work to. It does not use the shared app login. See Z-Claw.