Free and Pro both have a dedicated Akasha instance requirement. Free places a cap on usage; Pro provides a path to additional capacity. Your Mind's data and engine identity should carry through an upgrade.
Review before upgrading
Open Billing for the intended organization. Review the current plan, measured usage, price, and billing period shown in the live account. Public pricing can change, so this guide does not hard-code rates from a screenshot.
Minds' current commercial direction is based on infrastructure usage such as compute, storage, and transfer. Older backend templates and documents may still mention legacy tiers or Mind Units. They should not be treated as the current Free/Pro contract without reconciliation.
Separate usage from capability
A service toggle can be a resource-control choice. It should not imply that Free uses a shared memory pool or that upgrading purchases a different set of core engine APIs. An API may still be unavailable because a deployment disabled its service or its implementation is unfinished; the instance reference identifies those boundaries.
Integration status
The audit identified a missing caller/tenant boundary in the billing action proxy. No live purchase, cancellation, or billing mutation was performed during documentation testing. Use the platform billing reference for the current route contract and compatibility for verification status.