Polygent
Polygent is a self-hosted control plane for running and supervising AI-assisted development across shared Git repositories.
A deployment consists of the web application, a database, and session execution capacity. Optional deployment workers host long-lived preview environments. Each development session uses an isolated Git worktree so concurrent tasks do not share a working directory.
Core capabilities
Polygent groups day-to-day development and operations into these areas.
| Area | Capability |
|---|---|
| Sessions | Run Chat, Develop, and Bot sessions against selected models in isolated worktrees. |
| Tickets | Track implementation, developer review, QA, pull requests, failures, and completion. |
| Automation | Reuse workflows, bots, scheduled automations, planning, and round-table reviews. |
| Git | Review changes, commit and push branches, create pull requests, and resolve merge conflicts. |
| Operations | Manage workers, preview deployment slots, logs, budgets, notifications, licenses, and branding. |
| Governance | Restrict actions with roles, permissions, workspace membership, and authenticated worker credentials. |
| Reporting | Review session, ticket, cost, automation, and user-activity statistics. |
Deployment and data boundaries
Polygent runs on infrastructure you control and supports SQLite, PostgreSQL, and SQL Server. Repository data, session records, credentials, logs, and uploaded files remain within the systems you configure, except where an enabled integration sends data to an external service. Model providers, Git hosts, and ticket systems receive the data required for their configured operations, under credentials you supply; route model traffic through an approved internal gateway when it must stay on your networks.
Secure production deployments with HTTPS, an OAuth or OpenID Connect identity provider, least-privilege roles, restricted worker credentials, protected storage, and tested database and storage backups.
Recommended reading
Use this order for a new production deployment.
- Installation — install the application and optional workers.
- System Requirements — size hosts and verify dependencies.
- Architecture & Security — review trust boundaries and hardening controls.
- Quick Start — configure a workspace and run a session.
- Permissions — define roles and workspace access before onboarding users.