@@ -139,6 +139,25 @@ Deleting workers that will not be used anymore is not always possible, because A
Archived workers **can no longer be used in processes**, and are displayed in their own tab in the workers list. It is possible to archive a worker from the Arkindex frontend, but an archived worker can only be made available again by an instance administrator from the admin interface.
## Costs
Multiple execution costs can be defined on workers:
**Hourly CPU cost**
: Cost of running any of this worker's versions without a GPU for an hour.
**Hourly GPU cost**
: Cost of running any of this worker's versions with a GPU for an hour.
**Cost per 1000 elements**
: Cost of running any of this worker's versions on 1000 elements in an inference process.
These costs allow to report the real hardware costs of executing workers to end users.
All costs are expressed in euros, have a precision of up to three decimal places, and can range from `0.000` to `99999.999`. They are set to `0.000` by default, meaning there are no costs for running a worker. They can only be configured through the [administration interface](../deployment/administration.md#administration-interface).
When any of these costs is set to any value above zero, all costs will be displayed when viewing the details of a worker, and a `€` icon will be shown next to the worker name.
## Secrets
Some workers may require the use of **Secrets**, like for example an authentication token to interact with an external API. See the dedicated [secrets documentation](../secrets/index.md).
