Announcing Aerobatic transition from Bitbucket

Tuesday, Jan 24, 2017

TL;DR; Aerobatic is transitioning from a Bitbucket add-on to a standalone CLI and web dashboard. You can still auto-deploy your sites with each push using Bitbucket Pipelines. In order to maintain continuous deployment, be sure to migrate your sites by March 1st 2017 when the Aerobatic Bitbucket add-on is retired. Your sites will continue to load fine after that date, even if you don’t migrate, but you won’t be able to deploy new versions.

Existing Customer Alert!

If you have websites that you created through the Aerobatic Bitbucket add-on, read this important message first to understand how you are impacted.


Back in Spring of 2015, Aerobatic launched as one of the original partners in the Bitbucket add-on program — providing a seamless static website deployment experience directly from the Bitbucket interface. The add-on has been a terrific way to introduce ourselves to a great many developers who use Bitbucket as their source-control provider. However this has meant in order to take advantage of Aerobatic, one needed to be a user of Bitbucket. In order for us to serve the largest possible audience, we’ve determined that Aerobatic needs to be the best static hosting solution not only for Bitbucket, but GitHub, GitLab, on-premise VCS, or no source-control at all.

To achieve that objective, Aerobatic is transitioning from a Bitbucket add-on to a standalone interface — actually two interfaces: a command line tool (CLI) called “aero” and a web dashboard at It’s important to convey that this is just a change in how you interact with Aerobatic. The underlying hosting infrastructure that you’ve come to know and trust remains largely unchanged (with a few enhancements discussed below).

Bitbucket Pipelines

Because Aerobatic will no longer be tied into Bitbucket, we will no longer receive a webhook when you push to your repo, so it won’t be Aerobatic that runs your build process anymore. But fear not, with Bitbucket Pipelines you’ll still have the same seamless continuous deployment workflow that you’re accustomed to.

Bitbucket Pipelines is a new CI/CD service from Atlassian that will automatically trigger a configurable build/deploy workflow when you push to your repo. Pipelines can easily be configured to build sites with all the same tools supported by Aerobatic including Jekyll, Hugo, Webpack, Middleman and so on. Because it’s based on Docker, you have full control over what software is installed on the image — such as the specific version of Hugo. Your build config is specified in a file called bitbucket-pipelines.yml at the root of your repo.

If this all sounds a bit complicated, don’t worry, our migration process will provide you the exact YAML contents for your website to copy and paste. This is generally a one time “set it and forget it” step.

To get a sense for what the bitbucket-pipelines.yml file looks like, here’s a sample that builds a Jekyll site and deploys to Aerobatic:

image: jekyll/jekyll                       # Use the jekyll image from Dockerhub
      - step:
          - bundle install                 # Run bundler against the Gemfile
          - bundle exec jekyll build       # Build the site
          - npm install -g aerobatic-cli   # Install the aero CLI
          - aero deploy --directory _site  # Deploy the built site to Aerobatic

An environment variable named AEROBATIC_API_KEY must be defined with Pipelines. The migration instructions will provide your unique api key value.


With the Bitbucket add-on, there is a _aerobatic section to the package.json file where you specify a router array with any plugins such as basic-auth, redirects, custom-errors, etc. Now, we rely on a file called aerobatic.yml which has basically the same structure with a few naming tweaks. The only mandatory property in the file is id which is the unique ID of your website. The reasoning behind this change is that the YAML format is more conducive to comments than JSON and also more universal to all programming languages and development stacks.

Like with bitbucket-pipelines.yml, we’ll provide you the exact YAML to copy and paste into a new aerobatic.yml file at the root of your repo.

Here’s a side by side comparison of the legacy package.json structure and the new aerobatic.yml:

