npm packages and marketplace listings — every surface where you can install Frontguard.

Where to find Frontguard

Frontguard ships across four developer marketplaces and the public npm registry. Pick the surface that matches how your team already deploys.

Frontguard 0.2.0 is the first release on every marketplace. If a listing is marked Coming soon, the integration is built and tested — we are waiting for the marketplace's review queue. The corresponding npm package is published and usable today.

npm registry

All Node-installable surfaces live on the public npm registry under the @frontguard/* scope. Every release ships with npm provenance so you can verify it was built from main in CI.

Package	What it is	Install
`@frontguard/cli`	Standalone CLI + GitHub Action entrypoint	`npm i -D @frontguard/cli`
`@frontguard/playwright`	3-line visual assertion plugin for Playwright	`npm i -D @frontguard/playwright`
`@frontguard/netlify-plugin`	Build plugin that runs on every Netlify deploy	`npm i -D @frontguard/netlify-plugin`
`create-frontguard-plugin`	Scaffold a custom Frontguard plugin	`npm create frontguard-plugin`

Once installed, the CLI's installation guide and quick-start cover the rest.

GitHub Marketplace

Frontguard ships as both a GitHub App (deeper Check Runs + PR signal) and a composite Action (no install required, drop into any workflow).

Surface	Status	Install
Frontguard GitHub App	Coming soon	One-click app install
Frontguard composite Action	Available via `@frontguard/cli`	`uses: ravidsrk/frontguard@v0`

Action manifest: packages/cli/action.yml. App manifest: integrations/github-app/manifest.yml.

Composite Action usage

- uses: ravidsrk/frontguard@v0
  with:
    routes: '/,/pricing,/docs'

Vercel Marketplace

The Frontguard Vercel integration listens for Deployment Ready webhooks and runs a Frontguard run against the preview URL, posting results back to the originating PR.

Status
Marketplace listing	Coming soon
Manual install	Available now via integration manifest

Install via Vercel CLI

vercel integrations install frontguard
# or, while it's in review, point at our manifest:
vercel integrations install --manifest=integrations/vercel/frontguard.config.ts

Netlify Build Plugins

The official Netlify Build Plugin runs Frontguard in onSuccess against the live deploy URL — the most reliable place to catch preview regressions.

Status
npm package	`@frontguard/netlify-plugin` — available
Build Plugins directory	Coming soon — Netlify Build Plugin partner program

Install in `netlify.toml`

[[plugins]]
  package = "@frontguard/netlify-plugin"

  [plugins.inputs]
    apiUrl   = "https://api.frontguard.dev"
    routes   = ["/", "/pricing"]
    failBuild = false

Set FRONTGUARD_API_KEY (and optionally GITHUB_TOKEN) in the site environment — never in netlify.toml.

Slack App Directory

The native Slack app posts run results into Slack and gives every developer a /frontguard slash command for ad-hoc runs.

Status
Slack manifest	`integrations/slack-app/manifest.yml`
Directory listing	Coming soon — Slack App Directory
Manual install	Available today via the Add to Slack button on the docs site

Quick install

Click Add to Slack on frontguard.dev.
Approve the requested scopes (chat:write, commands).
Run /frontguard help in any channel.

Self-hosting

Every surface above hits the public Frontguard Cloud API by default. To point at a self-hosted instance, set apiUrl (Netlify, GitHub Action, Playwright) or FRONTGUARD_API_URL (CLI) to your endpoint. The cloud-api package is in the same monorepo — see packages/cloud-api.

Release cadence

Releases land on the same day across every surface: tag a v* on main, the Release workflow publishes the npm packages, and a release captain submits the marketplace listings using scripts/release.sh. The npm tarballs are reproducible — npm pack --dry-run will print the exact contents of the next release before publish.

Found a marketplace surface we're missing? Open an issue and we'll add it.

Where to find Frontguard

On this page