Introducing Kriten: Your api-driven execution environment

Automation can significantly increase the speed and accuracy of running IT infrastructure, whether cloud or on-premise. Having worked in IT automation for many years, we have developed Kriten to address some of the major inhibitors of IT automation adoption.

Leverage your knowledge

The people best placed to automate systems are the people who run them. IT teams are using automation platforms and learning coding and DevOps practises. Running code in an enterprise environment can be challenging, setting up servers and installing dependencies, providing access etc.

With Kriten, code can be made available to run with two commands (three if you include login).

Share your knowledge, securely

A common problem is that engineering teams do not want to expose system level privileges, which limits access to automation routines. Kriten jobs are launched from a job specific URL. The users have no access to the code, usernames, system accounts or any secret data.

Kriten has granular RBAC, so you can specify exactly which users should be able to launch jobs.

use what you have, with central control

Anything that can be run in a container can be run on Kriten. What ever mix of languages and platform you have now or in the future does not need to change. Using Kriten gives a central point of control for access to automation jobs, so you can specify who can administer jobs, who can run them, and have an audit log of events.