Frequently asked questions
Answers for buyers and technical evaluators. Seat mechanics, checkout, and the license calculator are on Purchase.
Product
Is PrideForge actual software or training?
Both, by design. Core is working automation framework software delivered through PrideForge Manager. Academy is hands-on onboarding mapped to the installed framework — not a standalone video course.
Does PrideForge automate our application out of the box?
No. PrideForge provides authentication, reporting, locators, handlers, data utilities, CI patterns, and other reusable infrastructure. Your team adds application pages, scenarios, configuration, and test data.
What must our team customize?
At minimum: application/environment configuration, login behavior for your products, page objects, business scenarios, and test data. Samples show every major capability; your production coverage lives in the customization layer.
Do we have to adopt every part of PrideForge?
No. PrideForge is an extensible working framework. Teams customize or replace individual pieces as their application requires. Teams with mature frameworks may adopt selected patterns where they fit.
Do we have to use BDD?
PrideForge is built around readable Gherkin scenarios and shared steps — that is the primary authoring model. The underlying stack is Playwright and .NET; engineers maintain step definitions and page objects underneath.
Can we extend the framework?
Yes. Add application-specific page objects, login handlers, field handlers, configuration, and custom widgets in the customization layer without rebuilding Core.
Can PrideForge support multiple applications?
Yes. One framework can target multiple products, servers, and URLs. Configuration drives authentication, navigation, and environment behavior per target.
How do Core updates interact with our customizations?
Core is maintained by PrideForge; your customizations live in a separate layer. The separation is designed to minimize conflicts when Core is updated. See How it works on the Product page.
Execution & delivery
Where does automation execute?
On infrastructure you control — developer machines and your CI agents. PrideForge is not a hosted test execution service.
Is CI metered?
No. Named users are licensed. Test volume, runners, agents, pipelines, and internal executions are not metered remotely.
How is software delivered?
Through PrideForge Manager. Licensed users authenticate, download Core and licensed modules, and install updates — not via a public repository clone.
What happens if we do not renew?
You may continue using the version and customizations created during your active subscription for internal automation. You lose Manager package delivery, Academy, and future updates until you renew. See the EULA and Commercial Terms.
Licensing
Who needs a user seat?
Anyone who installs PrideForge with Manager or takes PrideForge Academy. License managers can assign seats without holding one, but cannot install or take Academy until seated.
What is included with Core?
Company Core at $5,000/year includes Manager delivery, Academy access, updates, and 1 user. Additional users use volume bands ($750 / $600 / $525). API and Database modules are $1,000/year each.
Can we add users later?
Yes. Additional users use the pricing tier in effect when purchased and are prorated for the remainder of your term. Existing seats keep their original pricing.
Need 20+ users?
Contact sales for a custom quote.
What support is included?
Technical support during an active Core subscription. Contact support@prideforge.com for licensing, billing, and product questions.