---
url: https://veles.beyondthecloud.dev/docs/intro.md
description: >-
  Veles refreshes, connects and configures your Salesforce sandboxes and scratch
  orgs so they come back ready to use.
---

# What Veles does

Veles is a Salesforce managed package. You install it in the production org that will act as the **Hub**, connect your sandboxes, scratch orgs and other production orgs to it, and from then on:

* **A refreshed sandbox comes back ready.** Veles detects the refresh, re-links the sandbox, pushes its configuration and secrets, and runs the workflow you assigned: activate users, fix emails, reset passwords, set profiles and permission sets, restore credentials, run Flows, deploy metadata.
* **Developers refresh their own sandbox.** They request it from Veles in the sandbox, keep their user, email and access through the copy, and log in to a configured org. No production login.
* **One config, every environment.** Define a configuration once with typed fields. Give each environment or environment group its own values. Code reads the right value with one line of Apex or a Flow action.
* **Secrets stay in Salesforce.** Config and credentials live in protected custom objects inside your own orgs and move only between them. No external vault, no middleware.

Everything is managed from one tab, the **Veles Command Center**, in the Hub.

## Who it is for

* **Admins and DevOps leads** who own a sandbox estate and are tired of rebuilding it after every refresh.
* **Developers** who want a fresh sandbox today without a ticket to the admin.
* **Security teams** who need secrets handled on-platform, with no third-party account to approve.

## Where it fits

Veles is not a full CI/CD pipeline. It is the native layer that keeps every org's configuration and secrets safe and gets a refreshed org ready to use, with as little setup as possible. Your release tooling (Gearset, Copado, `sf`) keeps shipping code; Veles can still deploy a metadata package as a workflow step when the refreshed org needs one. Everything lives inside your Salesforce orgs; nothing is stored or processed outside them. Today you create sandboxes and scratch orgs the usual way and Veles takes over from there; creating them from Veles is on the roadmap.

## Where to go next

1. [How it fits together](/docs/concepts): Hub, environments, groups, workflows, push and pull in five minutes.
2. [Install and set up the Hub](/docs/setup/): the Setup tab, step by step.
3. [Connect a sandbox](/docs/setup/connect-sandbox) or [a scratch org](/docs/setup/connect-scratch-org).
4. [Sandbox refresh](/docs/guide/sandbox-refresh): what happens, and how to see it happen.

Plans start at free. See [Plans and pricing](/pricing).