What this solves
Platform pricing becomes hard to compare when monthly equivalents, annual commitments and deployment-specific terms are presented as if they were the same thing.
Compare MIGHTY-published list prices by annual commitment or month-to-month billing, then prepare a governed estimate without browser-side price calculations.
Platform pricing becomes hard to compare when monthly equivalents, annual commitments and deployment-specific terms are presented as if they were the same thing.
MIGHTY publishes separate approved price rows for annual and month-to-month billing, while Pradiota Core returns the selected term, price and disclosure as one bounded public contract.
Annual commitment and month-to-month pricing come from separate immutable MIGHTY price rows.
Estimator results are returned by MIGHTY through Pradiota Core; the browser performs no pricing arithmetic.
Cloud, dedicated, customer-cloud and on-premises paths retain their own scope and commitment rules.
A buyer can see the lower monthly list price together with the explicit annual commitment.
The same buyer can switch to the higher month-to-month list price without annual-only plans being misrepresented.
The selected plan and billing term are submitted to MIGHTY and returned with an effective price-book reference.
Most cloud plans show a monthly list-price equivalent under a 12-month commitment. Annual-only deployment plans are labelled per year.
No. Month-to-month prices are separately published MIGHTY rows and can differ from annual-commitment rates.
No. The browser submits the selected plan and term; MIGHTY returns the governed amount from the effective price book.