Skip to main content
Use any harness. Reach any model. Measure every token. Change nothing. Find the coding agents already running. See what each one costs, by harness, model and team. Reach any model from any harness. One command on a laptop, the same command across an estate — and nothing changes about how anyone works. An OpenRuntime belongs to no vendor in it. Use any harness, any model, any framework, and change your mind about all three. Your cost history, policy and memory stay with you rather than with whichever tool you happened to pick.

​
Two properties

Non-invasive

Your architecture. Nasiko discovers the harness you already run, and it keeps running unchanged. No wrapper. No SDK in your code path.

Non-intrusive

Your day. One command to find your agents, one more to register each, and your workflow stays the same. Developers keep using the same harness commands and interfaces.

​
Choose your path

Find and measure your coding agents

Discover Claude Code, Codex, OpenCode and the Cursor CLI on your machine, report their sessions, and see what each one costs. About ten minutes.

Deploy an agent

Scaffold an agent in any framework, run it locally, deploy it to your Nasiko cluster, and chat with it.

​
What Nasiko does

TokenOps

Spend across every harness and framework in one schema — by model, agent, session, developer and team.

Policy, security and governance

Control what each agent can reach, enforced where the call happens: access grants, tool permissions, approvals, flow limits and secrets.

Orchestration

Build, deploy and compose agents from any framework, and route each model call to the provider you choose.

​
How a call flows

Nasiko sits in the call path. That’s what lets it attribute cost across vendors and enforce policy without owning the machine. A few terms you’ll see throughout the docs:
  • Coding agent or harness: a developer tool such as Claude Code, Codex, OpenCode or the Cursor CLI. Nasiko discovers it and can report its sessions and route its model calls. The harness itself is unchanged.
  • Deployed agent: an agent you build in any framework and run on your Nasiko cluster. It speaks the A2A protocol.
  • Cluster: a Nasiko server the CLI is connected to — local on your laptop, or shared across your organization.
  • Session: one conversation, whether it came from a harness, the dashboard, or the CLI.
  • Flow: everything one request caused — every agent hop, model call and tool call — traced and attributed together.

​
Explore

Coding agents

Discovery, session reporting and model routing.

Model routing

Route any harness or agent to any provider.

MCP gateway

One permission-filtered tool surface for every agent.

Dashboard

Every screen, explained.

Self-hosting

Run the full stack with Docker Compose.

CLI reference

Every command and flag.