System Requirements
Use these requirements to size the control plane and every worker host before installation.
Hardware
Hardware needs scale with repository size, active worktrees, local model use, and configured concurrency; the values below are initial planning baselines, not hard limits.
| Component | Minimum | Recommended |
|---|---|---|
| CPU | 2 cores | 4+ cores (more if you run many parallel sessions) |
| RAM | 4 GB | 8+ GB |
| Disk | 10 GB free | 50+ GB free (scales with concurrent sessions and repository size) |
Disk usage scales with the number of concurrent sessions, plans, and round tables — each gets its own Git worktree under StoragePath.
Software
Install these dependencies on the control-plane host and on each worker that executes the related workload.
| Requirement | Version | Notes |
|---|---|---|
| .NET Runtime | 10.0+ | Runs the API, Session Worker, and Deployment Worker |
| Git | 2.20+ | Worktree-based isolation |
| OS | Windows 10/11, Windows Server 2019+, Linux (Docker) | Windows Service deployment is the recommended path on Windows |
Agent and models
Model requirements apply to every host eligible to run sessions with that model.
The built-in Polygent Code agent runs every session — no CLI install is required. You pick a model from a single flat dropdown and supply its credentials. Optional backends need something on the session host:
- Local command-line tools — only for models that authenticate through a local tool. Must be on
PATHand logged in on every eligible Session Worker host. - Ollama — only for local models. Must be installed with the model pulled.
Direct API models need the matching credential. Models authenticated through a local subscription or coding tool also require that tool to be installed and authenticated on every eligible session host.
Database
The database stores platform state; choose one provider before production rollout and back it up independently of file storage.
Polygent supports three database providers, configured via appsettings.json:
| Provider | Use Case |
|---|---|
| SQLite | Default, zero-configuration, suitable for small teams and trials |
| PostgreSQL | Recommended for production with multiple users |
| SQL Server | Enterprise environments with existing SQL Server infrastructure |
See the Database configuration guide.
Network
Allow only the inbound and outbound paths required by your deployment, and terminate TLS before exposing Polygent to users.
- The API listens on a configurable port (default
5000for a bare process / Windows Service;8080inside the container image). Override with the standard ASP.NET CoreUrls/ASPNETCORE_URLSsetting. - Real-time updates require WebSocket support — make sure reverse proxies forward
UpgradeandConnectionheaders - The agent needs outbound access to whichever model backend you use (Anthropic, OpenAI, Google, OpenRouter, etc.) — unless you use local models via Ollama
- The Session Worker and Deployment Worker services connect back to the API over HTTPS using an API key
- Optional: GitHub and/or Azure DevOps connectivity for OAuth login, PR creation, and ticket sync
Authentication
Production deployments require one configured OAuth2 or OpenID Connect identity provider.
Polygent supports the following sign-in methods:
- Google OAuth2
- Microsoft OAuth2 (Microsoft 365 / Entra ID)
- Generic OpenID Connect — any OIDC-compliant IdP (Okta, Auth0, Keycloak, etc.)
Configure OAuth credentials in appsettings.json. JWT keys (RS256) are auto-generated under StoragePath on first run. Tokens use secure, HttpOnly cookies and rotate automatically; sign-in state syncs across browser tabs.
Browser support
Use a current browser with cookies and WebSockets enabled.
The client targets evergreen browsers:
| Browser | Minimum |
|---|---|
| Chrome | 110+ |
| Edge | 110+ |
| Firefox | 115+ |
| Safari | 16+ |
WebSockets must be allowed end-to-end for live updates.
Optional integrations
Install or permit these integrations only when the corresponding feature is enabled.
| Integration | Use Case |
|---|---|
| GitHub PAT / OAuth | OAuth login, issue sync, PR creation, public release pulls |
| Azure DevOps PAT | Work item sync, PR/MR creation and tracking |
| Session Worker host(s) | Spread AI sessions across multiple machines |
| Deployment Worker host(s) | Run slot deployments on dedicated machines |
| MCP-compatible clients | Agent access to approved Polygent context tools |
Security: Access to
/mcprequires a temporary credential issued for an active agent run and scoped to its identity, session, workspace, and allowed tools. Keep the endpoint behind HTTPS and reachable only from trusted worker networks as defense in depth.