Straightforward and no surprises.
Vamp’s permission system provides control levels for team members based on a set of built-in roles (Developer, DevOps/SRE, Product Owner).
The Developer role gives users the ability to safely test their code into production and track the results. The DevOps/SRE role gives users the ability to create a technical (canary) release policy that describes how to rollout a new version of the microservice, the length evaluation period for each step in the release and when to trigger a rollback. The Product Owner role gives users the ability to define business-focussed release policies. A business release policy and a canary release policy follow the same pattern, the only difference is that a business release policy, includes one or more non-technical, business focussed metrics. The Product Owner role also gives users the ability to create custom dashboard and track important release KPIs across teams, services and applications.
A feature release is the release of a new version of a service that has not previously been seen by Vamp. This does not affect normal operations like bring up a new cluster with an existing application for maintenance or disaster recover purposes.
Releasing an older version of a service that was previously released by Vamp is not a feature release.
Migrating the latest version from one application to another, for example from acceptance to production, is not a feature release.
Vamp offers three different support packages: community-, business- and enterprise support.
You can always upgrade your support package. We offer business support for €400 p/m and enterprise support for €900 p/m.
Vamp is a SaaS solution and therefore easy to install and setup. To get started with Vamp, you only need to install our release agent. Our customers typically start releasing software with Vamp within 2 days.
Vamp is an AIOps platform for Cloud-Native Release Orchestration that makes software releases self-driving and self-healing.