> For the complete documentation index, see [llms.txt](https://docs.appfactor.io/52eJroWboQfTwsFl14gL/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appfactor.io/52eJroWboQfTwsFl14gL/docs-billing/pricing-and-billing/pricing.md).

# Pricing

## Pricing Model Overview

The AppFactor platform uses a hybrid pricing model combining a ***fixed platform subscription*** with a ***consumption-based usage element***. This ensures predictable core costs while directly aligning variable workload with consumption. 

<table><thead><tr><th width="208.86328125">Component</th><th>Description</th><th>Key Characteristics</th></tr></thead><tbody><tr><td><strong>Platform Subscription Fee</strong></td><td>Annual subscription providing access to the core platform</td><td>Includes secure hosting, base support, and enterprise-grade SLA</td></tr><tr><td><strong>Consumption Usage (AWU – AppFactor Work Units)</strong></td><td>Usage-based model where AWUs represent executed platform work</td><td>Covers compute, AI usage, and automation tasks; deducted from a prepaid balance upon successful completion</td></tr></tbody></table>

***

## AppFactor Work Units (AWUs)

### What an AWU Is

An AppFactor Work Unit (AWU) measures execution capacity across automated activities such as assessments, deployments, or modernization tasks. AWUs are designed as a flexible measure of effort rather than a fixed count of operations.&#x20;

### When AWUs Are Consumed

AWUs are deducted only for *completed, successful operations* that produce a tangible outcome. Retried, rolled-back, or internal housekeeping activities do not consume AWUs.&#x20;

### What Doesn’t Consume AWUs

The following are not charged against your AWU balance:

* System-level orchestration or monitoring
* Failed or rolled-back work without a successful deliverable
* Activities included within the Platform Fee <br>

***

## Subscription Term

The minimum term for the platform subscription is 12 months to support adoption and value realization with predictable costs. <br>

***

## Global Consistency

Pricing for platform subscription and AWU consumption is consistent worldwide and does not vary by geographic region or data residency. <br>

***

## Usage Management

* AWUs are purchased in advance as part of your subscription or via top-ups.&#x20;
* You can optionally enable auto-reload to automatically add AWUs when your balance runs low.&#x20;
* AWUs are shared across teams, projects, or business units at the platform level, simplifying cost allocation. <br>

***

## Monitoring & Reporting

Within the AppFactor admin interface you can view:

* Total AWUs consumed
* Remaining AWU balance
* Consumption history and trends <br>

***

## Budgeting & Forecasting

AppFactor provides tools to help forecast costs based on application size, task complexity, and expected work units consumed. This supports planning and budgeting for modernization or maintenance objectives. <br>

***

## Support & SLA

Your platform subscription includes access to enterprise-grade support according to the SLA defined for your tier.  More information here [SLA](/52eJroWboQfTwsFl14gL/docs-billing/sla/uptime-sla.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.appfactor.io/52eJroWboQfTwsFl14gL/docs-billing/pricing-and-billing/pricing.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.