Amoga Fair Use Policy

This Fair Use Policy (the “FUP”) sets out the technical limits relating to the use of the Amoga Service. The Usage of Amoga is monitored continuously. Only Licensees that consistently generate high loads over a sustained period will be affected by the FUP.

Amoga understands that Licensees may occasionally have remarkably high volumes of traffic outside of normal usage patterns. In those cases, where this traffic can be predicted, Amoga requests to be informed with as much notice as possible to ensure that service + delivery remains consistently high. 



  • A named user is considered a user. 
  • Each user maintains a singular active session, accessible across diverse devices or platforms (including mobile, web, and API). 
  • Users can log in, engage in activities, and partake in transactions. Amoga presents a range of user types, augmenting the Pay-per-use pricing model. This approach ensures cost-effectiveness, adapting charges based on usage intensity, with transactions serving as the defining metric. 



Amoga monitors and manages the platform’s compute capacity and usage for activities or transactions to prevent exceeding it and incurring additional charges or having our service restricted. The Fair Usage Policy (FUP) guidelines outline the principles that govern transactions on our Low-Code Platform, ensuring transparency and consistency in tracking usage. 

It is worth noting that the system provides a substantial compute capacity, which is equivalent to two times the combined capacity of users’ transactions per minute during working hours. This ensures that the platform maintains optimal performance and responsiveness, even during periods of heightened activity. 

  • Login/Logout Incidences: Each instance of user login and logout will be considered a transaction. 
  • Session Token Refresh: The refresh of session tokens will not be counted as transactions. 
  • Session Timeout: Session timeouts will not be counted as transactions. 
  • Object Actions (Crud, Assignment changes, Comment, Actions): Each action involving CRUD operations, assignment changes, comments, or other actions will be considered a separate transaction. 
  • Multiple Changes within a Single API Call: If multiple changes occur within a single API call, they will be combined and counted as one transaction. 
  • Workflow and Related Automation (User Initiated): Each object action initiated by the user, along with resulting communication events, will be treated as distinct transactions. 
  • Notification: The act of sending a notification will not be considered a transaction. 
  • Email, Mobile, or Other Communication: Custom automation flows that trigger email or notifications will be counted as transactions. 



  • The capacity limit for queries is the same as the capacity limit for transactions. 
  • These queries encompass direct object access, list views, search operations, filters, index pages, reports, and dashboards. 



Automation flow tasks are backend tasks that are initiated by automation flows. These tasks can be triggered by various events, such as internal events, external events, scheduled occurrences, or data imports. Each flow run can encompass multiple tasks that are organized in a logical sequence, in a trigger-condition-action setup. 

It is important to note that these flow runs are executed using a compute-optimized approach. This means they are designed to be efficient but may not be able to ensure real-time responsiveness. 

The capacity limit for flow tasks is the same as the capacity limit for transactions. Each flow task may take the form of: 

  • An API lookup. 
  • A scripted action. 
  • An executed action, such as sending emails, WhatsApp messages, notifications, or updating specific objects. 



The system provides the following storage limits for users: 

  • Standard users: 5 GB per user per month. 
  • Lite users: 1 GB per user per month. 
  • Portal users: 100 MB per user per month. 

Additional storage can be purchased at a rate of INR 10,000 per terabyte per month. This means that users can purchase additional storage in terabyte increments. 



This disclaimer outlines the terms of use for our services, products, and resources. By using Amoga’s offerings, you acknowledge acceptance of these terms. Please note that the information provided here is not intended as legal advice. For legal matters, please consult qualified professionals. Amoga aims to maintain accurate content, but changes may occur without notice.  

For usage inquiries or concerns, reach out to us at [email protected].