---
url: https://veles.beyondthecloud.dev/pricing.md
description: Veles plans, prices, limits and which features each plan includes.
---

# Plans and pricing

Every plan includes the whole refresh loop: refresh detection, auto-push and workflows after refresh. Paid plans are priced per production org, per month, and cover every user in that org plus all sandboxes and scratch orgs connected to it. No seat counts.

|                                                               | Free       | Standard                        | Enterprise                        |
| ------------------------------------------------------------- | ---------- | ------------------------------- | --------------------------------- |
| Price                                                         | $0         | $500 / month per production org | $1,200 / month per production org |
| Trial                                                         | not needed | 14 days                         | 14 days                           |
| Connected orgs                                                | 2          | 25                              | Unlimited                         |
| Config fields                                                 | 25         | Unlimited                       | Unlimited                         |
| Workflows                                                     | 1          | Unlimited                       | Unlimited                         |
| Environment groups                                            | 1          | Unlimited                       | Unlimited                         |
| Refresh detection, auto-push, workflows after refresh         | Yes        | Yes                             | Yes                               |
| All built-in actions and User Setup                           | Yes        | Yes                             | Yes                               |
| Credential merge fields                                       | Yes        | Yes                             | Yes                               |
| Encrypted export and import                                   | Yes        | Yes                             | Yes                               |
| Custom Apex actions                                           |            |                                 | Yes                               |
| Multi-hub: a Hub per region or subsidiary, reporting to yours |            |                                 | Yes                               |
| Audit log of deleted configs                                  |            |                                 | Yes                               |
| Configurable retention policies                               |            |                                 | Yes                               |
| Support                                                       | Community  | Email, 24 h response            | Chat, 4 h response, onboarding    |

Start on Free from the AppExchange listing. To start a trial or upgrade, [contact us](https://beyondthecloud.dev/contact).

## What counts as a connected org

The connected-orgs limit counts, per Hub: sandboxes, other production orgs (including a child Hub) and active scratch orgs. It does not count the Hub itself or the Hub it reports to. Scratch orgs that expire free their slot; on a Dev Hub Veles reads the real status, elsewhere a scratch org counts for 30 days.

A config field is one field of a configuration. The Configuration list groups fields by config name, so 25 fields is roughly five configs of three to five fields each.

## When you hit a limit

Veles tells you in place: the **New Config**, **New Environment**, **New Workflow** and **New Group** buttons explain the limit, and the message names the plan. Everything you already created keeps working; only new records are blocked. On a child org the message names the Hub whose plan applies.

## If a plan is lowered

Nothing is deleted. Orgs, workflows, groups and config fields over the new limit keep working and stay editable; only new ones are blocked. A custom action step stops at run time with one logged line, built-in steps keep running. An existing sub-hub keeps reporting. Children follow the Hub's plan on their next push or pull.

## How the plan is applied

Your Hub's plan is set on its Veles licence. Sandboxes and scratch orgs connected to the Hub inherit it; Setup shows **Plan: Standard (inherited from Hub ...)** on a child. Each licensed production org, including a child Hub, is its own subscription.