Registry¶

The registry is a package manager for CloudSlash plugins and policy packs. Install community plugins with one command. Publish your own the same way.

Browsing the Marketplace¶

# Browse everything available
cs plugin search

# Search by name or keyword
cs plugin search cost
cs plugin search digitalocean

# Filter by type
cs plugin search: type=plugin    # Provider plugins only
cs plugin search: type=policy    # Policy packs only

Review Process¶

The registry index is fetched live from registry.cloudslash.dev. Results show the plugin name, author, description, category, version, and pricing tier.

Installing Packages¶

Provider Plugins¶

# Install by registry name (resolves to latest stable version)
cs plugin install aws
cs plugin install gcp
cs plugin install azure
cs plugin install k8s
cs plugin install linode

# Install a specific version
cs plugin install linode@v1.3.0

# Install directly from a GitHub Release (for private or beta plugins)
cs plugin install drskyle/gcp-scanner@v1.2.0

Plugins download to ~/.cloudslash/plugins/ as pre-built binaries: no build tools required. The daemon auto-discovers them on next restart.

Only install what you need

Each plugin is a separate gRPC process. Installing unused providers adds startup overhead. Install only the providers you actively use: you can always add more later.

Policy Packs¶

Policy packs are collections of curated CEL governance rules. Install them from the marketplace:

cs plugin install soc2-compliance
cs plugin install aws-security-baseline
cs plugin install cis-kubernetes-benchmark

Policy packs download to ~/.cloudslash/policies/ and automatically evaluate on the next scan.

Managing Installed Packages¶

# List all installed plugins and policies with load status
cs plugin list

Output shows:

Status	Meaning
`loaded`	Plugin is active and connected to the engine
`installed`	Plugin is on disk but not yet loaded (daemon restart needed)
`active`	Policy pack is being evaluated on scans

# Remove a plugin or policy
cs plugin uninstall linode
cs plugin uninstall soc2-compliance

After removing a plugin, restart the daemon to fully unload it from the active scanner pool.

Web Dashboard Marketplace¶

The full marketplace is available in the Web Dashboard at http://localhost:8080 → Marketplace tab. From there you can:

Browse the full registry with descriptions, author profiles, and version history
Install with one click: no terminal required
Rate and review plugins you've used
See pricing for paid plugins and subscribe directly

The daemon exposes these API endpoints:

Endpoint	Method	Description
`GET /api/v1/registry/search?q=aws`	GET	Search registry
`POST /api/v1/registry/install`	POST	Install a package `{"name": "linode"}`
`GET /api/v1/registry/installed`	GET	List installed packages

Custom Plugin Publishing¶

Anyone can publish plugins and policy packs. Paid plugins earn revenue on every install. CloudSlash handles licensing, distribution, and billing.

Scaffold your plugin¶

cs plugin create mycloud

Generates a complete gRPC plugin project:

cloudslash-plugin-mycloud/
├── main.go          # Provider stub with Handshake + Scan + Remediate
├── go.mod           # Dependencies pre-configured
├── Makefile         # build, test, install targets
└── README.md        # Getting started + registry manifest template

Build and test locally¶

make install         # Installs to ~/.cloudslash/plugins/
cs daemon --mock     # Test your plugin against the simulated graph

Create your manifest¶

Create a manifest.yaml describing your plugin for the registry:

name: cloudslash-plugin-mycloud
type: plugin
version: v1.0.0
description: "CloudSlash provider plugin for MyCloud infrastructure"
author: your-github-username
category: cloud
pricing:
  model: free          # or: paid, freemium
  price_usd: 0         # Monthly price for paid plugins
binaries:
  - os: linux
    arch: amd64
    url: https://github.com/yourname/cloudslash-plugin-mycloud/releases/download/v1.0.0/plugin-linux-amd64
    sha256: abc123...
  - os: darwin
    arch: arm64
    url: https://github.com/yourname/cloudslash-plugin-mycloud/releases/download/v1.0.0/plugin-darwin-arm64
    sha256: def456...

Submit to the registry¶

Open a Pull Request to the cloudslash-registry repository adding your manifest.yaml. The registry team reviews for security, functionality, and documentation quality before approving.

See Building Plugins from Scratch for the complete plugin development guide.

Plugin Verification¶

All registry plugins verify before install:

SHA-256 checksum: binary hash checked against the manifest
Handshake protocol: plugin must implement the CloudSlash gRPC contract
Category assignment: assigned by the registry team (not the author) to prevent miscategorization

If a checksum mismatch is detected:

# Force reinstall from registry
cs plugin install aws: force