Skip to main content
On Nasiko Cloud, the dashboard is at app.nasiko.com. On a self-hosted server, it ships inside the Nasiko server: open your cluster URL — nothing extra to install. It reads the same data the CLI and API do.

Signing in

On Nasiko Cloud, sign in with Google or GitHub. A Pro workspace can also connect its own identity provider. See SSO and SCIM. On a self-hosted server, sign in with a username and password at your cluster URL. GitHub, Google, and Microsoft buttons appear only if your organization has enabled them. GitHub sign-in is included in the open-source server. Sign-in through your own identity provider, such as Microsoft or Google, needs an Enterprise license. Sessions are stored in a secure cookie. When a session expires, the app returns you to the login screen. The rail, left to right: Also in the module trees, not all on the rail: Workflows and Executions (Workflows), Set up CLI, Flows, Resources, Secrets.
Plans: Pro and Enterprise. Self-hosted: Enterprise license.
Access control, with its Org structure and Users tabs, is where admins manage people and org units. A self-hosted open-source server manages user accounts and agent grants through the API, without org units.

Artifact registry

Plans: Enterprise (dedicated or self-managed). Self-hosted: Enterprise license.
The artifact registry is a standalone service you deploy with the admin CLI. Every Nasiko server, including the open-source server, has the embedded image registry at /v2/* and a client (nasiko registry connect/search/list) that can point at an artifact registry if you have one. See Artifact registry.

Screens

Chat

Orchestrator or a named agent.

Agents

Catalog, deploy, manage.

Workflows

MAF pipelines and executions.

MCP gateway

Connectors and per-agent tools.

Sessions and traces

Transcripts and traces.

Settings

Secrets, SSO, flow limits.