Skip to main content
Preview. This part of the console is still being built. What you see here describes the intended behavior and can change before general availability.

Installation hub

Some of Dwaar has to run where your systems are: on a developer's laptop, next to a gateway, or inside your network. The Installation hub puts every one of those components on a single page, with copy and paste steps.

Use the commands the hub shows you rather than ones copied from elsewhere. They are specific to your tenant, and the install token is filled into them.

The components​

ComponentWhat it is for
CLIWorks with the console from your terminal.
GuardsOne enforcement point per resource type, such as an SCM app, a Kubernetes admission controller or an AI gateway adapter.
MCP serverLets your coding agent read your products, resources and findings, and start scans. It signs in with OAuth, not the install token. See MCP server.
SkillsAgent skills for running assessments and fixing findings.
OutpostA runner in your own network for the discovery and scans of what Dwaar cannot reach from outside. See Outpost.

The install token​

Guards authenticate with a tenant install token. Generate one on the page and it fills into each snippet.

An outpost uses its own token instead: a one-time enrollment token that enrolls exactly one outpost. Deploy outpost creates it. See Deploy an outpost.

Important

The token is shown once, so copy it straight away. It is saved as a guard token, and you can revoke it at any time under Settings, then API. Viewers cannot create tokens, so ask an administrator.

Try this next​

Install one guard, then check Guard Center, then Live guards. A guard reports healthy within a minute, so you find out quickly whether it worked. Read Guard Center first.