Serdar Yegulalp
Senior Writer

Project Kratos: AWS Lambda functionality, without Amazon lock-in

news
Feb 11, 20162 mins

Iron.io uses Docker for a self-managing, stateless application stack, but forgoes the open source path

locked gate
Credit: Thinkstock

Amazon AWS Lambda’s premise is audacious: event-driven applications made of little more than pure functions in Python, Java, or Node.js.

Iron.io, creator of a task-queuing platform that runs across multiple clouds, is preparing a similar platform that runs on any cloud or local architecture and uses Docker containers as the basic unit of the service.

Project Kratos allows enterprises to take either existing AWS Lambda functions or Dockerized workloads and deploy them in a stateless fashion. A “runner agent” cluster listens for work queued up via Iron.io’s RESTful API. The agent cluster stores metadata about the job — whether it completed successfully, how to deal with retrying failed jobs — but all other state data has to be manually managed by the applications themselves.

While Kratos and Iron.io make use of some open source projects, the core of Kratos is not intended to be open source. Given that part of Iron.io’s plan is to avoid lock-in with services like AWS Lambda, the approach seems counterintuitive. Instead, the company will offer its protocols as an open project, with other open source elements possibly to follow.

“We don’t have much of an interest in becoming a support and services company,” said Iron.io CEO and co-founder Chad Arimura in a phone interview, citing the fate of most outfits based on open source. “Enterprises want an open source story, but they don’t want to rely on just open source software. They want a commercial offering as a complement, which they can trust running this stuff.”

The company’s success with its existing customers, Arimura said, means there’s been little momentum to become open source. “We want to put investment money into the product and the platform itself, because there’s a lot of value on top,” such as the dashboarding, reporting, and analytics solutions.

The lightweight, just-enough-code approach popularized by AWS Lambda has spawned a slew of projects that extend on it (ZappaJaws), and frank imitation from competing cloud vendors (Google Cloud Functions). But Arimura thinks of Iron.io in more general terms.

“We’re like a layer on top of all compute,” Arimura said, a “job API for developers,” as opposed to merely being “a widget that manages Docker containers.”

Iron.io is currently soliciting applications for Kratos’s public beta. Arimura anticipates a release to the general public within the next 60 days or so.

Serdar Yegulalp

Serdar Yegulalp is a senior writer at InfoWorld. A veteran technology journalist, Serdar has been writing about computers, operating systems, databases, programming, and other information technology topics for 30 years. Before joining InfoWorld in 2013, Serdar wrote for Windows Magazine, InformationWeek, Byte, and a slew of other publications. At InfoWorld, Serdar has covered software development, devops, containerization, machine learning, and artificial intelligence, winning several B2B journalism awards including a 2024 Neal Award and a 2025 Azbee Award for best instructional content and best how-to article, respectively. He currently focuses on software development tools and technologies and major programming languages including Python, Rust, Go, Zig, and Wasm. Tune into his weekly Dev with Serdar videos for programming tips and techniques and close looks at programming libraries and tools.

More from this author