# Pricing


Zerops Box has no price of its own. You pay for the Box Workspace service like for any other Zerops service, at the rates on the [Zerops pricing](/company/pricing) page.

## What you pay for

- **The workspace VM's resources.** A workspace has fixed resources and never autoscales, so you pay for the CPU cores, RAM and disk you [set](/zbox/workspace-service#resizing), whether sandboxes use them or not. CPU is billed at the shared or dedicated rate, depending on the CPU mode, shared unless you choose dedicated.
- **The project.** The project core, and optional extras such as a dedicated IPv4 address or egress over the included amount, are billed per project as usual ([pricing](/company/pricing), [top-up and billing](/company/payment)).

## What costs nothing extra

Sandboxes, bases, templates, snapshots, forks, integrations and webhooks are not billed by themselves. They use the workspace's CPU, RAM and disk, so the workspace's size limits how many of them fit ([capacity](/zbox/workspace-settings#capacity)). To run more sandboxes at once, [resize the workspace](/zbox/workspace-service#resizing) or park the sandboxes you don't need.

## While the workspace is stopped

A [stopped](/zbox/workspace-service#service-lifecycle) workspace is not billed for CPU and RAM. Its disk is still billed at the configured size, because the data disk keeps everything on it. Billing for the workspace ends only when you delete the service.