We fell in love with Docker in 2013. What Docker catalyzed is a powerful revolution in how software is designed, built, tested, deployed, and operated.
There’s just one thing that always nagged at us: If what we’re wanting to run in containers are minimally small, ideally ephemeral, and strongly isolated microservices, then why the heck are we running them on shared OS kernels that were designed decades ago for practically the polar opposite use case?
The question isn’t philosophical. The side effects of running containers on kernels that comprise tens of millions of lines of code, most of which are completely unnecessary for container workloads, are real. Security breaches. Kilobytes of app code yielding gigabyte artifacts. And while containers start a lot faster than full-blown VMs, they aren’t nearly quick and scalable enough for true ephemerality.
We aren’t the only ones to posit that a unikernel would be a better platform for containerization. We are the first to release a solution that intimately integrates the best features of containers and unikernels.
We’re proud to publicly release Kontain for developers to learn about, try, and put to use. We’re excited to work with you. If you’re interested in working with us, please drop us a line.
THE KONTAIN timeline
- Mark and Serge did a bunch of work in and around containers
- We did a lot of research and thinking that led to the Kontain concept. More than a few world-class experts told us, “One, it’s a great idea. Two, you’ll never get it to work.”
Join our mailing list
to receive occasional technical articles, tips, and updates