# How much infrastructure costs

A server's cost depends on its plan, running and sleeping time, and extra disk capacity. Bitrix24 Cloud prices are in Vibe credits.

## How Vibe credits are charged

You pay for actual usage time rather than buying a month of runtime in advance. Costs are calculated by the minute within hourly accounting intervals. A server has no monthly term to renew: charges continue while it exists, according to its state.

Retrieve current rates from [Provider plans](/docs/infra/providers/plans):

```bash
curl -H "X-Api-Key: YOUR_API_KEY" \
  https://vibecode.bitrix24.com/v1/infra/providers/bitrix-cloud/plans
```

| Plan field | Meaning |
|-------------|----------|
| `priceMonthly` | Rate for a running server for a billing month. |
| `sleepPriceMonthly` | Rate for a sleeping server for a billing month. The field may be absent. |
| `currency` | Price unit: `"Vibes"`, Vibe credits. |

Prices reflect payer-specific settings, so request them with your own personal key. A billing month is 30 days, or 43,200 minutes. When both rates are available, the approximate base-plan cost is:

```text
priceMonthly × runningMinutes / 43200
+ sleepPriceMonthly × sleepingMinutes / 43200
```

Intervals are rounded to whole minutes. Whether hours spent entirely asleep are billed depends on platform settings. Extra disk capacity is billed separately.

You can create a server for a few days of testing and then delete it. Charges are proportional to running and sleeping time. Stopping or deleting a server leaves no prepaid remainder of a month to use up or refund.

## How to stop charges

[Stopping a server](/docs/infra/lifecycle/stop) and [sleep](/docs/infra/lifecycle/sleep) stop the application and switch the server to its sleeping rate. This does not mean zero cost: the disk is retained, and extra disk capacity is also billed at its sleeping rate. Waking restores the running rate. Account for [automatic wake](/docs/infra/lifecycle/wake) and configured [schedules](/docs/infra/wake-schedules).

To stop further charges for the server itself, [delete it](/docs/infra/servers/delete). Retained backups are separate resources: stopping a server does not delete them or end charges for their storage.

## Plan availability

Bitrix24 Cloud plans on `.com` are non-preemptible. They are not subject to the forced daily restarts associated with preemptible plans.

Plans differ in resources and price. Choose the capacity your application needs and account for running and sleeping time when estimating its cost. A non-preemptible plan does not remove application downtime caused by sleep or a billing freeze.

## If Vibe credits run out

When infrastructure is frozen for non-payment, servers stop and the application becomes unavailable. Starting and waking are blocked with `ACCOUNT_FROZEN`. Check infrastructure state through [`GET /v1/me`](/docs/keys-auth): `data.infraState.frozen` indicates a freeze, and `data.infraState.topupUrl` provides the top-up URL.

Top up the balance to lift the freeze. Server data is retained until the server is deleted. A prolonged freeze can lead to deletion: the period is set by platform settings and defaults to 33 days. Deletion also depends on the deletion procedure being enabled and a recent backup being available. Do not treat this period as a guaranteed retention time. The backup created before this deletion has a separate recovery window, defaulting to 30 days after deletion. Once the server is deleted, recovery from a backup is required. Topping up alone is not enough.

Loss of access under your Bitrix24 plan is a separate restriction. On `.com`, infrastructure access depends on the Bitrix24 plan, with full access offered through the Vibe+ plan line. Operations can return `INT_TARIFF_REQUIRED` or, for accounts requiring a Vibe+ plan, `INT_VIBE_PLUS_REQUIRED`. When access ends, the platform can put servers to sleep and block waking them. Accounts requiring a Vibe+ plan are exempt from that general access-expiry shutdown. A Vibe+ trial server is handled separately: when its trial ends, it is frozen and waking returns `VIBE_DEMO_EXPIRED` until the account has a paid Vibe+ plan. To restore access, switch back to the required plan. Topping up Vibe credits alone does not replace it.

## What is preserved

Sleep and a temporary freeze stop execution without deleting the disk. Deployed code and configured environment variables are retained. Process state in memory is not retained: the application must be able to start again.

On a standalone virtual machine, files remain on its disk until deletion. For data that must also survive redeployment, use a separate directory, such as `/opt/data`, and the `dataDirs` setting described in [Upload code](/docs/infra/deploy/deploy).

A [Galaxy app](/docs/infra/galaxy) runs its code in a container, with environment variables passed at startup. Store persistent data in `/data`: this directory is mounted as a separate volume and survives container recreation. Files in the code directory do not replace persistent storage. Retaining the disk during a stop does not mean indefinite retention after a freeze or deletion.

## Where to see spending

Open [Billing](/billing) → the **Overview** tab. The remaining Vibe credits appear under **Available**. View charges for a selected period on the **Transactions** tab in **Billing**.

## See also

- [Provider plans](/docs/infra/providers/plans)
- [Stop a server](/docs/infra/lifecycle/stop)
- [Delete a server](/docs/infra/servers/delete)
- [Galaxy app](/docs/infra/galaxy)