简体中文
EnglishWhere to Find jcode Pricing, Enterprise Options, and Documentation
Updated
jcode's official site links directly to a Pricing page at https://jcode.sh/pricing, alongside Docs and Enterprise entries in the main navigation. The project is open-source and written in Rust, with source code and full commit history available on GitHub. If you want to check cost, evaluate an enterprise arrangement, or read the documentation, those three links on jcode.sh are the starting points — but note that the site content available here does not state actual prices, plan tiers, or what the Enterprise option includes, so you will need to open those pages to get specifics.
Where each resource lives
| What you need | Where to go | What is confirmed |
|---|---|---|
| Pricing | https://jcode.sh/pricing | A dedicated Pricing page exists and is linked from the homepage navigation |
| Enterprise options | "Enterprise" link in the site navigation | An Enterprise entry is present; its contents are not described in the available page content |
| Documentation | "Docs" link in the site navigation | A Docs entry is present |
| Source code and history | GitHub (linked from the site) | The project is open-source; full commit history is viewable on GitHub |
| Install command | Homepage | `curl -fsSL https://jcode.sh/install |
The homepage also lists macOS, Linux, and Windows as supported platforms, and notes a desktop app in beta. A "justrust" link and a GitHub link appear alongside the other navigation entries, and the page states the project is backed by Combinator.
What the available content does not tell you
The page evidence contains no prices, no plan names, no billing model, and no description of what Enterprise adds. It also does not say whether any tier is free. Treat the Pricing and Enterprise pages themselves as the only reliable sources for those answers — do not assume a free tier or a paid-only model from the presence of a pricing link alone.
A practical way to check
- Open https://jcode.sh/pricing and read the plan list. Look for whether a free or open-source tier is named separately from paid tiers.
- Open the Enterprise link from the same navigation bar. Check what it covers — typically support, deployment, or compliance terms — rather than assuming it is only a larger seat count.
- Open Docs for installation and usage detail. The install command on the homepage is
curl -fsSL https://jcode.sh/install | bash, which pipes a remote script into bash; if you prefer to inspect before running, fetch the script first and read it. - Go to the GitHub repository for the source, issue tracker, and full commit history — useful when you want to verify claims about performance or check release activity.
Why the performance claims matter to this decision
The homepage frames jcode around a "multi-agent bottleneck": heavy workflows stall when the harness itself is slow or memory-hungry. The published benchmarks compare memory per additional session and time to first input across several tools, with jcode listed at roughly 10.4 MB extra RAM per interactive session and 48.7 ms to first input, against figures in the hundreds of megabytes and hundreds of milliseconds for the other tools shown. These numbers are attributed to specific versions (jcode v0.92.14, Claude Code 2.1.267) and a stated measurement method, so they are worth reading on the page rather than taking secondhand. If your reason for checking pricing is deciding whether to run many parallel agents, the resource cost per session is the number that determines how far your existing hardware goes.
Bottom line
Start at jcode.sh for the three navigation entries — Pricing, Enterprise, and Docs — and use the GitHub link for source and history. The available site content confirms these destinations exist and that the project is open-source and Rust-based, but it does not confirm any price, tier, or enterprise term. Verify those on the linked pages before making a cost decision.