Hosted Solo
€59/ month
- Developer seats
- 1
- Concurrent agent runs
- 2
- Data storage
- 20 GB
- Backup retention
- 60 days
Your own ProPR instance, operated by us.
ProPR Hosted runs the full ProPR backend in a dedicated VM that the ProPR team operates. Connect handles GitHub routing, billing, and lifecycle status. The fleet service provisions, checks, suspends, backs up, and retires the VM through operator-approved plans.
Limited capacity. Hosted is open for paid signups. Capacity is limited, and Connect checkout shows whether a new instance is available or sold out.
Authority
- Polar checkoutSigned billing webhook sets the plan entitlement
- Connect control planeCloudflare Workers, D1, and R2 hold desired state, plans, approvals, and audit history
- Operator approvalEach infrastructure plan is approved by hash; destroy needs two operators
- Fleet executorOne executor host pulls approved work over HTTPS and applies it
- Proxmox hostsFleet nodes and sites; the pool grows as hosts are added
Traffic
Your dedicated ProPR VMRepositories, tasks, agents, credentials, logs
- outboundConnectGitHub events over a WebSocket the VM opens
- outboundManaged tunnelUI access through
t-<instance>.propr.dev - outboundGitHubClones, branches, and pull requests with tokens issued through Connect
- outboundYour AI providersPrompts and code context for the agents you configure
No public inbound ports. Management access accepts only the operator network.
Operational overview
Three monthly plans, sized by capacity.
Each plan includes the managed ProPR backend, Connect routing, a managed UI tunnel, and encrypted application backups. Repositories have no count limit; they share the plan's storage. Prices are monthly, in euros, and exclude VAT where applicable.
Hosted Team
€149/ month
- Developer seats
- 5
- Concurrent agent runs
- 6
- Data storage
- 130 GB
- Backup retention
- 60 days
Hosted Scale
€349/ month
- Developer seats
- 15
- Concurrent agent runs
- 12
- Data storage
- 280 GB
- Backup retention
- 60 days
Additional Hosted seats cost €15 per seat per month and raise the seat count only. Concurrency, storage, and backup retention follow the plan. Connect Plus seats for self-hosted stacks keep their own USD pricing on the pricing page.
What each limit means.
Developer seats
A seat is a distinct GitHub developer who starts ProPR work through Connect in a billing cycle. Bots such as GitHub Actions and the ProPR bot never take a seat. At the limit, Connect replies on the issue or pull request and starts no task for new developers. Connect applies the larger of two allowances: your Connect allowance (3 free users, or your Plus seats) or your Hosted seat total, which is the plan's included seats plus any additional Hosted seats. The allowances never add together, so Hosted Solo keeps the 3 free Connect users.
Concurrent agent runs
The plan sets the ProPR worker concurrency on your VM, and the setting cannot be raised from the ProPR UI. Additional tasks wait in the queue until a run finishes.
Data storage
Data storage holds repository clones, agent workspaces, the database, logs, and settings. Each VM also gets a fixed 20 GB system reserve for the operating system and the ProPR runtime, which does not count against your data storage. Plans never shrink an existing disk.
Backups
Application backups contain the ProPR database, protected configuration and encryption keys, stored agent credentials, ProPR settings, and the queue state. They are compressed and encrypted on the VM before the remote copy. Repository clones, agent workspaces, and logs are excluded; clones come back from GitHub, and unpushed work in a workspace is not recoverable from a backup. The plan's backup retention is a rolling window while the instance runs. Restore is an operator-run procedure with no recovery-time commitment.
Every infrastructure change is approved and recorded.
One VM per subscription
Each Hosted subscription gets its own VM, disk allocation, managed tunnel, and tenant identity. Tenant VMs cannot reach each other.
Operators approve plans
Provisioning, resizing, suspension, and deletion run from saved infrastructure plans. An operator approves each plan by its hash, and the approval expires. Deletion needs two different operators.
Activation verifies the owner
The GitHub account that subscribed becomes the instance administrator. Activation also waits for a health report from the new VM.
The executor holds no authority
One fleet executor host applies approved plans to the Proxmox hosts. It cannot approve plans, verify backups, or request deletion.
Provider access is yours
You supply the AI subscriptions or API keys your agents use. Providers bill that usage directly; ProPR adds no token markup.
Deletion has gates
Offboarding drains running work, takes a final backup, and waits out the retention schedule agreed at activation before the destroy plan runs. The encrypted backups left after destruction are kept for 60 days, a window separate from the plan's rolling retention. Purging them afterwards needs two operator approvals.
Hosted: we operate the VM that holds your data.
Repository clones, prompts, task history, logs, settings, and the AI provider credentials you configure live on the Hosted VM. The ProPR team operates that VM and can access it to run, secure, back up, and restore the service. Review artifacts land in GitHub.
Self-hosted: you hold everything.
With self-hosting, the same data stays on infrastructure you operate, and the ProPR team has no access to it. Connect remains optional for webhook routing and tunnels. Compare both data boundaries.
From plan to running instance.
Choose a plan
Pick Solo, Team, or Scale and the number of developer seats.
Sign in and attach GitHub
Sign in to Connect with GitHub and select the GitHub App installation the instance serves. An organization installation needs an organization admin.
Check out through Polar
Connect reserves an instance slot before it opens checkout. When every slot is taken, Connect shows Hosted as sold out and starts no charge.
Follow provisioning in Connect
Payment sets the plan entitlement. The fleet then provisions your VM through an operator-approved plan, and Connect shows each lifecycle step.
Claim your instance and add providers
Sign in to your ProPR instance with the GitHub account that subscribed and claim administrator access. Then add your AI provider subscriptions or API keys in the instance settings. Those credentials stay on your VM and never reach Connect.
Hosted is open for paid signups.
Each subscription gets its own VM, so Hosted capacity is limited. Connect checkout shows whether a new instance is available right now; when it shows sold out, check again later.