Services

Expertise that funds
the open core.

lean-ctx is Apache-2.0 and free locally, forever. That is CI-enforced and non-negotiable. These engagements buy senior time, not features: rollout, integration and operations expertise from the people who build the engine.

Fixed-price packages

Three packages, no surprises.

Every package has a fixed scope, a fixed price range settled before we start, and a measurable outcome. Work that improves the engine lands upstream in the open core. You never pay for a fork.

Team Onboarding & Governance

CHF 6–12k fixed price · 2–4 weeks

Engineering orgs rolling lean-ctx out to 10–100+ developers.

  • Rollout plan for your IDE/agent mix (Cursor, Claude Code, Copilot, CI agents)
  • Token-budget & SLO policy tuned to your repos (budgets, alerts, dashboards)
  • Security review of your config: PathJail roots, shell allowlist, secret redaction
  • Savings baseline + signed-ledger reporting wired to your cost owner
  • Two enablement workshops (engineers + platform team), recorded

Outcome: a measured before/after savings report on your own repositories.

Request this package →

Custom Connector / Integration

CHF 5–15k fixed price · 2–6 weeks

Teams that need lean-ctx wired into internal systems or a custom agent.

  • A production connector (REST/GraphQL/DB/queue) through the provider pipeline
  • Consolidation into search, knowledge and cache: your data becomes context
  • Or: embedding lean-ctx in your own agent product via the versioned /v1 API + SDKs
  • Contract tests against the frozen surface, CI-ready
  • Handover session + runbook; code delivered under your license of choice

Outcome: your system shows up in ctx_semantic_search and survives engine upgrades (frozen /v1 contract).

Request this package →

Platform Retainer

CHF 1.5–4k per month · 3-month minimum, cancel monthly after

Teams running lean-ctx in production that want guaranteed expertise on tap.

  • Private support channel with a 1-business-day response SLA
  • Monthly savings & config review (read modes, budgets, cache hit rates)
  • Upgrade shepherding: RC validation against your workload before you ship it
  • Priority triage for issues that block your rollout (fix lands upstream, in the open core)
  • Quarterly roadmap session: your needs, argued honestly against the public roadmap

Outcome: someone who knows your setup answers within a business day, and fixes land upstream rather than in a fork.

Request this package →
Not ready for a package?

Run an 8-week guided pilot.

CHF 1.5–3k / month · 8 weeks · stops automatically unless you continue

We set lean-ctx up on two of your real repositories, define the success metric with your cost owner up front (tokens, latency, or developer time), and review the signed savings ledger together every two weeks. At the end you have a decision document with your own numbers, not ours.

  • Week 1: setup on real repos, baseline measurement, success metric agreed in writing
  • Weeks 2–7: rollout to the pilot group, biweekly ledger reviews, config tuning
  • Week 8: decision document with measured savings, costs, and an honest go/no-go recommendation
Request a pilot →
Rules of engagement

Read this before you email us.

Services never gate features.

Everything local is free forever (the local-free invariant is a frozen, CI-enforced contract). If your problem is solved by a config change, we will tell you in the first reply, for free.

Fixes land upstream.

Engine improvements from any engagement are released in the open core under Apache-2.0. You pay for prioritization and expertise, never for a private fork.

Honest numbers only.

Every claim we make in a pilot or onboarding is measured on your repositories with the signed savings ledger: reproducible by you, without us in the room.

Small by design.

This is a focused operation, not an agency. We take a small number of engagements per quarter; if capacity is full, you get a date, not a runaround.

Tell us what you are rolling out.

Two paragraphs about your team, your agents and your repos is enough. We reply within one business day with either a fit, a config tip, or a referral, whichever is true.