UiPath Document Understanding: Does a deployed model cost money even if nobody uses it?

Short answer: yes, it can. A document model deployed as an AI Center ML Skill keeps consuming AI Units at UiPath as long as it is running in "Available" or "Updating" status, regardless of whether any automation ever calls it. Anyone who simply leaves a model deployed after testing pays for pure idle time. That is exactly what a user recently asked in the UiPath Community Forum.

Why does an unused UiPath model incur costs at all?

The reason lies in billing by uptime, not by usage. As soon as an ML Skill is deployed and available in AI Center, UiPath reserves compute power for it and bills it by the hour. According to the UiPath documentation a CPU deployment costs around 2 AI Units per replica and hour, a GPU deployment around 20 AI Units per replica and hour. The standard GPU configuration reaches about 40 AI Units per hour, which works out to roughly 30,000 AI Units a month for continuous operation. Billing applies for every hour started, in which the model is "Available" or "Updating", regardless of the number of documents processed.

It's important to distinguish this from the modern, managed Document Understanding models: these cost nothing while idle, since AI Units are only incurred per page processed. The cost trap applies to the classic, self-trained models that run permanently in AI Center as an ML Skill. Many businesses calculate the UiPath license costs for SMEs, but overlook the ongoing AI Units from such deployments.

What you can do about the hidden cost trap

The most effective measure is mundane: stop or remove a model that isn't currently needed. UiPath explicitly recommends stopping or fully undeploying ML Skills when not in use, to save on hardware costs. Three steps help in everyday practice:

• Check your inventory: Regularly check in AI Center which ML Skills are set to "Available", and switch off leftovers from test phases.
• Deploy on demand: Models that only need to run at certain times can be deployed automatically via the AI Center API right before the run and stopped again afterwards.
• Monitor consumption: Use the AI Units dashboards to spot idle time early, before it adds up over months.

In our automation projects, this is exactly where we start: a document model that, for example, processes invoices automatically, is only deployed when a process actually requests it, and shut down again afterwards. This noticeably lowers ongoing AI Units costs without the automation losing any reliability.

Frequently asked questions

Does a deployed UiPath model cost money even without documents?

Yes. A model deployed as an ML Skill is billed hourly as long as it is "Available" or "Updating", regardless of the number of documents processed. Only "Stop" or "Undeploy" ends the billing.

How high are the ongoing costs of a deployed model?

A CPU deployment costs around 2 AI Units per replica and hour, a GPU deployment around 20. The standard GPU configuration adds up to roughly 30,000 AI Units a month with continuous operation.

Do the modern Document Understanding models also incur idle costs?

No. For the managed modern models, AI Units are only incurred per page processed, so idle time costs nothing. The trap applies to classic, self-hosted ML Skills.