Skip to content

feat(site): Mitos vs CubeSandbox comparison page#69

Open
stubbi wants to merge 1 commit into
mainfrom
feat/compare-cubesandbox
Open

feat(site): Mitos vs CubeSandbox comparison page#69
stubbi wants to merge 1 commit into
mainfrom
feat/compare-cubesandbox

Conversation

@stubbi

@stubbi stubbi commented Jul 3, 2026

Copy link
Copy Markdown
Contributor

What

Adds CubeSandbox (TencentCloud, Apache-2.0, open-sourced April 2026) as a competitor entry in src/data/competitors.ts, generating /compare/cubesandbox and its card on /alternatives.

Positioning notes

  • Opens and closes on the outcome we own: a warm fleet forked from one running machine. CubeCoW is snapshot/clone/rollback from saved state, not a live fork; stated factually.
  • Ties conceded fast: both Apache 2.0, both own-kernel microVMs.
  • Wins: live fork of running memory, Kubernetes-native CRDs vs their standalone control plane (own scheduler, node agents, Redis state store), Firecracker production pedigree vs a new RustVMM-based VMM, reproducible benchmarks vs vendor charts.
  • Their numbers are labeled as their figures (sub-60 ms cold start, hundred-millisecond clone); ours stay the reproducible ~27 ms / ~3 MiB set. Nothing fabricated.

Verification

  • npm run build: 38 pages, dist/compare/cubesandbox.html generated, listed on /alternatives.
  • npm test green; no em or en dashes in the copy.

Related: mitos-run/mitos#658 and mitos-run/mitos#659 came out of the same competitor teardown.

🤖 Generated with Claude Code

Summary by CodeRabbit

  • New Features
    • Added a new competitor comparison page for CubeSandbox, including overview copy, feature comparisons, and FAQs.
    • Expanded the comparison content to highlight how CubeSandbox differs in cloning and isolation approaches.

Adds CubeSandbox (Tencent, open-sourced April 2026) to competitors.ts,
which generates /compare/cubesandbox and lists it on /alternatives.
Positioning per .agents/product-marketing.md frame rules: lead with the
fleet-from-a-running-machine outcome; concede the Apache-2.0 and
own-kernel ties in one line; their figures labeled as theirs
(sub-60 ms cold start, hundred-millisecond CubeCoW clone); wins are
live fork vs snapshot clone, Kubernetes-native CRDs vs a standalone
Redis-backed control plane, and Firecracker pedigree plus reproducible
benchmarks vs vendor charts.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Signed-off-by: Jannes Stubbemann <jannes.stubbemann@gmail.com>
@coderabbitai

coderabbitai Bot commented Jul 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: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 50ee9019-8c06-4b7b-a826-13334afa0654

📥 Commits

Reviewing files that changed from the base of the PR and between ed4a944 and d012b77.

📒 Files selected for processing (1)
  • src/data/competitors.ts

📝 Walkthrough

Walkthrough

A new CubeSandbox entry was added to the competitors array in src/data/competitors.ts, including metadata fields, comparison rows, sections, mitosWins statements, and FAQs describing differences between CubeSandbox and Mitos.

Changes

CubeSandbox competitor data

Layer / File(s) Summary
CubeSandbox competitor entry
src/data/competitors.ts
New CubeSandbox object added to competitors array with metadata, comparison rows, sections, mitosWins statements, and FAQs contrasting snapshot cloning vs. live fork approaches.

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

Possibly related issues

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly summarizes the main change: adding a Mitos vs CubeSandbox comparison page.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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.
✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/compare-cubesandbox

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

@greptile-apps

greptile-apps Bot commented Jul 3, 2026

Copy link
Copy Markdown

Greptile Summary

This PR adds CubeSandbox to the competitor comparison data. The main changes are:

  • Adds a cubesandbox competitor entry in src/data/competitors.ts.
  • Provides copy for the /compare/cubesandbox page.
  • Adds comparison rows, sections, wins, and FAQs used by the existing alternatives and comparison templates.

Confidence Score: 5/5

Safe to merge with minimal risk.

The change is a single data-only addition that follows the existing Competitor shape and uses valid row/cell values.

No files require special attention.

T-Rex T-Rex Logs

What T-Rex did

  • Validated the CubeSandbox compare-page flow; the path moved from a 404 Page not found to a 200 response, the title updated to 'Mitos vs CubeSandbox: live fork vs snapshot clones', and the CubeSandbox comparison UI rendered; no contract mismatch was found for the stated validation objective.
  • Validated the alternatives flow by comparing the base capture (found=0, linkCount=0) with the head capture (found=1, linkCount=1) and confirmed all requested blurb checks passed.

View all artifacts

T-Rex Ran code and verified through T-Rex

Important Files Changed

Filename Overview
src/data/competitors.ts Adds a complete CubeSandbox competitor entry for the existing data-driven comparison and alternatives pages.

Reviews (1): Last reviewed commit: "feat(site): Mitos vs CubeSandbox compari..." | Re-trigger Greptile

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