A single application, or process, without its dependencies. A service can be a micro-service in a complex micro-service architecture, or a large self-contained monolith without external dependencies.

Developing Services

Developing services refers to changing one or more services in a development session and testing them using an ephemeral environment. Velocity supports two development modes:
  1. 1.
    Develop code locally with remote dependencies running in the cloud environment.
  2. 2.
    Run a full environment remotely while syncing local file changes with remote containers (hot-reload).


A blueprint holds all the definitions needed to create ephemeral environments, including: services, dependencies and other deployment configurations.
A blueprint may also include the definition of database seeding jobs or testing tools that help the developer use the environment effectively.
Velocity's blueprints are defined using industry-standard formats and tooling – i.e, Docker Compose, Kubernetes Resources, Helm and Kustomize.


The running version, or instance, created when a blueprint is instantiated via the Velocity CLI or IDE extensions. An environment can span both local and cloud-hosted compute resources, and it contains the various services that make up a given application.


A representation of data that has been captured from a production environment at a specific point in time. This data can then be injected into a development environment to replicate “real world” data while developing a given service.

Development Candidates

When you create a new environment in Velocity, you only need to specify the services you wish to develop. These are your development candidates. Velocity will automatically detect all their dependencies, and will provide you with a working environment for the selected development candidates.


The Portal is a long-living process that runs in your local computer in the background and manages all the tunnels between your local machine and the remote environment.