Community catalog
Plugins are published by independent authors, agencies, and partners as well as Beach. Your team browses and installs from the in-product marketplace; we curate policy and safety, not a single-vendor shelf.
Platform · Plugins
BetaThe plugin platform is in beta: installable panels and tools inside Gleo.dev, contributed by the community — including Beach and partners, but not limited to us. Plugins add specialist workflows while you manage sites; they are separate from workspace-wide Integrations and per-site Forge Apps.
Plugins are published by independent authors, agencies, and partners as well as Beach. Your team browses and installs from the in-product marketplace; we curate policy and safety, not a single-vendor shelf.
Each install adds tabs or tools next to deploys, forms, and settings. Plugins use the client plugin SDK and scoped site data — ideal for SEO reviews, QA snapshots, accessibility checks, and custom ops dashboards.
Build iframe panels with @forge/client-plugin-sdk. Writes and heavy logic usually run on the plugin backend; Gleo hosts the shell, install flow, and protocol between panel and workspace.
Illustrative cards below show the kinds of tools teams install during beta — not a live public directory on gleo.dev.
Review titles, meta descriptions, Open Graph tags, and heading structure for the current site. Surface quick fixes before you ship a deploy.
Capture visual snapshots of key pages when you deploy — compare staging to production and spot layout regressions without leaving Gleo.
Run automated WCAG checks against your live preview URL and summarise issues by severity with links to the affected routes.
Aggregate Gleo form submissions in a panel: volume trends, top referrers, and spam flags for the site you are editing.
Inspect redirect rules and 404 patterns for a site, suggest bulk updates, and validate chains before they hit production traffic.
Lightweight Lighthouse-style signals on staging: LCP, CLS, and asset weight — tuned for marketing sites rather than full CI reports.
Integrations are not plugins. They connect once at the workspace level and can span every site your team manages — shared credentials, shared mapping, one place to audit access.
Link a GA4 account to the workspace, map properties to production sites, and open analytics from Gleo without pasting tracking IDs into every project by hand.
Configure under Workspace → Integrations after sign-in. Account-level deploy sources (such as GitHub) stay separate from these team-wide connections.
Sign in to Gleo.dev to install beta plugins from the marketplace and configure workspace integrations. Authors can ship panels with the client plugin SDK — community contributions welcome.