Connect your codebase to Poliogo
Every way to connect a project. Whatever the path, Poliogo reads only what it needs — service names, project addresses, env var names — and the files a scan reads are processed in memory and dropped.
16 connectors · 4 categories · the grant stated per provider
No connector for your setup? Connect the Git repository or hosting account your project already lives in.
Git Providers
Connect a repository and get documents, installs and drift updates as pull requests.
Hosting
Connect a deployment to confirm your production URL and detect services from environment variable names — values are never read.
Project list, production URL and env var names via a read-only integration.
Site list and live address; env names read, values discarded by design.
Projects, service domains and variable names over read-only queries.
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.
No-Code / AI Builders
Connect the repository your builder syncs to — the scanner reads what the generated code actually calls, not what a page renders.
Turn on GitHub sync in Lovable, then connect that repository.
Push your project to GitHub from Bolt, then connect that repository.
Deploys through Vercel — connect your Vercel account for the most accurate scan.
Export to GitHub where your tier allows it, then connect that repository.
Connect the repl to GitHub, then connect that repository.
Turn on GitHub Integration in FlutterFlow, then connect that repository.