Download
Install the Windows desktop app when a verified release is published.
AI workspace for Windows
Use one account to run AI-assisted coding work across your local projects: inspect files, explain code, prepare edits, run terminal checks, review changes, manage API keys, and keep billing, teams, devices, and history visible from the web portal.
Use AI agents to work on your local codebase.
Ask an agent to help with your project...
I will take a look at your project and suggest next steps.
Scanning project files...Analyzing code structure...Identifying improvements...Ready with suggestions.Install the Windows desktop app when a verified release is published.
Use email/password or configured Google sign-in for the same account on the site and app.
Open a local repository, keep the file tree visible, and choose what the agent may access.
Ask for explanations, edits, tests, terminal checks, review notes, or project cleanups.
Built for local coding
UGP combines a Windows coding application with a web account portal. The desktop app is where code work happens; the website keeps account access, pricing, plan limits, usage, billing, devices, teams, API keys, project records, and security settings in one place.
Ask an agent to inspect a repository, explain unfamiliar code, plan a change, prepare edits, or summarize what needs verification before you merge.
Keep project files, terminal output, and agent context near each other so code changes can be checked without jumping between unrelated tools.
The web portal stays focused on account and product operations. Local code work belongs in the Windows application, where file access and terminal actions are explicit.
Manage profile, plan, usage, invoices, API keys, linked devices, teams, project records, and security settings from the website.
Agent records, statuses, provider and model metadata, timestamps, project links, and history actions are shown when returned by the account API.
Invite members, manage roles, issue scoped API keys, rotate or revoke access, and review which devices are connected to the account.
The billing area is designed to show plan, spend, remaining credits, forecasts, invoices, and exportable usage once the server supplies those records.
Download pages show a direct installer only after a real release URL and version are configured; otherwise the site explains what is missing.
Protected account routes require a session, private pages are excluded from robots, and destructive account actions are represented as explicit routes.
Public pages describe only product surfaces that are wired in the current site and server. When a release, payment route, provider, or sign-in method is not configured, the page says so plainly.
Download, sign-in, billing, and account routes lead to working product states backed by current configuration.
The same account links the website, Windows app, devices, usage records, teams, API keys, and billing state.
Public pages, cards, navigation, footer, and forms stay readable on mobile, tablet, laptop, and desktop widths.
Google sign-in, Stripe, email flows, and release metadata either use real configuration or show a clear unavailable state.
Start free, upgrade to Pro for individual work, choose Team for shared accounts, and use Enterprise when procurement, deployment, or policy needs are larger.
$0
no hard limit
For trying UGP, opening the account portal, and validating the desktop workflow.
$20/month
no hard limit
For one developer working daily with agents, terminal checks, history, and usage.
$40/user/month
team collaboration
For multiple members, shared billing, roles, projects, devices, and API keys.
Custom
no hard limit
For procurement, security review, access policy, self-host discussion, and rollout.