Get your eng team in sync, on top of Linear.
We're building Lake: a layer over Linear and GitHub that checks tickets against what actually shipped, keeps blockers moving, and puts a cost on trade-offs before you commit. It's an early prototype, and we're looking for a handful of teams to help shape it.
This opens a public GitHub discussion; share only what you're happy to have public.
What we're building
- Ticket vs. reality. Will flag tickets whose status doesn't match the PRs, CI runs and deploys behind them, with the evidence linked.
- Blocker loop. Every blocker will get an owner and an agreed date, with follow-ups until it's cleared.
- Trade-off planner. A new request will turn into scenarios (what moves, how much delay, engineering and AI cost) before you approve it.
Lake is designed to sit on top of Linear, not replace it, so there's nothing to migrate. No integrations are live yet.
Start today, free
- lake-gate: a plan-approval gate for AI-coding teams.
- lake-meter: a per-step model and $ estimate for Claude Code plans, plus a per-run cap that stops and asks.
Both are open source (MIT), with no Lake account or server: lake-meter runs fully on your machine, lake-gate runs in your repo and on GitHub.
Who it's for
Heads of Engineering and team leads with 5–30 engineers on Linear and GitHub who ship with Claude Code or Cursor.
What design partners get
- Early access as each piece comes together.
- A direct line to the people building it.
- A real say in what we build next.
Joining the list is free and commits you to nothing.
This opens a public GitHub discussion; share only what you're happy to have public.