Connectors

Every way to connect a project. Whatever the path, Poliogo reads only what it needs — service names, project addresses, env var names — and never stores your source code.

No connector for your setup? Every project can start from a ZIP upload.

Git Providers

Connect a repository and get documents, installs and drift updates as pull requests.

GitHub

Read-scoped App installation — you pick the repositories. Compliance updates arrive as PRs.

GitLab

Connect gitlab.com projects; installs arrive as merge requests from Poliogo's own branch.

Bitbucket

Connect workspaces; installs arrive as pull requests from Poliogo's own branch.

Hosting

Connect a deployment to confirm your production URL and detect services from environment variable names — values are never read.

Vercel

Project list, production URL and env var names via a read-only integration.

Netlify

Site list and live address; env names read, values discarded by design.

Railway

Projects, service domains and variable names over read-only queries.

Cloudflare Pages

A scoped read-only API token you mint yourself — two Read permissions, nothing else.

AI Editors

Via MCP — npx poliogo-mcp init. Scans locally; only the detected-service fingerprint leaves your machine.

Cursor

Your agent runs scan_stack, generate_docs, install_pages and check_compliance in the editor.

Claude Code

The same six MCP tools, plus CLI subcommands so CI reaches the same code path.

Windsurf

No-Code / AI Builders

Connect the synced repo where one exists, or export a ZIP — the scanner reads what the generated code actually calls.

Lovable

Best path: GitHub sync. Otherwise export a ZIP from your builder.

Bolt.new

Best path: GitHub sync. Otherwise export a ZIP from your builder.

Deploys through Vercel — connect your Vercel account for the most accurate scan.