Mirror: docs: remove Enterprise pricing, direct users to contact sales (#5807)#6
Mirror: docs: remove Enterprise pricing, direct users to contact sales (#5807)#6jeremylongshore merged 8 commits intomainfrom
Conversation
Replace all Enterprise tier pricing references ($150/user/month, $3588/ent seat) with 'Contact Sales' language and link to https://kilo.ai/contact-sales. Teams pricing is unchanged.
Co-authored-by: kiloconnect[bot] <240665456+kiloconnect[bot]@users.noreply.github.com>
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ✨ 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 |
Summary of ChangesHello @jeremylongshore, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request updates the public documentation to reflect a change in the presentation of Enterprise tier pricing, moving from a fixed public price to a "Contact Sales" model. Additionally, it removes an outdated internal architectural document related to annual billing. Highlights
Changelog
Activity
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
|
Failed to generate code suggestions for PR |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request successfully removes the public-facing Enterprise pricing, replacing it with a 'Contact Sales' link, and deletes an obsolete internal architecture document, aligning with the intended changes. I've identified a minor formatting issue in one of the documentation files that could affect list rendering.
|
|
||
| 1. **Create organization** at [app.kilocode.com](https://app.kilocode.com) | ||
| 2. **Subscribe to Teams ($15/month)** or **Enterprise ($150/month)** | ||
| 2. **Subscribe to Teams ($15/user/month)** or **Enterprise ([Contact Sales](https://kilo.ai/contact-sales))** |
There was a problem hiding this comment.
There's an extra leading space in this list item which will cause it to be rendered as an indented sub-item. To maintain consistent formatting with the rest of the numbered list, this space should be removed.
| 2. **Subscribe to Teams ($15/user/month)** or **Enterprise ([Contact Sales](https://kilo.ai/contact-sales))** | |
| 2. **Subscribe to Teams ($15/user/month)** or **Enterprise ([Contact Sales](https://kilo.ai/contact-sales))** |
|
@coderabbitai review |
✅ Actions performedReview triggered.
|
jeremylongshore
force-pushed
the
main
branch
from
4231140 to
fa13626
Compare
Review: kilocode Kilo-Org#5807
Checklist
Findings🔴 Dangling references to deleted
|
| Check | Result |
|---|---|
| Build Markdoc Site | PASS |
| compile | PASS |
| check-translations | PASS |
| unit-test | PASS |
| test-extension (ubuntu) | PASS |
| test-extension (windows) | PASS |
| test-webview (ubuntu) | PASS |
| test-webview (windows) | PASS |
| build-cli | PASS |
| test-cli | PASS |
| test-jetbrains | PASS |
| Vercel | SKIP (auth required) |
Code Snippets
# apps/kilocode-docs/pages/collaborate/index.md (clean)
-- **Enterprise ($150/user/month)** — Model controls, audit logs, SSO, dedicated support
+- **Enterprise ([Contact Sales](https://kilo.ai/contact-sales))** — Model controls, audit logs, SSO, dedicated support# apps/kilocode-docs/pages/contributing/architecture/annual-billing.md (deleted)
# 67 lines removed — internal architecture spec with pricing details// apps/kilocode-docs/lib/nav/contributing.ts — DANGLING REFERENCE (not in PR)
{
href: "/contributing/architecture/annual-billing",
children: "Annual Billing",
},Verdict
COMMENT - The pricing text replacements are correct and the annual-billing.md deletion is appropriate (removes internal pricing details from public docs). However, the deletion leaves 3 dangling references — most critically a nav entry in contributing.ts and a doc link in features.md that will produce broken links. Recommend adding these cleanups before merge. The indentation nit in migration.md is minor.
Review Journal: kilocode Kilo-Org#5807
SummaryThis PR replaces Enterprise pricing ($150/user/month) with "Contact Sales" links across 2 docs pages and deletes an internal architecture spec ( First ImpressionsGenerated by kiloconnect bot from a Slack thread with Alex Gold. The What I expected: simple text find-and-replace across pricing pages. What I Looked At
AnalysisThe pricing text changes are cleanTwo files get simple replacements: index.md: migration.md: Same pattern, but also fixes "$15/month" → "$15/user/month" (adding the missing "/user" qualifier). Bonus accuracy fix. However, an extra leading space was introduced on the The file deletion leaves broken links
The Markdoc build passes because it doesn't validate link targets at build time. These broken links would only be caught by a link checker or manual navigation. The deleted file was sensitiveThe deleted
This content shouldn't be in public docs. The deletion is correct — but ideally the cleanup references should be in the same PR. VerificationAll CI checks pass: Note: Build passes despite dangling references — Markdoc build validates syntax, not link integrity. Diagramsgraph TD
subgraph "PR #5807 Changes"
A["index.md<br>✅ $150 → Contact Sales"]
B["migration.md<br>🟡 $150 → Contact Sales<br>(+ indentation nit)"]
C["annual-billing.md<br>🔴 DELETED"]
end
subgraph "Not Updated (Broken Links)"
D["contributing.ts<br>❌ Nav entry → 404"]
E["features.md<br>❌ Table link → 404"]
F["mappingplan.md<br>⚠️ Reference → stale"]
end
C -.->|"references<br>not cleaned up"| D
C -.->|"references<br>not cleaned up"| E
C -.->|"references<br>not cleaned up"| F
style A fill:#2d6a4f,stroke:#1b4332,color:#d8f3dc
style B fill:#e9c46a,stroke:#f4a261,color:#264653
style C fill:#9d0208,stroke:#6a040f,color:#fff
style D fill:#9d0208,stroke:#6a040f,color:#fff
style E fill:#9d0208,stroke:#6a040f,color:#fff
style F fill:#e9c46a,stroke:#f4a261,color:#264653
Bot Review Synthesis
Critical observation: Neither Gemini nor any bot caught the dangling reference issue. The broken links in Lessons Learned1. File deletions need cross-reference checks. When a PR deletes a file, always search the codebase for references to that file. Navigation configs, feature tables, and mapping docs can all break silently. This is a tier-1 check that should be in the review checklist. 2. Bots can't catch missing changes. AI reviewers analyze the diff. They don't ask "what else should have been in this PR?" Cross-reference validation — searching for imports, links, nav entries that point to deleted files — requires manual or Sourcegraph-style analysis. 3. Build passing ≠ links valid. The Markdoc site builds successfully even with broken internal links. This is a gap that a link-checking CI step would catch. Consider recommending a link checker for the docs build. 4. Bot-generated PRs may have gaps. This PR was built by kiloconnect from a Slack conversation. The bot correctly identified the pricing text to replace but didn't discover the nav and feature table references to the deleted file. Human + AI review catches what automated PR generation misses. 5. Sensitive content in public docs. The deleted Review #3 of 75 | Review methodology: AI PR Review Case Studies | Reviewed with GWI + Claude Code |
2 participants
Mirror of Kilo-Org#5807
This PR mirrors the upstream change for multi-AI review analysis.
Changes
Remove all public-facing Enterprise tier pricing references ($150/user/month) and replace with "Contact Sales" language. Deletes internal annual-billing architecture spec. Teams pricing ($15/user/month) unchanged.
Bot Review Checklist