Security

Cloud vs on-premises: what's the difference?

Cloud vs. on-prem explained: who owns the servers, why banks and hospitals keep data in-house, what that costs in security, and how to pentest inside the box.

  • 8 min read
  • 5 questions
  • +35 XP
Transcript

Cloud vs. on-prem, explained by cats. Kitty works at a bank. She builds an app to keep every cat’s tuna safe. It tracks who owns the tuna, who moved it, and where it is now. Now Kitty needs a place to run the app.

She could use the cloud. Azure. AWS. Google Cloud. Fast. Easy. And No servers in the office. But in the cloud, someone else owns the machines. For most cats, that’s fine. But not for every cat. Banks. Hospitals. Government. They need their data to stay private, close by, and inside their own building.

They want to keep it in the box. That’s is on-prem. Kitty owns the servers. Kitty owns the network. Kitty knows exactly where the data sleeps. That gives Kitty more control. But it also means Kitty has to protect everything in that box.

Because attackers still show up. And try to steal the tuna. So Kitty uses Aikido Machine. Aikido Machine is a box with GPUs living right inside Kitty’s network. It runs autonomous pentests all day, every day, fully inside Kitty’s building.

No cloud API. No outside model. So Kitty keeps her app inside the box and still gets continuous security testing. Which means Kitty’s data stays protected. And that makes Kitty. Happy, happy, happy.