Plans: Enterprise (dedicated or self-managed). Self-hosted: Enterprise license.
nasiko-ee registry init. The nasiko CLI can connect to, search, and list a registry at a URL you give it. It doesn’t include or default to one.
The artifact registry is an OCI-compliant store for everything you build — agents, skills, tools, MCP servers, standalone binaries. It speaks the same protocol as docker, podman, and oras, with a metadata and search layer on top.
Reach it three ways: its own web UI, the nasiko and nasiko-ee CLIs, or the /v1 (metadata) and /v2 (OCI) HTTP APIs.
Artifact types
Packaging is separate from type. An artifact can ship as plain source, a Dockerfile or Compose recipe, a multi-layer OCI image, or an external reference card with no blob at all.
Publishing
The registry publish command auto-detects agents (AgentCard.json at the root) and skills (skill.json). For anything else, pass --type with an artifact.json manifest:
--force, which replaces what anyone who already pulled that version received. Other publish flags: --framework and --language override what the manifest says, --format sets the packaging (source, open_standard, dockerfile, compose, or external_card; default source), and --card <path> embeds an AgentCard.json when you publish an image. All flags: Admin CLI.
A standard OCI push — docker push, podman push, or oras push — works against /v2 with any compliant client. The registry still classifies the artifact for its catalog, best-effort and never rejecting the push:
- An explicit
org.nasiko.typeannotation: - Otherwise, inference from OCI media types — an OCI 1.1
artifactType, a Helm chart’s config media type. - Otherwise
unknown, grouped under “Miscellaneous.”
Pulling
-
Image-packaged —
docker pull/podman pull/oras pullagainstregistry.example.com/{owner}/{repo}:{tag} -
Single-blob (source, open-standard bundles) —
/v1/artifacts/{owner}/{name}/{version}/download -
From the CLI:
nasiko registryalso supportsdisconnect,status, and--json.search(aliasdiscover) takes--framework,--top, and--min-score.
Browsing and searching
The web UI shows a card grid with type tabs — All, Agents, Skills, MCP, and Miscellaneous (which appears only when there’s an uncategorized artifact). Framework and format facet filters hide themselves when they wouldn’t narrow anything. Search takes a natural-language query and ranks semantically when an embeddings provider is configured. Without one, it falls back to keyword search transparently — same API, same UI, no error.Lifecycle and admin edits
Each version carries a status:preview, stable, or verified. An admin sets these in the UI’s edit-details view or via the metadata API:
yanked isn’t settable this way — removing a version is a deliberate separate action: nasiko-ee registry yank <name> <version> [--owner <org>].
The metadata API accepts these fields on PATCH /v1/artifacts/{owner}/{name}/{version}, all optional: status (preview, stable, or verified), artifact_type, description, tags (string array), license, framework, and metadata (JSON object). Send admin credentials as HTTP Basic auth.
Browsing, searching, and downloading stay open to anyone who can reach the registry. Publish, yank, and edit require admin credentials.
Connecting an MCP client
The registry exposes an MCP server over Streamable HTTP, so MCP-capable clients can browse and act on it directly.Deploying a registry
registry init connects over SSH (--ssh-user, default ubuntu; --ssh-key-path, default ~/.ssh/id_ed25519) and serves the registry on --domain with automatic TLS. Without --database-url and --s3-bucket it runs an embedded Postgres and object store on the host. Leave out --admin-password to be prompted, or set NASIKO_REGISTRY_ADMIN_PASSWORD; a password on the command line is visible to other users of the machine. registry use <name> switches between registries you manage, and registry ssh opens a shell on the registry host.
Pull and push access is governed by the credentials you configure for that deployment. nasiko-ee activate <token> saves pull credentials for a cluster consuming images from a gated registry.
Agent Development Lifecycle
Where publishing fits into shipping an agent.
A2A agents and frameworks
What makes an agent a valid, discoverable artifact.
Sample agents
Ready-to-deploy agents you can pull.
Registry in the dashboard
Browse and publish from the registry’s web app.