- Get Stackato
- Why a Private PaaS?
- Features & Benefits
- Stackato by Language
- Compare Editions
- Stackato & Cloud Foundry
- Developer Tools
- Stackato Training
- Professional Services
- Commercial Support
- Code Recipes
Angie Hirata, October 13, 2011
While Stackato is still in beta, we've been having conversations with many companies that are testing Stackato as a private PaaS platform. Whether large companies or private cloud operators, they seem to fall into two categories when it comes to how they view the underlying infrastructure of their private cloud.
1. Some are 100% VMware, and run their private cloud on vSphere, vCenter, vCloud Director - the VMware cloud infrastructure stack.
2. Others are split between a few different virtualization technologies, including vSphere, KVM, Xen, and others. They've either implemented different ones, or are looking to diversify the technologies they use. Some of these companies are open source supporters so lean towards KVM or Xen. Others want commercially backed options, but still don't want to be tied to a single vendor for their virtualization.
We built Stackato as a private PaaS platform that would work with whatever underlying infrastructure a customer chose. Our first implementation and testing was done on vSphere. Then on Amazon EC2. And now, with feedback from the Stackato beta testers, we are more closely and quickly looking at testing with other popular technologies.
Have feedback for us? Share your comments! Or better yet, join the Stackato beta and test out a private PaaS as a micro cloud (VM) or in our Amazon EC2 Sandbox.
And stay tuned for more news on infrastructure support!