Self-hosted AI agents, in production · installs in fifteen minutes
Rikoo

We built the layer we kept rebuilding.

Every team we worked with reached the same wall: the agent worked in a week, and then took months to become something anyone would put in front of a customer. Rikoo is that second part, extracted and made reusable.

What we believe

An agent that acts on your systems is infrastructure, not a feature. It deserves the same things any other production service gets: versions you can point at, permissions that are enforced rather than requested, a record of what happened, and a bill you can explain.

We also believe you should be able to read the code that decides what your agents are allowed to do. That is why the core is open and why the enterprise modules are separable rather than woven through it.

What we will not do

  • We will not train on your data. We never see it.
  • We will not price on your usage. What you spend at a model provider is between you and that provider.
  • We will not lock the core behind a licence key. If you stop paying, the enterprise modules stop loading and everything else keeps running.
  • We will not claim a capability we have not shipped. What is planned is labelled as planned.

Where we are

Rikoo is developed by a small team. If you want to know who, what we are working on next, or whether something on the roadmap will land in time for you, ask. We answer directly.

Tell us what you are building.

We are more useful in a conversation than in a form.