Skip to content

docs(cloud): state the celld tenancy boundary in the runtime decision - #588

Merged
prisis merged 1 commit into
alphafrom
docs/celld-tenant-boundary
Sep 3, 2026
Merged

prisis merged 1 commit into
alphafrom
docs/celld-tenant-boundary

Conversation

@prisis

@prisis prisis commented Sep 3, 2026 •

Copy link
Copy Markdown
Member

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.md says 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 deploy works 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:

  • A managed tier is one fleet per tenant, not one fleet — 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.
  • Self-host stays the honest tier, precisely because it is single-tenant by construction — the customer's fleet runs the customer's app, which is the shape celld supports.

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

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.md passes
  • Claims verified against celld docs/security.md at the v0.4.0 tag directly, not from the review summary
  • Reviewer re-read of §7.8 for whether the two gates are the right two

Checklist

  • Commit messages follow the Conventional Commits style (feat(scope): subject)
  • Added or updated tests covering the change — n/a, documentation only
  • Updated relevant docs in apps/docs (or README.md for package-local docs) — this change is the doc; no user-facing docs affected
  • No package.json files in packages/* modified outside the touched package
  • If a new package was added: project.json has type:package and a category:* tag — n/a
  • If migration impact: noted upgrade steps in the PR description and changelog entry — n/a

Notes 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:

  • I did not soften the decision in row 8. This corroborates it rather than changing it.
  • I did not touch 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

  • Documentation
    • Added guidance on celld’s current tenancy and security boundaries.
    • Clarified that deployments should use one fleet per application or tenant, with self-hosting as the current single-tenant option.
    • Documented prerequisites for offering shared managed deployments, including stronger isolation guarantees and an ongoing security-fix channel.

§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
@netlify

netlify Bot commented Sep 3, 2026 •

Copy link
Copy Markdown

✅ Deploy Preview for lunorash ready!

Name Link
🔨 Latest commit 4bbc2c1
🔍 Latest deploy log https://app.netlify.com/projects/lunorash/deploys/6a999aa214b2910008d8680f
😎 Deploy Preview https://deploy-preview-588--lunorash.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

@github-actions

github-actions Bot commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

Thank you for confirming the Contributor License Agreement! 🙏

@github-actions

github-actions Bot commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

Thank you for following the naming conventions! 🙏

@coderabbitai

coderabbitai Bot commented Sep 3, 2026 •

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Team

Run ID: 945aa50b-c4a2-46be-b6ae-af0eb12f08f7

📥 Commits

Reviewing files that changed from the base of the PR and between 19dbb78 and 4bbc2c1.

📒 Files selected for processing (1)
  • apps/cloud/MULTIPLATFORM.md

Included review availability: Your plan provides up to 2 included reviews per hour; 0 remain after this review.


Walkthrough

The 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.

Changes

Celld tenancy model

Layer / File(s) Summary
Document celld tenancy constraints
apps/cloud/MULTIPLATFORM.md
Documents celld's alpha status, single-application fleet model, latest-release security fixes, per-tenant managed fleets, self-hosting, and gates for shared deployment.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to 4bbc2

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)
Check name Status Explanation
Description check ✅ Passed 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 t…
Title check ✅ Passed The title is concise, conventional-commit formatted, and accurately identifies the documentation change to the celld tenancy boundary in the runtime decision.
Docstring Coverage ✅ Passed 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…
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Full details: Description check

Explanation

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 Coverage

Explanation

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)
  • Create PR with unit tests
  • Commit unit tests in branch docs/celld-tenant-boundary

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@codecov-commenter

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 79.84%. Comparing base (19dbb78) to head (4bbc2c1).
⚠️ Report is 12 commits behind head on alpha.

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     

see 3 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@prisis
prisis merged commit f58c5d5 into alpha Sep 3, 2026
53 checks passed
@prisis
prisis deleted the docs/celld-tenant-boundary branch September 3, 2026 18:35
@github-actions

github-actions Bot commented Oct 3, 2026

Copy link
Copy Markdown
Contributor

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.
Please note this issue tracker is not a help forum. We recommend using our GitHub Discussions tab for questions.

@github-actions github-actions Bot locked as resolved and limited conversation to collaborators Oct 3, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants