PaaS Pricing Model

Our Platform as a Service that lets you Pay for Usage Not Limits!

  • PaaS Pricing Model
  • WebWolf-PaaS-Pay-for-Usage

Container resources are measured in Cloudlets. Each cloudlet consists of 128 MB of RAM and 400 MHz XEON CPU power simultaneously.  By providing you with smaller increments you are able to more accurately measure the resources you application is going to use. It makes no sense to upgrade your server or hosting plan with an additional 2GB of RAM and CPU and continue to pay monthly for all those resources when all that is needed is an additional 756 MB or 1 GB for the duration of a heavy traffic spike which could only last a few hours, perhaps several. It is very unlikely that your application will continue to use the additional resources 24/7.

Cloudlets come in two flavors:

  • Reserved Cloudlets: All applications need a certain amount of resources just to be loaded and ready to run, you’ll always consume a particular number of cloudlets regardless the load level. Therefore, you can allocate them beforehand with Reserved Cloudlets and benefit by receiving automatic discounts, the more cloudlets your reserve, the higher the discount level you receive.
  • Dynamic Cloudlets: are set and allocated for your application to use when they are required in a particular moment in time and will be added or removed automatically according to the amount of resources your application(s) needs – i.e. they’re assigned when load goes up, and removed again as soon as it drops down. As a result, you pay based on your actual resource usage. The automatic scaling of cloudlets can easily be set within your dashboard and you can opt to receive email notifications when your application is reaching the limits.
Automatic Vertical Scaling

Automatic Horizontal and Vertical Scaling

Automatic Horizontal Scaling refers to the “Nodes” or application servers such as Apache, Nginx, Tomcat, mySQL, MariaDB, Percona databases, Memcached, Redis or even Storage that you allocate to your application so that in the event that you application needs the additional resources, they available, hence the terms High Availability and Clustering. You are then effectively creating a cluster of servers.

The image below is an example of an Apache application server which has been set to scale to 4. Replication of data and settings is automatic.  Each server is set with a certain amount of reserved cloudlets and dynamic. So as you will see in the example, we have set each application server to have 1 reserved cloudlet and the scaling limit to 8 cloudlets and we have allocated 5GB of disk space for each application server. Note that as soon as your add an additional application server, the platform will automatically assign a load balancer.

Automatic Horizontal Scaling

Automatic Vertical Scaling refers to cloudlets – the CPU and RAM that you allocate and set for your application. These will only be used IF your application needs additional resources and they will only be used for the duration they needed. You can scale from 1 to 256 cloudlets. Setting up automatic vertical scaling is also used to control your monthly expenditure. Your application will never use more than the limit you have specified. If you prefer to have a fixed monthly spend instead of a variable amount each month, then you can disable the automatic scaling by sliding the slider and setting both the Reserved and Dynamic cloudlets to the same number of cloudlets. Bear in mind that setting Scaling Limit too low for highly-loaded applications may cause their instability.

Control Monthly Expenditure with PaaS

Scaling ranges are configured individually for each server instance, so you can specify different limits for each container depending on your needs and preferences.

Automatic Scaling of Resources

Getting Started with WebWolf PaaS

If what you are reading about our Platform has peaked your interest, you may be wondering what and how to go about migrating to our platform and if you and your online business will benefit, financially and performance wise. The chances are you either still on a shared hosting account or you may have a Cloud VPS. You might even have explored the options available at Amazon Web Services and Google Cloud but got lost in the maze of options, settings and configurations. The most popular hosting control panel is currently WHM / cPanel and both of these will give you enough information so that you can start off with our platform. The CPU usage and load, disk space usage and more, will all give you a pretty good idea of what your application may need.

When getting started with our platform, we recommend that you start off small with fewer cloudlets – yes we know – it is great to load the system with resources- but ask yourself, do you really, really need it? Then monitor your application usage closely. Our platform makes it extremely easy for you to keep a watchful eye over your application(s). After a couple of months you’ll know how many cloudlets to allocate and how to setup automatic horizontal and/or vertical scaling.

Platform Statistics

For each Node there is a Statistics button and by clicking on that, you can view exactly what each node is using, per 1, 6 and 12 hours, per day, per week, per month and even per minute. You can also see at what time of the day your web site is the busiest and the amount of resources that each Node is consuming.

Resource Usage

Not only can you monitor the resources that your application is using, but you can you can also monitor the cost on a daily basis, and see exactly what each instance has cost you. By clicking on the “Balance” link at the top of your dashboard, a drop down menu will display various links all related to the financial side of things. Click on the “Billing History” and you will be presented with a screen which displays your environment and instances and the cost of each for the day. You can select to see the costs between dates, simply select the dates and refresh.

The image below shows you the screen which reflects the daily costs for the instances you have created. Learn more about our pricing and payment options.

Balance and Billing History
Billing History

It’s best to start off with a lower amount of cloudlets and monitor your application for at least 3 months. That should give you a good idea of the resources you can expect your application to use.  If you have been making use of Google Analytics, there is a myriad of information which is at your disposal in your Google Analytics account that can help you decide on the amount of resources to allocate to your application. The sooner you get started, the sooner you can start saving money on IT, and hosting fees. Please contact us if you need assistance, we are here to help and advise you.

Get Started Today with WebWolf PaaS