Skip to content
This repository was archived by the owner on Mar 31, 2026. It is now read-only.
This repository was archived by the owner on Mar 31, 2026. It is now read-only.

Explore multi-tenant Apollo with subscriptions and tenant-scoped access #207

Closed as not planned

Description

@codeacula

Apollo may eventually need to support multiple tenants/customers with subscription-backed access rather than only being a single privately managed assistant instance.\n\n## Why\n\n- allow people outside the initial test circle to subscribe and use Apollo\n- separate data, configuration, and access cleanly per tenant/workspace\n- create a path toward a hosted product model\n\n## Questions to answer\n\n- what is the tenant boundary: person, household, Discord server, workspace, or account?\n- how should billing/subscription state map to access control?\n- which configuration lives globally vs per tenant vs per person?\n- how should reminders, conversations, telemetry, and AI/provider usage be isolated?\n- what architectural changes are needed for auth, routing, storage, and admin UI?\n\n## Notes\n\nThis is intentionally parked as a future-facing design issue. It can be promoted into Release or a dedicated commercialization milestone later.\n

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions