Skip to content

docs(roadmap): multi-tenancy (organizations) workstream + fail2ban ops follow-up#68

Merged
Isonimus merged 1 commit into
mainfrom
docs/roadmap-multitenancy-ops
Jun 18, 2026
Merged

docs(roadmap): multi-tenancy (organizations) workstream + fail2ban ops follow-up#68
Isonimus merged 1 commit into
mainfrom
docs/roadmap-multitenancy-ops

Conversation

@Isonimus

Copy link
Copy Markdown
Contributor

Records two future items per discussion:

  • Multi-tenancy (organizations layer) — the model today is single-org/multi-project with a global-superuser owner (canViewProject returns true for any owner on any project). Correct for self-host; unsafe for a multi-customer hosted SaaS (no company boundary, no billing root, no signup). Plans an organizations tenant layer with org-scoped owner + projects/admins under an org, as the prerequisite for hosted Phase 7. Self-host stays a single auto-created org (no behaviour change), mirroring the migration-009 role backfill.
  • fail2ban ops follow-up on scent-prod (ignoreip allowlist + relaxed jail) — the launch-day jail self-banned the admin after a mistyped key passphrase.

…2ban ops follow-up

- Multi-tenancy: today's model is single-org/multi-project with a global-superuser
  owner (fine for self-host, unsafe for a multi-customer hosted SaaS). Plan an
  organizations layer (org-scoped owner, projects/admins under an org, billing root)
  as the prerequisite for hosted Phase 7. Self-host stays a single auto-created org.
- Ops: soften fail2ban on scent-prod + add an ignoreip allowlist (the launch jail
  self-banned the admin after a mistyped passphrase).
@Isonimus Isonimus merged commit 490502d into main Jun 18, 2026
4 checks passed
@Isonimus Isonimus deleted the docs/roadmap-multitenancy-ops branch June 18, 2026 14:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant