ashlr pricing

June 3, 2026 · View on GitHub

Ship less context. Keep more money. ashlr Pro adds cloud genome sync, hosted retrieval, and cross-machine dashboards — on top of a free tier that is already a complete, production- grade token-efficiency layer.


Plans

FreeProTeam
Price$0 forever$12/mo or $120/yr (7-day trial, no card)$24/user/mo or $20/user/mo annual (min 3 users)
ForEvery developer, foreverOne developer who wants cloudEngineering teams
40 MCP toolsYesYesYes
34 slash commands + Codex skillsYesYesYes
Local genome + scribe loopYesYesYes
Per-session token ledgerYesYesYes
Tri-agent delegationYesYesYes
Savings benchmark + badgeYesYesYes
Codex + Cursor + Goose support¹YesYesYes
Cloud LLM summarizer (no Ollama required)NoYesYes
Cross-machine stats syncNoYesYes
Live auto-updating badgeNoYesYes
Leaderboard participationNoYesYes
Priority supportNoYesYes
Shared encrypted team genome (E2E + vclock conflict detection)NoNoYes
Org savings dashboardNoNoYes
Policy packs + pushed hook configNoNoYes
Genome diffs on PRsNoNoYes
SSO + SCIMNoNoYes
Audit log + SOC 2 evidence exportNoNoYes
CTAStart freeUpgradeContact sales

Enterprise (on-prem, private inference, dedicated SLA): contact sales.

¹ Codex has first-class plugin, MCP, skills, and nudge-first hooks. Cursor and Goose register the ashlr MCP server only. Claude-only extras include auto redirects, status line, slash commands, and OAuth bootstrap.


Detailed feature list

Free — everything you need as an individual

  • 40 MCP tools: ashlr__read, ashlr__grep, ashlr__edit, ashlr__edit_structural (v2: Unicode + cross-file + extract-function with return-value detection), ashlr__multi_edit, ashlr__glob, ashlr__webfetch, ashlr__ask, ashlr__diff, ashlr__diff_semantic, ashlr__sql, ashlr__bash (+ _start/_tail/_stop/_list), ashlr__tree, ashlr__http, ashlr__logs, ashlr__orient, ashlr__test, ashlr__ls, ashlr__flush, ashlr__savings, ashlr__pr / ashlr__pr_comment / ashlr__pr_approve, ashlr__issue / ashlr__issue_create / ashlr__issue_close (v1.18 GitHub write ops), and the three ashlr__genome_* tools.
  • 34 Claude Code slash commands including /ashlr-help, /ashlr-dashboard, and /ashlr-tour, plus Codex workflow skills for doctor checks, savings, genome refresh, efficient tools, and parallel exploration.
  • Local genome with automatic propose/consolidate loop and TF-IDF retrieval.
  • Optional local Ollama semantic search.
  • Per-session atomic token ledger with fidelity confidence footers on every compressed output.
  • Animated status line with gradient sweep and activity pulse.
  • Calibration harness and reproducible benchmark against your own codebase.
  • Codex packaging lives at .codex-plugin/plugin.json; Cursor and Goose ports are documented in ports/README.md.
  • 794 passing tests, MIT license, telemetry off by default, forkable.

Pro — cloud for one developer

Everything in Free, plus:

  • Cloud LLM summarizer — removes the local Ollama requirement. Genome summarization runs on hosted infrastructure with the same 5s timeout and SHA-256 cache you already rely on.
  • Cross-machine stats sync — your per-session ledger syncs across machines so /ashlr-dashboard reflects your real history, not just the current session.
  • Live badge — the /ashlr-badge SVG URL auto-updates. Embed it in your README and it always shows current savings without re-running.
  • Hosted embedding retrievalashlr__grep uses a cloud pgvector index refreshed on every push, falling back to Ollama and then TF-IDF. Material quality improvement on repos with more than 5,000 files.
  • Leaderboard — opt-in comparison of savings percentiles across repos and models.
  • Priority support — response within one business day.

Team — shared context for engineering teams

Everything in Pro, plus:

  • Shared encrypted team genome — one authoritative genome per repo, encrypted end-to-end (AES-256-GCM) so the server never sees plaintext. Vclock metadata enables automatic conflict detection across concurrent edits; concurrent writes are surfaced via /ashlr-genome-conflicts for human resolution. (CRDT auto-merge is on the roadmap.)
  • Org savings dashboard — aggregate view of every seat's per-session ledger, deduped per-repo, visible to team admins.
  • Policy packs — centrally authored allow/deny lists for ashlr__bash, ashlr__sql, and destructive operations, compiled into hook configs pushed to every seat automatically.
  • Genome diffs on PRs — GitHub App posts proposed genome mutations alongside every code diff. Knowledge review as part of code review.
  • SSO + SCIM — WorkOS integration for identity management.
  • Audit log — append-only log of every non-read MCP tool call with commit linkage. Exportable for SOC 2 evidence.

Enterprise

On-prem deployment of the full Pro/Team stack in your own infrastructure. Private inference endpoint (any OpenAI-compatible API). Dedicated support engineer, named SLA, custom genome spec. Get in touch.


FAQ

Is the free tier crippled?

