Repository navigation
docs(cloud): state the celld tenancy boundary in the runtime decision - #588
Conversation
§7.8 offered a fully-managed celld tier as needing "no fork either — Apache-2.0, celld deploy works today". celld's own docs/security.md says it "is not safe for hostile multi-tenant use" and "one fleet runs one application… do not run code from mutually distrusting tenants in one fleet"; cell fencing protects storage consistency and is explicitly not an isolation boundary between hostile applications. Security fixes land on the latest release only. Left as written, that reads as a managed multi-tenant tier being a straightforward Later. It is not, and the reason is a cost model rather than a safety footnote: a managed tier is one fleet per tenant, per-tenant nodes and object store, no bin-packing across customers — which is most of the margin the own-the-runtime case was arguing for. It also forces continuous upgrades, since only the latest release is patched. Records the boundary, both consequences, and the two gates before a shared managed deployment is offered to anyone: an upstream isolation boundary we can point at, and a security-fix channel that can carry an SLA. Notes that self-host stays the honest tier precisely because it is single-tenant by construction, which is the shape celld supports. Raised in review on #582 and verified against celld's docs/security.md at v0.4.0 rather than taken from the review summary. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019dhrsvdiJJuDAMjmiKVrae
✅ Deploy Preview for lunorash ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Thank you for confirming the Contributor License Agreement! 🙏 |
|
Thank you for following the naming conventions! 🙏 |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 2 included reviews per hour; 0 remain after this review. WalkthroughThe cloud documentation adds a celld tenancy-boundary subsection. It describes current multi-tenant limitations, single-tenant self-hosting, per-tenant managed fleets, and requirements for shared managed deployment. ChangesCelld tenancy model
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to The documentation clarifies celld's single-tenant deployment boundary and requirements for any future shared managed offering. No merge-readiness risk remains. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Full details: Description checkExplanation The description follows the required template and clearly explains the documentation change, linked issues, test plan, checklist status, and reviewer notes. The CLA confirmation line is omitted, but the template allows organization members to omit it. Full details: Docstring CoverageExplanation No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.) ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## alpha #588 +/- ##
==========================================
- Coverage 79.85% 79.84% -0.01%
==========================================
Files 1579 1579
Lines 82323 82323
Branches 20410 20399 -11
==========================================
- Hits 65735 65732 -3
+ Misses 16021 16016 -5
- Partials 567 575 +8 🚀 New features to boost your workflow:
|
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Summary
Follow-up to #582 (already merged), addressing the one actionable review comment on it:
apps/cloud/MULTIPLATFORM.md§7.8 described a fully-managed celld tier without stating celld's tenancy boundary.celld's own
docs/security.mdsays it "is an alpha", "is not safe for hostile multi-tenant use", and "one fleet runs one application… do not run code from mutually distrusting tenants in one fleet". Cell fencing protects storage consistency and is explicitly not an isolation boundary between hostile applications. Security fixes land on the latest release only.§7.8 as merged said a managed fleet "needs no fork either — Apache-2.0,
celld deployworks today", which reads as a managed multi-tenant tier being a straightforward Later. It isn't, and the interesting part is a cost model rather than a safety footnote:Also records the two gates before a shared managed deployment is offered to anyone: an upstream isolation boundary we can point at, and a security-fix channel that can carry an SLA.
Area:
apps/cloud(documentation only). Related framework package:@lunora/platform-celld(#359).Linked issues
apps/cloud/MULTIPLATFORM.md)Test plan
Documentation only — one markdown file, no code, no schema, no dependency change. Nothing to execute beyond formatting.
pnpm exec prettier --check apps/cloud/MULTIPLATFORM.mdpassesdocs/security.mdat thev0.4.0tag directly, not from the review summaryChecklist
feat(scope): subject)apps/docs(orREADME.mdfor package-local docs) — this change is the doc; no user-facing docs affectedpackage.jsonfiles inpackages/*modified outside the touched packageproject.jsonhastype:packageand acategory:*tag — n/aNotes for reviewers
The substantive question is not the caveat but the one-fleet-per-tenant consequence. If that is right, it removes a large part of the economic case for ever operating our own fleet, which is worth disagreeing with explicitly if you read it differently.
Two things I deliberately did not do:
apps/cloud/ROADMAP.md. Its "optional fully-managed hosting (Later)" line is still accurate — it promises managed hosting, not managed-on-celld — but if you want the tenancy constraint surfaced in the public roadmap too, that is a separate call.#582 skipped this template; this one follows it.
🤖 Generated with Claude Code
https://claude.ai/code/session_019dhrsvdiJJuDAMjmiKVrae
Summary by CodeRabbit