Ready. Set. Deploy

Optimizing and automating the processes of initializing and configuring cloud servers and the applications that run on them makes deploying applications through Standing Cloud seem point-click-simple. What goes on behind the scenes is way more complicated.

Think spinning up a virtual server, optimizing the application, installing the base code, and standardizing the data and configuration locations. And that's just for starters.

The Server Layer

We start with a clean server image from one of our 15+ supported cloud providers, integrating directly with their API. Once we've spun up a virtual machine, we install the stack and any supporting software needed by the application.

The steps may vary depending upon the stack the application requires. For example, our LAMP application installation performs installations of Apache, PHP and MySQL. But across the board, the operating system, server software and underlying application stack are all scripted and automated for best practice configurations, and optimized for application performance.

The Application Layer

After the server image is prepared and the stack installed, we install the application layer. This includes the base application code, and the application data and configuration. The custom configurations for the application are standardized and stored in a common location regardless of the cloud or operating system running underneath.

And here's where it really gets good. Unlike standard deployment using application images, all of our server and app configuration steps are scripted on the deployment server directly — nothing is staged ahead of time. This means that any configuration changes users make through our interface are done directly to the server.

Back-up, Restore and Beyond

Our standardized app code locations make automated backups, application recovery and cross cloud porting simple. When a user restores an application, on the same cloud provider or a new one, the system spins up a new stack and application install, then adds in the existing application data. This gives the user a fresh install, using the existing application data and configuration.

If a user makes manual changes to any of the configuration files, however, those changes may be lost if the app is shutdown and restored to a cloud provider using a different distribution than what the app was on previously. In the future, the system will maintain all of the AMP software in a common location regardless of distribution, so all changes will be maintained, and cross-cloud migration will be completely transparent.

Learn more about some key features. Explore our solutions.