With the release of version 7.0 and the new Standard Edition, it seemed like a good idea to revisit our mission and overall vision and strategy.

Clarive’s mission is to build an integrated DevOps product for delivering applications with an easy to use, flexible end-to-end workflow.

We aim to reduce the amazing waste that countless Dev and Ops tools alike produce, with their disjoint workflows, technologies and configuration issues.

With Clarive, teams will be able to code, track, test and deploy software without getting caught up setting up toolchains for doing only 1 or 2 things that later could become a liability. We believe DevOps toolchains have gotten to a point where they are missing a solid foundation to build upon. We want Clarive to be that foundation.

The Clarive founding team taking a break on a good afternoon

Clarive Rules

DevOps is about teams defining “what happens when”, setting the rules of the game so that teams can focus more on the innovation and less on plumbing. DevOps embodies the brain’s right-side in the great art of delivering applications. We wanted a tool where we could define these rules and run them continuously without many moving parts.

So Clarive’s vision is a platform that brings together code management tools, application change and release tracking with build, test and deployment automation into a flow that is both transparent and irrespective of methodology and maturity level.

Seems like a lot to aim for, but we are fulfilling this vision implementing very simple concepts.

Topic branches evolved

Clarive’s technology is based on the notion of tracking “changesets” that are irrespective of origin or scope, so that releases can be multi-application and multi-technology. We rely heavily on the concept of topics to abstract many change, configuration and project planning methodologies into a simple graph of interconnected goals.

Topics help the team focus on the release, adapting to any particular team size, complexity or speed. Topics are also great for insight and easy to navigate.

The idea of “topics” was borrowed from Git’s simple approach to branching. Git’s branching is simple and lightweight. Its graph of changes is one of the most revolutionary concepts to enter the mindset of development teams in the last 10 years. Git topic branches make it easy to experiment, reuse and discard changes. Clarive expands on that concept by bringing topics to the workflow.

Our topic graph bootstraps ideas, features, bugs and make them scale up and down in your list of priorities with a solid kanban, our DevOps kanban board. In Clarive topics can materialize any item, task or story, be them long or short-lived, as they move from idea to production.

DevOps Microservices

To support the topic workflow, Clarive implements automation rules that can be triggered at every stage of the DevOps lifecycle. If a matching rule is found, Clarive runs it. Our rule-based automation engine is powered by container technology and we’re driving the product towards becoming a DevOps microservices platform.

Every service in your DevOps toolchain is then unified and can be used easily from every project or repository. We call that orchestration.

Today Clarive is an accomplished platform for delivering applications fast and reliably. As we move forward, we plan to strengthen our solution as a leader in application delivery by empowering our users in key areas:

• Advanced rule automation features that help manage deployments at scale.
• A fully integrated Docker registry and container platform targeting short-lived pipelines.
• Planning and collaboration enhancements and lots of insight – with a little help from our AI engine.

We think our roadmap is well geared towards making Clarive a great DevOps foundation that is both robust and lean.

– Rodrigo