Make your AI agents pay off. Your people. Your knowledge. Your rules. All in Kindgi, the full-stack agent framework.
And Kindgi runs all of it on your own infrastructure, with:
- the dev ergonomics of custom code
- the flexibility of a plugin architecture
- the guardrails of a framework
- the audit trail of a compliance system
- the durability of a workflow engine
- On your machine in about ten minutes
- In your test environments the same day
- In production when your review signs off
Let us ask you a question.And if we're right, we have an answer.
Is this why you're here?
Kindgi was built for this.
- Demo to production turned into a platform project. That platform is ready today and always current. How it fits
- Every prompt change waits for engineering. The people who know the work improve the agent directly. How it gets better
- You can't move fast and stay confident at the same time. Risky actions wait for a person, and any release rolls back in one step. How it stays safe
- Your data can't leave your environment. Kindgi runs on your infrastructure, with your own models. Where it runs
- You can't prove the next version is better. Your experts' judgments become the test. How it's proven
- You can't bring the cost down without hurting quality. Plain code wherever it works, and the cheapest model that passes everywhere else. Cost per run
- Something else. Tell us what you're solving. Talk to us
Beside your app. Inside your environment. Across your teams.Kindgi's anatomy at a glance.
Kindgi runtime a service you deploy
Your experts decide what good looks like.How your agents get better.
- 1 Your agent does real work.
It answers requests, drafts replies and updates records in your own systems.
- 2 Anything risky waits for a person.
You choose which actions need someone's approval before they happen.
- 3 Your experts mark answers right or wrong.
A yes or a no, with a reason if they like. Nobody has to write prompts.
- 4 Their judgments become the test.
Before release, a new version is tested on your real cases, and you can make that a rule.
- 5 You decide what goes live.
Instructions change without waiting for engineering. Release when it's better, and roll back in one step.
Your business team owns what good looks like; engineering owns the code. Both work on the same agent, and nothing goes live without your say.
Built by your coding agent. Supervised by your people.How your agents get built.
Paste one prompt into Claude Code, Cursor, Codex or any coding agent. It sets up Kindgi, builds a first agent with you, and stops whenever it needs you.
Set up Kindgi for me: read https://docs.kindgi.com/start/agent/ and follow it step by step. Tell me whenever you need me to do something, and wait for me.
$ npx @kindgi/cli init my-pack --template=sample $ cd my-pack && pnpm install $ pnpm exec kindgi dev
$ uvx --from "kindgi-cli>=0.1,<0.2" kindgi init my-pack --template=python $ cd my-pack && uv sync $ uv run kindgi dev
$ npx @kindgi/cli init my-pack --template=java $ cd my-pack $ ./kindgiw dev
$ npx @kindgi/cli init my-pack --template=scala $ cd my-pack $ ./kindgiw dev
$ curl -X POST "$KINDGI_API_URL/v1/runs" \
-H "Authorization: Bearer $KINDGI_API_TOKEN" \
-H "Content-Type: application/json" \
-d '{"agent":"my-pack.support","input":{"userMessage":"Where is order 1042?"}}' No SDK for your language yet? Use the HTTP API. Every route is in the OpenAPI spec with an example, so any language can start runs, follow them, send judgments and decide approvals. Your own services, in any language, can be an agent's tools as HTTP endpoints or MCP servers.
Kindgi gives coding agents everything they need to keep you in charge without keeping you busy.
- Skills in your repo
Step-by-step instructions for tools, agents, flows and guardrails, in your language and matched to your Kindgi version.
- Four ways in
The CLI, the SDKs and the HTTP API for your coding agent and your developers; the console for your business people.
- Docs written for agents
Every detail documented in sync with Kindgi's interface, and all of docs.kindgi.com optimized for agent-to-agent communication.
- Errors that name the fix
kindgi doctorchecks the machine, and every error says what's wrong, so the agent fixes it and runs again. - You stay in charge
It builds and tests; your people decide what goes live. A release can require your experts' tests and a reviewer's sign-off, and each one is kept with who asked for it and why.
- When Kindgi is the problem
Your agent tells a bug in Kindgi from a bug in your code, and writes it up, ready to send to us.
Running on your terms.Your knowledge, your decisions, your infrastructure, your models, a plain licence.
Where it runs
In your environment, as one more of your services: a container image and a database, inside your network, next to the services it works with.
Which models
Your agents don't name a model. They say what they need, and Kindgi picks from the models you connect: the leading model providers, open models you serve yourself, or your company's AI gateway.
Model calls use your own accounts.
Licence
The SDKs and CLI are open source (Apache-2.0). The runtime is free for development, testing and staging; production use needs a licence.
Give Kindgi a try.On your own, or with us.
Request access
Kindgi is in private preview. Write to contact@kindgi.com for access; then it's one prompt and about ten minutes to a first agent on your machine.
A 4-week pilot
Kindgi in your environment, on one of your workflows, with weekly sessions with the founding team.
We can't wait to see what you do with it.