Why developer/developer teams should use?

Old School FTP Uploads

Certainly you should never ever use FTP Uploads. FTP Protocol sends your ftp username and passwords as plain text over the network. Which means you are exposing your credentials to the world.

If you are doing simple websites for your online presence, Its ok to upload all the files to the server once or twice. If you are daily working on applications like job portals, Matrimony Portal and adding new features everyday. You might be working on a couple of javascript files, Updating few template files in php, and few more php files. Your files could be in multiple different folders. When you upload you need to remember to upload each and every files that you need to uploaded.


This approach is not ATOMIC or Instantaneous, Meaning till you upload each files, the changes will be incremental, Sometimes it would be breaking your website. Not all your changes would go instantaneous or the user sees all your changes instantaneous.

Since its a manual process, its very much tedious and error prone.

Medieval School

Version control system are not deployment system.

You don't require a complex configuration and setup of version control system to use it for your deployments. Moreover you need to have lots sysadmin or devops skills to setup properly, otherwise you would invite a lot of security breaches.

One such example:

If you keep your web folder /var/www/html/project as your git or svn working directory. You tend to give your .git folder inside your project folder to the hackers, could even compromise your whole website.

You can't execute pre deployment tasks before your deployment using git. For Ex. doing a complete static code analysis of your php project. Running complete set of unit tests.


Rollout uses industry standard OpenSSH Protocol for all its remote task execution, Hence its 100% secure.

Rollout updates only changes to the remote server. Hence rollout is fast.

If anything goes wrong after your rollout, Just click on rollback, Your website changes would be reverted to previous version.

Its completely automated, So No Error.

Rollout is made as recipe based, so you can add any number of steps before deployments.

Builtin steps
  • Check for required PHP Version on the hosting server.
  • Check for required PHP extensions are present or not.
  • Install dependencies via composer
  • Create Shared folders ( like media folders that are common across all versions )
  • After deployment, it checks the health of the server.

It doesn't require more than 2 min. to setup rollout for your project.

Rollout saves lot of your time. Focus more on development than on deployment.

Why IT Organisation should use?

Save Time

Saves 70% of time of developers spent in debugging production deployment related issues.

Increase Productivity

Developers can focus more on Development rather on deployments, thereby increases Developer's Productivity greatly by 70%.

Save Money

Time is Money, Saving Time is Saving Money. Penny Saved is Penny Earned.

Setup your project in minutes

All you need to do is

  1. Give your project a Name
  2. Provide ther version of your PHP that you use on your DEV BOX eg. PHP 5.6
  3. Mention all the PHP extensions that you use in your application
  4. Select the git service you use, and Key in your username and password. Rollout will automatically grab the repositories for you. Just pick one that you require.
  5. Add your slack team info and get your team notified on the slack.
  6. Provide Staging Server, Production Server [more info]
  7. Make sure your configurations are correct by doing "Test Connection"

Deploying your first project using Rollout

Watch the full video, to know more about how to perform automated php deployment using rollout, single click rollback.

Baked for you as Recipe

Recipe are prebuilt steps that are executed with your project config settings

  • Step 1: Check PHP Version on the cloud.

    Make sure your cloud server PHP version meets your required version.

    Lots of functions get depreciated in newer versions and if you upload your codebase without this check, your application may break in several places. You will be wasting lots of time in debugging your breaking code and fixing.

  • Step 2: Check if all your required extensions are present

    At times as you build new features you may be using extensions. Many times you tend to forget installation of these extensions on your server. Rollout checks all your required extensions are already installed or not. If it is not installed, it will halt the installation.

    This prevents code getting broken due to a missing extension on the cloud. Hence it saves a lot of your time to find the reason for broken code and install the missing extensions.

  • Step 3: Dependency Installation via Composer

    Just commit your composer.json, composer.lock on alongside in your project. Rollout automatically installs all the required libraries via composer

  • Step 4: Check for code quality project

    There could be errors in your code even after lots of quality assurance checks. Roll-out does a complete code quality on your codebase and make sure nothing breaks after your code is uploaded to the live servers.

  • Step 4: Atomic Deployment / Download your code from your git repository

    Rollout works seamlessly with both github and bitbucket. Downloads the code in a new release folder. Finally once your code is downloaded. rollout makes this new release folder as active.

Supported Cloud Platforms

We support all the cloud platforms are available. Here are some of them we support.

Amazon Web Services


Google Cloud




Use Rollout To deploy

It can be CMS, E-Commerce Platform like Magento or It could be a webapp built with frameworks like codeigniter, laravel, yii. Or it could be event a custom application built with Plain / vanilla PHP. Rollout will help you to deploy on to the cloud.





Yii 1 & 2


Custom Apps

Use Rollout To Migrate

Are you looking to migrate your website from shared hosting server to cloud service but don’t have the technical know-how to do it by yourself? Talk to our migration team today about migrate your website. Moving your website from one hosting provider to another can sometimes present unforeseen technical problems as web server technologies can vary from one platform to another. We will however be able to determine the majority of these issues in advance of completing a migration ensuring minimum or no downtime.

If you would like our team to review your website and provide you with a migration proposal, please drop us a line @ info@grandappstudio.in .


No Credit Card Required for signup!

Special offer for 91SpringBoard members.

First 50 Signups get 50% off.

Do Unlimited Rollouts and Rollbacks @ $ 20 Per Project / Month


One of the best finalist of Feb 2018 @ Startupsclub.