What are overages in SaaS?
In SaaS, overages refer to the additional costs or fees that are incurred when a user exceeds the contracted usage limits or terms of their plan. Examples of overages include user overages, storage overages, API usage overages, feature overages and support overages.
Related Definitions
Spot Instances
What are spot instances?
As with any cloud service provider, AWS will have spare capacity available to support surges in customer demand. To offset the loss, AWS offers this excess EC2 capacity – in other words, spot instances – at a heavily discounted rate.
To benefit from these spot instances, users must bid on this unused EC2 capacity in their desired region. The capacity is then allocated to the highest bidder. While it can be a great way to reduce costs by as much as 90%, it is only suitable for workloads that can tolerate interruptions and don’t require continuous availability. This is because AWS will terminate the instance after a two-minute notification in the event that it needs to reclaim the resources, or because the spot price exceeds the bid price. In other words, when other customers are willing to pay more.
Zero-Based Budgeting
What is zero-based budgeting?
Zero-based budgeting is an accounting technique that requires all expenses to be justified and approved for each financial period, starting from zero rather than a pre-existing spend. This enables organizations to monitor and assess the necessity of each cost on a more granular level, lowering expenses and promoting fiscal responsibility.
Originally conceived in the 1970s, zero-based budgeting isn’t a new idea — but in the current economic climate, accounting for every dollar is helping businesses to regain control over their outgoings. The technique can be applied to a wide range of costs, from research and development to asset management.
Multi-Tenancy Environment
What is a multi-tenancy environment?
In cloud computing, a multi-tenancy environment refers to a situation where multiple users, also referred to as tenants, share the same physical infrastructure and resources. These resources, such as computing power, memory and storage are dynamically allocated based on the needs of each tenant. Each tenant’s data is, however, stored in separate databases to ensure both privacy and security.
Decentralized Procurement
What is decentralized procurement?
Decentralized purchasing in SaaS refers to the process of allowing individual departments or teams within an organization to make their own purchasing decisions for software applications. This is in contrast to a centralized purchasing model, where all purchasing decisions are approved by a single procurement team or a department such as finance.
While a decentralized purchasing model can provide teams with the flexibility to select and purchase the tools that best meet their needs, without having to wait for approvals or navigate bureaucratic purchasing processes, it can create challenges for the company. This can include reduced buying power, higher costs, lack of control over vendor relationships, and increased compliance and legal risks.
Data Storage
What is meant by data storage?
In the context of cloud computing, data storage refers to the process of storing and managing digital information in either a remote server or a data center provided by a cloud service provider such as Amazon Web Services (AWS) or Microsoft Azure.
The cloud ultimately provides a versatile platform for storing various types of data, whether that be documents, media files, application data, machine learning data or structured data.
Service Level Agreement (SLA)
What is a service level agreement in SaaS?
A Service Level Agreement (SLA) is a subset of a Master Service Agreement (MSA) and contains specific details about the level of service that will be provided by the SaaS vendor. This agreement will specifically define the performance metrics, responsibilities, and expectations of both parties.
An SLA is likely to include uptime guarantees, the level of support that will be provided to the customer, response times for any support requests, information on how these requests will be managed and escalated, information on how the vendor will protect the customer’s data and ensure the security of its systems and networks, as well as details on how it will compensate the customer if it fails to meet the agreed-upon service levels.