kadeep
The client a pipeline or an agent runs: sign-in, runs, localization, CI detection. No runtime dependencies. It does not make the ship call.
KaDeep Release Gate·Apache-2.0
Engineering release confidence.
A go or no-go for this commit, from the terminal, the pipeline, and the coding agent.
npx releasegate in CI. Get started free
KaDeep · Acme WebCheckout releasePull request 214
- Web checkoutliveguest pay
- Android APKbuildsame pay step
- iOS IPAbuildsame pay step
- Figma screensframesfull button
Release gate file
Name the release. Smoke, Checkout, and Localization ready are required. Mobile is advisory.
Acme Web checkout v2
Claude
Cursor
Codexreleasegate.yml
mode: shadowchecks:- name: Smoke- name: Checkout- name: Localization ready- name: Mobile
KaDeep · Acme Web · p_9a118f0499704752be72 · commit 8c3f2d1 · Pull request 214not run · 3 required checks · 1 advisory
Name the release
Acme sends the web checkout, the APK, the IPA, and the Figma screens. Codex stays on the gate. Smoke, Checkout, and Localization ready are required. Mobile is advisory.
How it works
From the pull request to a ship answer.
kadeep is the client: the CLI, the MCP server, and the library, with no runtime dependencies. releasegate sits on it and returns the go or no-go for this commit.
Pull request 214 walks the belt, from arrival to the ship answer.
releasegate
Policy and the verdict. It reads releasegate.yml, asks Studios to run the checks, and returns GO or NO-GO. It depends on kadeep.
Studios
Where the checks run, over HTTPS to api.kadeep.ai, on the team’s model key. The CLI sends no telemetry and never calls a model.
A run is a queued job. The CLI starts it and polls until it finishes. The suite never holds a request open.
01Start
Posts the checks named in releasegate.yml. Studios returns a job id and the request closes.
02Poll
Reads that job every few seconds, and once more if the connection drops.
03Report
Writes report.json, report.md, and junit.xml. Each check records pass or fail, the defect, and the time.
04Verdict
Exit 0 on GO. Exit 1 on NO-GO in enforce. Shadow writes the same report and exits 0. A person still ships.
The team records the verdict and exits 0 until that record matches their judgment, then they switch the same policy to enforce.
The files land in .releasegate. On GitHub they also land in the job summary, and a failing check is annotated on the change.
Integrations
Bring the agent you already run.
The agent and the pipeline read one commit and print the same go or no-go.
kadeep mcp
MCP over stdio. Suites, runs, defects, and the localization gate.
- Cursor
- Claude Code
- Codex
- Any MCP client
Acme Web · p_9a118f0499704752be72
AgentPay by card [DEFECT] · Expected "Order placed" to be visible
CINO-GO · 1/3 required checks passed · PR #214
The same project in CI
npx releasegate blocks the merge in enforce.
- GitHub Actions
- GitLab CI
- CircleCI
- Jenkins
- Buildkite
- Azure Pipelines
- Bitbucket
Sample report
What this commit’s gate report shows.
Smoke passed. Checkout failed on pay by card. hi-IN is 92% against a 100% bar. No-go: one of three required checks. A person still decides whether to ship.
Acme Web · commit 8c3f2d1 · pull request 214
One checkout sample. Not a customer total.
NO-GO
1 of 3 checks
- ✓ Smoke suite passed
- ✗ Checkout suite failed
- ✗ Localization check failed
Verdict
No-go. One of three required checks passed. Pay by card blocked checkout, and hi-IN at 92% missed the 100% bar. A person still makes the ship call.
2 min 12 sec
median
Live
- ✓ Smoke, 12 of 122 min 41 sec
- ✗ Checkout, 3 of 41 min 5 sec
Time to a verdict
Median time for the gate to answer on this commit. Smoke finished 12 of 12 checks. Checkout finished 3 of 4, and stopped where “Order placed” should have been visible.
12 more than yesterday
Quiet
Busy
Runs today
Suites and test cases the gate started today, twelve more than yesterday. Darker days had more runs. Weekends are drawn lighter.
Past 24 hours
1.9% of runs
1
Open defects
One defect is open: pay by card. Over the past 24 hours, 1.9% of runs failed. The mix is assertions, locale gaps, and job errors.
Past 30 days
96.2%
Checks passed
Share of checks that passed over the past 30 days. One failed check blocks the commit, which is why this one is still a no-go.
Past 24 hours
Model Context Protocol
Calls an agent made to this project in the past 24 hours: test cases, runs, defects, and localization. It saw the same pay-by-card defect the pipeline failed.
Month to date
Model spend
What Studios has spent on the team’s model key this month. Model spend only. The client never calls a model.
Past 24 hours
- Claude52%
- OpenAI27%
- Gemini13%
- Other8%
Model tokens
Tokens Studios spent on the team’s key in the past 24 hours. Claude took the most, then OpenAI, then Gemini. The client never calls a model.
FAQ
Frequently asked questions
A release gate is the check on a commit before that change ships. releasegate runs the required suites, test cases, and localization through KaDeep Studios, and returns GO or NO-GO with a report of why. The runs happen on web, iOS, Android, and desktop. The CLI starts each job and polls. It does not call a model.
Yes. kadeep and releasegate are open source under Apache-2.0. They connect to KaDeep Studios, where the tests run. You can get started free.
Any pipeline that can run Node.js 20. GitHub Actions, GitLab CI, CircleCI, Bitbucket Pipelines, Buildkite, Azure Pipelines, and Jenkins supply the commit, the branch, the pull request, and the run link. On a GitHub pull request the gate uses the head commit. Everywhere else it reads git.
Yes. kadeep mcp is a Model Context Protocol server over stdio. Cursor, Claude Code, Codex, and any MCP client can list tests, run them, wait for the verdict, and read a failure step by step. Fourteen tools cover projects, suites, test cases, runs, jobs, defects, and the localization gate. The pipeline evaluates the same project.
Only HTTPS, to the KaDeep API you set. The default is https://api.kadeep.ai. The CLI collects no telemetry. A personal session is stored in ~/.config/kadeep/config.json, readable only by that user. In CI, the project token KADEEP_CI_TOKEN stands in for a personal login.
A required check failed, or errored. A check is a suite, a list of test cases, or localization. An advisory check is printed and does not change the verdict. An empty suite counts as a failure. GO means every required check passed. Shadow writes that verdict and exits 0. Enforce fails the build.
The verdict, the check that failed, and the reason. The job writes .releasegate/report.md, report.json, and junit.xml. On GitHub the job summary carries the same verdict, and a failing check is annotated on the change. The gate holds that check. A person still merges.
Yes, when that check is required. You name the locales, such as hi-IN and ar-AE. A locale blocks the release when coverage is below the bar you set, a delivery is still unapproved, or a critical flag is open. An MQM floor blocks a score below it. kadeep loc validate is the same check from the terminal.
Localization