Do Not Trust or Kata Containers

Do Not Trust or Kata Containers

Since writing this post, has pivoted and no longer offers its container hosting. They gave users less than a month to move off their platform, so I no longer recommend working with Hyper or Kata Containers. The company never gave me a reason for the shutdown, and refused to offer any substantial tools to help with migration. Do not trust this company for your production workloads.

I’ve been doing a lot of searching for a simple Docker hosting experience lately.

I’m pretty committed to Docker Compose for running containers locally and Codeship for my continuous integration, but I hadn’t found a container hosting service that was (1) simple enough for me to use on side projects, (2) reliable enough to use in production, and (3) not prohibitively expensive.

My goal this weekend was to get a couple side projects up and running on, and here’s how it went.

About the projects

Both the projects I wanted to deploy this weekend were NodeJS apps: my personal blog, and a microservice that emails me the latest articles from Feedbin every day.

Currently, both projects were set up on a Digital Ocean droplet and running with Docker Compose. That meant that I had to write a lot of scripts to automate deployments, and it was honestly a huge pain point. I’ve found that for side projects if I don’t automate the minor stuff (deployments, CI, etc.) I probably won’t update them very often. Digital Ocean droplets are great, but each one cost me at least $10 (the $5 ones couldn’t build my Docker images reliably), and running multiple side projects on each was problematic. If one went down or had a memory leak, it would take other ones down with it. Another option I’ve used in the past is Heroku, which I also like, but I don’t know about its support for Docker. If anyone’s tried that I’d be willing to hear about it.

Since my semi-automated process hosting on Digital Ocean wasn’t working well for these two apps, I decided to find an alternative.

What is

I read about on HackerNews a while back. I liked the idea of container-first infrastructure, and I first got an MVP of my personal blog running on their containers back in February. I didn’t migrate then though as I hadn’t figured out how to move data around, so when I sat down this weekend, I realized that it would actually work pretty well for my workflow.

My workflow

So here’s how I’m using for both of the projects mentioned above:

For my personal blog, I downloaded my blog’s data (it’s using json files and NEDB) from its current server and created a Volume. I then attached it to a container that runs the NodeJS process using a Hyper Compose file. Then I attached the container to a FIP which I mask using CloudFlare for DNS.

Now when you go to you’re getting served a Node app running on a 512MB container which costs a fraction of what my DigitalOcean container did. It’s also easier to manage. When I update code and push it, Codeship builds the image, pushes it to Docker Hub, then uses a CLI container to pull and recreate the container.

The feedbin-mailer project is even easier since it doesn’t need a webserver. When I update code, I again use the CLI container to update the image, then I set up a Cron job to automatically run the script every morning.

What I like

  • UI It’s nice to see what’s running and when it was last updated without typing a bunch of stuff into the CLI, although their CLI is pretty nice too. The --help flag works for every command I’ve used.
  • Documentation Almost every question I’ve had has been answered by a closer read of the documentation.
  • Pricing I agree with’s pricing page, it is a crime to pay just to power on an instance. For most of my side projects, using a whole server just to host a few hundred visitors per month (or simply run a Node script every day) is very wasteful.
  • Support Finally, the team at has been pretty responsive considering I think there are just four of them. They’ve always pointed me in the right direction for documentation I’ve missed and usually gotten back to my posts on the forum.

What could improve

  • More community engagement The forum is there, but there are just a few people posting on it. If they’ve got users, maybe a little time spent on marketing to them or rewarding active participants would be well spent. I’m sure there are people out there who have tread the same problems I faced while setting up
  • More examples and use-cases One thing that larger hosting companies do well (Digital Ocean being probably the best) is provide clear, step-by-step tutorials for lots of use cases. I’d start by documenting tutorials for using to host 5 or 10 of their most popular stacks. If anyone at is listening, I’d be happy to contribute, just reach out.
  • Dealing with volumes Finally, I did find some operations with volumes to be a little less intuitive than I had hoped.
    • First, there’s not an easy way to download or back up a volume’s contents to my machine. My plan is to write a Docker container to do this via S3 or something, but something like hyper volume download <VOLUME NAME> would be amazing.
    • Second, there isn’t a way to disconnect a volume from a container and then reconnect it to another without taking the container down. I was hoping to do this for my deployment process.
    • Third, using volumes in multiple containers is a pain. You have to set up a shared volume container which then uses NFS to allow each container to attach to it. I am not enough of a Docker expert to propose a better solution, but I’m hoping they come up with something.

Since writing this post, shut down and gave users less than a month to move off their platform. I do not recommend working with Hyper or Kata Containers. The company never gave me a reason for the shutdown, and refused to offer any substantial tools to help with migration. Do not trust this company for your production workloads.