Legacy package.json

  "_aerobatic": {
    "router": [
        "module": "basic-auth",
        "options": {
          "username": "$BASIC_AUTH_USERNAME",
          "password": "$BASIC_AUTH_PASSWORD"
        "module": "custom-errors",
        "options": {
          "errors": {
            "404": "404.html"

New aerobatic.yml

id: <website_id>
  # Oh nice, comments!
  - name: basic-auth
      username: "$BASIC_AUTH_USERNAME"
      password: "$BASIC_AUTH_PASSWORD"

  - name: custom-errors
        404: 404.html # Custom 404 page

Web serving improvements

The underlying web serving infrastructure is largely unchanged, however there are a couple of key enhancements. First we’ve improved how asset path rewriting is done. Originally we rewrote your images, JavaScripts, css, etc. to an absolute URL, fingerprinted with your unique appId and versionId.

Legacy asset paths

<!-- original html  -->
<img src="/banner.jpg" />

<!-- deployed html  -->
<img src="[appId]/[versionId]/banner.jpg" />

This performance enhancement allows for aggressive cache headers since a new version will always result in a new URL. However the downside is that cached versions are always invalidated, even if the file didn’t change. Our new approach injects a hash representing the actual file contents into the asset path at deploy time. These assets are served with a 1 year expiration and the same cached files will continue to be served across multiple deployments unless the file has actually changed (resulting in a new MD5 hash).

New asset paths

<!-- original html  -->
<img src="/banner.jpg" />

<!-- deployed html  -->
<img src="/banner--md5--[asset-content-hash].jpg" />

Read more about Aerobatic asset acceleration.


The free plan provides all features and unlimited deployments, but does not include a custom domain and daily traffic is capped at 10GB / day.

Previously Aerobatic had multiple pricing tiers with a set number of websites and domains. Now we are simplifying our pricing model to a straightforward $15 a month per website (special pricing offer below for Bitbucket customers). This includes a custom domain, wildcard SSL certificate, and 500GB of data transfer per month.

How you are impacted

Current paying customers:

If you are already a paying Aerobatic customer, your existing websites will be grandfathered in to the new Pro Plan and your monthly bill will remain the same. However new websites you create will need their own individual subscriptions.

Non-paying customers WITH a custom domain:

When you migrate your site, you will automatically get a trial of the Pro Plan that lasts until March 1st. If you wish to continue hosting your site on Aerobatic after that, be sure to upgrade before the end of the trial. After March 1st, any websites on the Pro trial will be downgraded to the free plan and the custom domain will no longer resolve. See the special pricing offer below.

Non-paying customers WITHOUT a custom domain:

Your websites will continue to resolve at their * domain. However data transfer out will be capped at 10GB / day. If you are thinking of upgrading, be sure to do so by March 1st to take advantage of the special pricing offer below.

Special offer for Bitbucket customers

All existing Bitbucket customers are eligible for a special $10 / month price for websites upgraded to the Pro Plan before March 1st (rather than the standard $15). Just use the coupon code “BITBUCKET2017” when you checkout. This offer only lasts until March 1st, 2017.

Migrating your websites

You should already have an account let’s you login both with the CLI and the dashboard. Your login email is the same one that you login to Bitbucket with. You will need to establish a new password by visiting: Once you login, you’ll be presented with a list of all your Bitbucket websites with a button to migrate them over. You’ll be presented with customized instructions including the code to paste into the new bitbucket-pipelines.yml and aerobatic.yml files that need to be created.

Bitbucket add-on retirement

We will be retiring the Bitbucket add-on on March 1st, 2017. After that date any websites that have not been migrated will continue to load, but will no longer automatically deploy when pushing to the repo. Any non-migrated websites that are using a custom domain will be downgraded to the free plan.


In the coming months you’ll start to see new enhancements landing in the dashboard with the goal of making it useful not only for developers, but also non-developer stakeholders. Specifically we want to deliver tools that facillitate an agency model where ongoing hosting and operation of the site can be turned over to a client. One typical scenario is allowing the client to login and push a version from a staging URL like to production once they’re ready.

The new CLI let’s you tail your weblogs in near real-time and this same functionality will be coming soon to the dashboard.