Unknown: Clarify target deployment model and scale #18

Closed
opened 2026-03-10 03:48:00 +00:00 by Mark · 0 comments
Owner

Question

The codebase has both single-user and multi-user features, but the target deployment model isn't clearly defined.

Current State

  • Multi-user auth exists (registration, login, tokens)
  • But default API key suggests single-user
  • RBAC mentioned in roadmap but not implemented
  • No clear distinction between personal vs team/enterprise use

Clarification Needed

  1. Primary use case:

    • Single developer local environment?
    • Small team shared instance?
    • Multi-tenant SaaS?
    • Enterprise on-premise?
  2. Scale expectations:

    • Concurrent sessions per user?
    • Total users per deployment?
    • Session duration expectations?
  3. Compliance requirements:

    • SOC2, HIPAA, GDPR?
    • Audit retention periods?
    • Data residency requirements?
  4. Deployment targets:

    • Docker Compose only?
    • Kubernetes support?
    • Cloud provider integrations?

Impact

These decisions will affect:

  • Architecture choices (shared vs isolated databases)
  • Security model complexity
  • Multi-tenancy implementation
  • Pricing/licensing model (if commercial)

Priority: High
Type: Unknown/Clarification Required

## Question The codebase has both single-user and multi-user features, but the target deployment model isn't clearly defined. ## Current State - Multi-user auth exists (registration, login, tokens) - But default API key suggests single-user - RBAC mentioned in roadmap but not implemented - No clear distinction between personal vs team/enterprise use ## Clarification Needed 1. **Primary use case:** - Single developer local environment? - Small team shared instance? - Multi-tenant SaaS? - Enterprise on-premise? 2. **Scale expectations:** - Concurrent sessions per user? - Total users per deployment? - Session duration expectations? 3. **Compliance requirements:** - SOC2, HIPAA, GDPR? - Audit retention periods? - Data residency requirements? 4. **Deployment targets:** - Docker Compose only? - Kubernetes support? - Cloud provider integrations? ## Impact These decisions will affect: - Architecture choices (shared vs isolated databases) - Security model complexity - Multi-tenancy implementation - Pricing/licensing model (if commercial) **Priority:** High **Type:** Unknown/Clarification Required
Mark closed this issue 2026-05-26 21:22:49 +00:00
Sign in to join this conversation.
No description provided.