- Get Stackato
- Why a Private PaaS?
- Features & Benefits
- Stackato by Language
- Compare Editions
- Stackato & Cloud Foundry
- Developer Tools
- Professional Services
- Commercial Support
- Code Recipes
Brent Smithurst, December 18, 2013
After 41 days in beta, Stackato v3.0 is finally available! As I wrote when the beta was made available, this is a truly massive and major release that provides tons of new functionality. Phil Whelan's post on the technical details of the beta has all of the key details and they still apply to the final release. The TL;DR version is that Stackato has a new Cloud Foundry v2 base, Docker for application containers, an all-new web console, Activity Streams from our Appsecute acquisition, and much more.
As always, the forum post, release notes, and press release have all of the details. This time, we've even added a dedicated Stackato v3.0 "What's New" page that lists the key features (I won't repeat them all here). Go get it now! Micro clouds and Amazon EC2 AMIs are available now; a hosted HP Cloud version will be available shortly. Our Sandbox is currently being migrated from AWS to HP Cloud, and will be available in the v3.0 flavor real soon now too.
If you tried the beta, this final release has signifcant improvements that are listed in the release notes. Notably, the rewritten web console has had some pretty dramatic improvements since then and literally a ton (I weighed them personally) of under-the-hood and stability improvements have been made.
So, current Stackato users should check this out; I think you're going to love it! Non-Stackato users who want an easy to use, yet powerful way to develop and deploy software solutions faster than ever before and manage them more effectively should check it out too.
As always, I want to hear from you—please let me know (via Twitter, brents+feedback [at] activestate [dot] com (subject: Stackato%203.0%20Feedback) (email), a comment below, or our Stackato discussion forum) what you like, don't like, or what problems you have that Stackato doesn't currently solve.