No. Never. The free tier ships 40 MCP tools, 34 slash commands, Codex skills, the full genome scribe loop, per-session token accounting, a calibration harness, and a benchmark suite. It is the product. Pro adds cloud infrastructure for developers who need it — it does not remove or degrade anything in the free tier. The MIT license means you can audit every line and fork if you disagree.

Can I self-host everything?

Yes. The free tier is entirely local — no account, no outbound calls unless you opt in. The Pro cloud features (hosted embedding index, genome sync, stats endpoint) are conveniences, not requirements. If you want to run the full stack on your own infrastructure, the Enterprise tier covers exactly that. The genome format is a public spec; nothing is locked to our servers.

What data leaves my machine?

On the free tier: nothing. The genome lives in .ashlrcode/genome/, the stats ledger lives in ~/.ashlr/stats.json, and no data is sent anywhere. On Pro, only what you explicitly opt into: the stats ledger sync and the cloud summarizer calls. Both are toggleable. We do not log prompt content, file contents, or anything identifiable beyond aggregate token counts and repo-level metadata. On Enterprise/on-prem, nothing leaves your VPC.

How is this different from WOZCODE?

ashlr is open source (MIT). WOZCODE is a closed-source commercial product. With ashlr you can read the compression logic, fork the genome format, run the benchmark against your own codebase, and verify the savings claims yourself. The Pro tier adds hosted infrastructure on top of that auditable base — it does not replace the open-source plugin with a black box.

What happens if I downgrade from Pro or Team to free?

Graceful. The plugin detects the missing or expired license on next session start and silently routes to free-tier fallbacks. The cloud LLM summarizer falls back to local Ollama (if installed) and then to the built-in snip compactor. Genome sync pauses; your local genome is untouched. The badge becomes static. No features break; no data is deleted. You can re-upgrade at any time and cloud sync resumes from where it left off.

Can I see it work before paying?

Yes. The /ashlr-tour skill ships free and runs a 30-second to 60-second scripted showcase of token savings on your actual codebase. Run /ashlr-benchmark for a reproducible, auditable savings number against your repo before spending a dollar.

Do you use my code or prompts to train models?

No. Not ever. Session content, file contents, and prompt text are not retained for training. The only data we collect on Pro is aggregate token counts and repo-level metadata for the savings ledger — nothing that identifies code or conversations. This is a hard commitment, not a policy that can be quietly revised in a ToS update.

How does billing work? Do you support invoicing or POs?

Pro and Team tiers are billed via Stripe (card). Annual plans are invoiced upfront. For purchase orders, net-30 terms, or invoicing workflows, contact support@ashlr.ai — standard PO terms are available for Team and Enterprise.

What is the minimum team size for the Team tier?

Three users. At fewer than three seats the overhead of shared genome sync and org policy management adds more complexity than it saves. Solo developers and pairs are better served by Pro.

Will pricing change?

Pro at $12/month and Team at $24/user/month are the launch prices. Existing subscribers are grandfathered at the price they signed up at. We will not raise prices on existing subscriptions without at least 90 days notice and an opt-out window.


Full feature comparison

FeatureFreeProTeam
MCP tools (40 total)AllAllAll
Slash commands (31 total)AllAllAll
Genome scribe loopYesYesYes
TF-IDF retrievalYesYesYes
Local Ollama semantic searchYesYesYes
Hosted embedding retrievalNoYesYes
Per-session token ledgerYesYesYes
Fidelity confidence footersYesYesYes
Animated status lineYesYesYes
Calibration harnessYesYesYes
Savings benchmarkYesYesYes
Static savings badgeYesYesYes
Live auto-updating badgeNoYesYes
Cloud LLM summarizerNoYesYes
Cross-machine stats syncNoYesYes
Leaderboard participationNoYesYes
Codex + Cursor + Goose support¹YesYesYes
Priority supportNoYesYes
Shared encrypted team genome (E2E + vclock conflict detection)NoNoYes
Org savings dashboardNoNoYes
Policy packsNoNoYes
Genome diffs on PRsNoNoYes
SSO + SCIMNoNoYes
Audit logNoNoYes
SOC 2 evidence exportNoNoYes
On-prem deploymentNoNoEnterprise
Private inference endpointNoNoEnterprise
Dedicated support + SLANoNoEnterprise

¹ Codex has first-class plugin, MCP, skills, and nudge-first hooks. Cursor and Goose register the ashlr MCP server only. Claude-only extras include auto redirects, status line, slash commands, and OAuth bootstrap.


Open source forever

ashlr is MIT-licensed. The full plugin — all 40 tools, all 34 slash commands, the genome format, the scribe loop, the benchmark harness, and every line of compression logic — is and will remain open source. No feature that exists in the free tier today will ever move behind a paywall. The Pro and Team tiers add new capabilities that require infrastructure to deliver; they do not erode what is already free.

You are welcome to fork, audit, and self-host. If you find a bug, open an issue. If you find a security issue, please disclose it privately first. The genome spec is published as a community asset — we want the format to outlast any particular implementation, including this one.

If the paid tiers succeed, the open-source project gets better maintained. If they don't, the plugin stays free and useful regardless. That is the intended relationship between the two, and it is not going to change.