Creating production-like environments is a pain and complex, but they are an important best practice for being able to work, debug and test on to prevent any errors or bottlenecks before reaching production.
Velocity lets you move fast and deliver better products, with the autonomy to spin up fully isolated production-like environments on-demand.
Here you'll find documentation to help you get started with using Velocity including best practices, use cases, and how-to guides.

Traditional Staging is Not Enough:

Staging environments are an important place where you validate and test code in an environment that is almost like production. However, these processes become much more difficult when you’re dealing with more complex architectures such as microservices and cloud-native applications.
So what happens when something changes in your applications' production infrastructure? ‌Or multiple dependencies need to interact and integrate with different components?
Velocity is set up to read, analyze and sync your application infrastructure and provision on-demand, production-like environments in real-time. So no matter how many components need to be integrated for you to develop or debug a feature, you will still have access to all that environments' dependencies. And you get the autonomy to create these environments as often as you need, so there is no need to be blocked by any bottlenecks that come with a shared, staging environment.

How Velocity Works

  • Using read-only access, Velocity connects to your source control, CI/CD, and cloud account to extract the relevant information and automatically identify your environment’s dependency graph
  • Developers provision their own environments, working on their own machine while the rest of the environment is running on YOUR CLOUD
  • On-demand environments are continuously synchronized with the definition of production, so environments are always kept up to date. For example, if you change the docker-compose, Kubernetes resources, or helm charts, Velocity will identify the change and sync automatically.
  • Destroy environments, or enable time-to-live, when you've finished using your environment. You can check status and logs to enable maximum resource utilization.