Plans: Enterprise (dedicated or self-managed). Self-hosted: Enterprise license.
nasiko-ee is the admin CLI for Enterprise deployments, dedicated or self-managed. It isn’t for Nasiko Cloud Free, Individual, or Pro workspaces: use the dashboard and the nasiko CLI there. Most organization and access commands fail against a self-hosted open-source server.
Install: Install and connect.
nasiko-ee keeps a list of the deployments it manages in ~/.nasiko/deployments.json. Commands that talk to a deployment use the active one. Set it with nasiko-ee use <name>. users, admin, access, billing, and license also accept --deployment <name> to target another one for a single command.
Provision
nasiko-ee init flags
Provider credentials come from
~/.nasiko/.ee.env or your environment:
nasiko-ee activate <token> takes --username (Docker Hub user, default nasiko) and --registry (default docker.io/nasiko).
Operate a deployment
Agent hosting
Existing Kubernetes clusters
Sign in
SSO sign-in uses a one-time code you approve in the browser. See Sign in from the CLI.
Users
nasiko-ee users manages accounts on the active deployment.
--role takes admin or member. A user becomes a manager when they’re appointed lead of an org unit, not through --role. See User and org management.
No --password flag exists. The server returns a one-time access key and secret, and the secret is the user’s first password:
nasiko-ee admin
Account recovery and search. Each user-* command also exists as admin user <verb> (for example admin user reset-creds), and each search-* command as admin search <kind>.
Access
--user (-u) and --agent (-a) repeat and combine in one call. Grants to org units are made in the dashboard. See User → agent access.
License
billing usage prints the deployment’s agent container count. billing plan prints the deployment’s plan.
Registry
See Artifact registry.
Agents, MCP, and coding agents
nasiko-ee includes the nasiko commands for day-to-day work, so one binary covers both:
See Coding agents CLI and MCP CLI for flags.