A developer runs many agents, so Pushgate does not charge once per process. Start with one private repository, then cover the people and repositories that use the gate.
The pricing model is live; checkout is not self-service yet. Free starts in the product. Business and Enterprise are provisioned with our team.
Prove the repository boundary end to end before buying.
Start freeFor engineering organizations putting the whole team behind the gate.
Talk to salesFor large or regulated deployments that need controls and terms.
Talk to usNo. Plans cover developers; each covered developer may connect as many supported or custom agents as needed.
The customer declares how many developers to cover. Paid provisioning and billing are handled with our team today; Pushgate does not silently turn a new pusher into an automatic charge.
Free covers one private repository and up to three developers. A second private repository or a fourth developer moves the deployment to Business.
The product should encourage useful automation. Charging for every agent process would punish the behavior Pushgate is designed to make safe.
In a customer-controlled AWS, Google Cloud, or Microsoft Azure account, or fully on-premises on customer-owned infrastructure. It is an appliance deployment, not a dependency on Pushgate's shared SaaS control plane.
Any Git repository provider, including self-hosted providers. We configure the appliance for the repository and identity infrastructure the customer operates; it is not limited to GitHub.
We size compute, storage, availability, and support with the customer. The proposal states cloud consumption or required equipment separately from the Pushgate subscription instead of hiding it inside a seat price.
Yes. Start on Free, use the instrumented delivery path, and compare equivalent Pushgate and hosted-CI workloads before choosing broader deployment.
Tell us how many developers and repositories you want to cover; our team will provision the plan through the sales-assisted buying process.