Search…
Why Should I Use Velocity?
Ever wasted hours maintaining and configuring environment setups, or waited to deploy to a shared staging environment to make one change? How about trying to develop or test something for a new feature, but without access to real use case context, services and databases?
With the rise of microservices and cloud-native applications, environments are becoming more complex. Features are made up of multiple components, and multiple developers need to work in parallel on their different moving parts. If you want to build anything in the feature, you need to wait or compete to get access to develop on a specific microservice, or can spend time waiting to deploy to a shared staging environment only to realize something already changed, and you're back to square one.
While you can work on pieces or components locally, how do you know it will really work and integrate with the rest of the application when it ships to production?
“It works on my machine!” only goes so far, and you don't want to be the cause of any unwanted changes or defects that cost the organization tens of millions of dollars. Ephemeral environments are a powerful way to ensure fully-baked features get into production, and fast.
With Velocity, you get the autonomy to spin up an isolated production-like environment on-demand to work, develop, test and debug against. This allows you to increase the assurance your code will work well in production - without the costs of maintenance or lack of resources.

Work locally with your existing dev toolbox:

Instantly spin up self-served ephemeral environments as part of every pull request. Work locally in your IDE to develop and debug, while your application’s dependencies run remotely. Self-serve also eliminates the bottlenecks of waiting for other teams to create environments, as every developer can create their own production-like environment, automatically, when they need it.
Work with your current tools:
Velocity automatically maps and configures your application infrastructure so you can develop and test multiple services in an environment that runs just like it would in production. Velocity is fully agnostic to your cloud and tech stack, as opposed to just focusing on Kubernetes-only environments. This means working on applications in parallel without disrupting one another, with full access to data and 3rd party dependencies.

Automatic Configuration & No Maintenance:

Velocity automatically configures and updates any changes within the production infrastructure’s mapping in real-time so ephemeral environments will always be synced with what is in production. Instead of having to spend time making sure any changes are configured, you will always have the right environment that replicates production, without having to wait.

Data & 3rd Party Dependencies:

Environments are complex, and don’t end with just the cluster. There are many additional elements such as AWS DynamoDB and Google Pub/Sub, and other 3rd party resources that are vital parts of the environment to test, work and debug against. Having the relevant data inside ephemeral environments is crucial to reflect real use cases that will occur in production. Velocity loads the relevant data so environments will be as close as possible to working on production.

Team Collaboration:

Ephemeral environments are a good way of previewing what the product will actually look like, while also enabling immediate fixes. With every isolated, environment spun up, you will get a custom URL that you can use to preview and share with other stakeholders so they get visibility and collaborate for faster feedback cycles. You can also share the custom URL while you debug some of the environment locally, or even purposely break things to preview in CI/CD and identify errors before reaching production.
Share progress with Custom URLs
Last modified 1mo ago
Copy link