Operating Costs

Estimated Utilization and Costs for Running GRAX Yourself

Since GRAX can operate in a large number of unique infrastructures and the application uses subsystems that can undergo any number of unique configurations, exact analysis of costs is not possible. For our purposes, we are going to calculate the expected cost for a standard AWS GRAX installation. The data provided here helps demonstrate how you may perform the same analysis in your specific architecture.

This is not the cost of contracting for a GRAX license - this is your internal cost of running GRAX.

Amazon Estimate Calculator

A pre-configured estimate of the high-level AWS resources necessary for GRAX is available here.

Static Costs

Costs that can be determined prior to usage, like the hourly cost of an EC2 instance given a 24x7x52 uptime, are considered static. These sections of the estimate are not expected to change, regardless of GRAX features used or data processed. All prices set by AWS are subject to change by AWS at any time, see their pricing documentation for more information. GRAX is not responsible for changes to AWS pricing.

Variable Costs

Many networking and storage services in the public cloud bill entirely based on utilization. When it comes to GRAX's utilization of RDS, S3, and NAT Gateway services, there is no exception. The estimate above includes best-attempt estimations of utilization when under a typical application load. GRAX provides no guarantees as to the accuracy, in either direction, of these estimates.

There are many factors that can affect total realized costs:

  • Utilization of Specific GRAX Features
  • Total Salesforce Org Size
  • Turnover Rate of Salesforce Records (created + changed per hour)
  • Number of Files in Salesforce (each file gets downloaded and stored)
  • Disk and Memory Cache Sizes (/tmp + memory sizes)
  • Cross-Provider Storage Connections (AWS to Azure, etc. traffic bills extra)
  • Public vs. Private Traffic Routing (exiting VPC may incur NAT costs)

Avoidable Costs

As a product of the cost-affecting parameters above, here are the biggest considerations for avoiding high costs with GRAX infrastructure:

Never Route Storage Publicly

Never route your storage traffic external to the VPC or cloud provider. Traffic leaving the VPC will cross the NAT Gateway and incur much higher costs; GRAX reads many Terabytes of data as it compacts and processes your datasets so this difference adds up. This includes traffic from an AWS instance to Azure storage, or any other similar mismatch in infrastructure providers.

Always Provide Cache Space

Low cache size, in both memory and disk, can lead to extremely frequent read operations from storage and thus drive up overall data transfer. In infrastructures where this incurs cost, this can become very expensive. See our technical specifications for GRAX hardware to ensure you're operating within safe limits.