A control plane that runs on your own machines
Your AI workforce.One route, one decision, one record.
You hold the pools: accounts, models, hosts, projects, roles. Kimene decides which of them runs the work, writes down why, and executes it on real machines through the real CLIs.
What it does
Four things, one plane.
Kimene holds the pools, decides which of them runs a piece of work, executes it on real machines, and writes down what happened with the evidence attached. Each has a section of its own, one level deeper, with the command that proves it.
The pools stay yours
Accounts, models, hosts, projects, roles and tools are separate pools. None of them owns another; the association is made only while work runs, and it is recorded.
The decision is written down
Which account, which model and which host were chosen — and which were rejected, and why. The components of the score stand as an immutable record.
Completion requires evidence
A task reaches completion only through review or approval. The evidence contract comes from the kind of task it is; the API has no path to write the state directly.
Credentials stay at the boundary
The control plane stores no credential body and carries none between machines. It knows paths and references; provider isolation is established through the process environment.
The part that is real
Not an abstraction: live sessions on real machines.
Every session runs on a host, through the provider’s own command-line tool. The wall shows them side by side, and an operator can take the keyboard at any moment.
Built by
Arpanet Bilişim Teknolojileri A.Ş.
Kimene is built and supported by an engineering team at the METU Technopark in Ankara.
ODTÜ Bilişim İnovasyon Merkezi — D Blok: 115/116/117Çankaya, Ankara · TürkiyeOn your own machines, with your own accounts.
Kimene runs on your infrastructure and manages your own provider accounts. It is not a credential-sharing service, not a multi-tenant proxy, and not a way around provider limits.