Iron.io introduces Project Kratos
Shortly after raising $8 million for its enterprise cloud infrastructure services, San Francisco-based startup Iron.io introduced Project Kratos which promises to enable companies ” to run AWS Lambda functionality in any cloud provider, as well as on-premise, eliminating vendor lock-in,” according to the project description.
AWS Lambda is a managed service for running Python, Java and Node,js in the Amazon cloud. It provides automatic scaling and users can have code run in response to events such as alterations to objects in cloud storage, database updates or calls to a REST API from mobile or IoT devices.
Iron.io created Project Kratos so that enterprises can deploy their existent AWS Lambda functions and Docker container-based workloads in a stateless manner. A “runner agent” uses the startup’s RESTful API to pay attention when work is queued up and stores metadata about the job. However, all other state data must be manually operated by the applications themselves.
Project Kratos’ main features
Iron.io CTO Travis Reeder told The Register that companies must be careful about being lock-in to one cloud provider and hinted that Project Kratos is a good solution because just like the startup’s main microservices platform for job processing applications, it can be installed anywhere. Reeder emphasized that Iron.io believes in open protocols and in enabling developers to run their code anywhere and that they have developer a layer where Lambda functions can be deployed. ” Google just announced Cloud Functions and we’ll add support for those,” the CTO of Iron.io added.
To ensure that Project Kratos functions flawlessly,the San Francisco-based startup’s platform must be functional. The platform offers added functionality such as reporting and dashboards, auto-scaling and intelligent workload distribution, according to Iron.io. The company’s CEO Chad Arimura told the British technology news and opinion website that workloads can be sent to a low-cost provider outside of peak times and save money when users have full control of where they are running. Another advantage of Project Kratos is that companies will now have the advantage of choosing specialized infrastructure, ” such as a particular chipset that might benefit your particular workload,” Arimura explained. ” We don’t look at the price comparison. We have an implement and extend strategy, you’re getting so much more,” he added.
The only problem that might keep some people away from Project Kratos is that a dependency on the startup’s platform may be created. For those who want to have a plan B, running Microsoft’s Azure Stack in their own database is doable, but they have to be ready to literally pay the price.
The product description also states that “Iron.io is currently seeking project members, who will provide input and feedback as the project is developed. Project members will have the option of becoming beta users.”
The San Francisco-based startup announced in September 2015 that it has raised a $8 million Series A round. In the announcement, Arimura revealed that Iron.io is “at a critical juncture in software, where applications are continuing to break down in smaller distributed services” which generate a plethora of low-key events ” across a host of cloud and on-premise infrastructure.” The CEO told his audience that the company he leads is ” the glue ensuring those compute tasks always happen no matter the scale,” thus allowing companies to deploy new applications fast.
Before the Series A round in late 2015, Iron.io managed to secure a total of $5.5 million in seed funding.