Pay as you grow

Start for free, scale up any time and only paying for what you use

  • Free

    Test for free without commitments

    • All basic features +
    • 1 Container Limit (?)
    • Idles due to inactivity (?)
  • Basic

    Perfect for small websites

    • 2 Container Limit (?)
    • Active Health Monitor
    • Application Logs
    • Recreate Deployments (?)
  • Standard

    Performance for growing applications

    • All basic features +
    • Increased Quota (?)
    • Container Scalability (?)
    • Faster Builds (?)
    • Rolling Deployments (?)

Scaling to production

You are able to scale your containers both horizontally and vertically depending on your application requirements.

Flexible usaged based billing to the second so you will only pay for what you use.

    $15.00/512MiB RAM per month
  • Persistent Storage
    $0.35/GiB per month
$10.00 /month

Frequently Asked Questions

  • What is a container?

    A container is an isolated set of compute resources and pre-packaged software runtimes which are used to run your application. When you deploy your website, one container will usually run just one service such as PHP web server. Another container will be used to provide the MySQL service.

  • What are is difference between two paid plans?

    The basic plan is a fixed prepaid $10.00/month plan, ideal for running a single website or application, you are limited to a set resource pool.

    The standard plan gives you the flexibility of per second postpaid billing, this means your monthly rate is variable depending on the resources you provision. You are billed at the end of each billing period.

  • What form of payments do you accept?

    We accept payments through Visa, MasterCard and PayPal. Each month you will receive an invoice for your usage; your credit card or PayPal account that we have on file will be billed in the next 7 days.

    All charges are in Australian Dollars (AUD) inclusive of GST.

  • How is my monthly cost calculated (Standard Plan)?

    Prices listed above are estimated on the approximation of 720 hours per month (30 days), so actual cost will vary from month to month.

    All compute resources are billed by MiB to the second. For example, if you are running a 512MiB container for a 24 hours, you will be billed $0.0390625 at the end of your billing period.

    512 MiB is approximately 537 MB

  • Am I charged if my container is in a powered-off state (Standard Plan)?

    When you scale your application to use 0 containers, you are not billed for any compute resource usage.

    You will still be billed for any persistent storage allocated to these containers. Persistent storage is billed to the hour.

  • How does automatic scaling work?

    After you enable automatic scaling, the platform will start to monitor your application's resource usage. Your application will then scale out horizontally as required, adding or removing containers depending on application load.

    Automatic scaling can be configured with CPU scaling threshold and a minimum and maximum container limit.

  • What are the runtimes supported? Can I run any Docker container?

    We currently maintain images for PHP, Ruby,NodeJS, Python, .NET, Wildfly (Java), Go and Perl. These runtimes can be extended with extensions including MySQL, MongoDB, PostgreSQL, Memcached or Redis.

    Theoretically you can run any Docker image, however security policies do now allow containers to run as root, which may prevent some images from running.

    See the image builder guideline to understand how you could adjust your images to run without root.

  • What is the difference between the Recreate and Rolling deployment strategy?

    Deployment strategies are triggered from events such as updates to your source repository or when a new security patches is released.

    The recreate deployment strategy will recreate your containers to deploy the new code change, temporarily taking your application offline during the process. The rolling deployment strategy does this process in parallel ensuring there is no disruption to your running application.

    Free and basic tier users need to use the recreate strategy as the parallel deployment will exceed their resource quota.

Start your project today

Sign up for free