> For the complete documentation index, see [llms.txt](https://upsolver.gitbook.io/content/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://upsolver.gitbook.io/content/support-1/faqs/cost-estimator.md). # Cost Estimator Upsolver provides a transparent and simple-to-understand value-based pricing model. To estimate the costs you simply need to understand the amount of data you will ingest. Our pricing comprises a **software edition fee** and a **data usage fee** based on the volume of data ingested. You will also need to account for **infrastructure fees**. ## Software Edition Fees Upsolver offers three software editions: 1. Start-up 2. Standard 3. Enterprise The **Standard Edition** has a software fee of **$4,999** monthly, which includes 24x7 advanced support and up to five hours of dedicated assistance from solutions architects. {% hint style="success" %} To learn more about the supported features in each software edition and to contact us for Enterprise Edition fees, please visit the [Upsolver Pricing](https://www.upsolver.com/pricing) page on our website. {% endhint %} *** ## Infrastructure Fees When you [deploy Upsolver in your AWS VPC](/content/how-to-guides-1/setup/deploy-upsolver-on-aws.md), Upsolver will automatically configure the required infrastructure. This infrastructure gives you full control over your data and ensures that none of it leaves your AWS account. You can learn more about these components in the [Deployment Guide](/content/how-to-guides-1/setup/deploy-upsolver-on-aws/deployment-guide.md). Upsolver does not charge you for infrastructure resources, they are billed directly by AWS. However, Upsolver will attempt to optimize how it uses these resources to reduce operational costs, like leveraging EC2 Spot Instances when applicable. ### Cost estimates for the AWS resources used to run Upsolver {% hint style="info" %} Prices are based on the US East region. AWS users with custom pricing/discounts will use their rates. Last updated February 2023. {% endhint %} **Predictable infrastructure costs:** * One Amazon Kinesis shard, in a provisioned mode, for about $15 a month regardless of deployment size. Kinesis is used for synchronization within Upsolver. [See the AWS Kinesis pricing page](https://aws.amazon.com/kinesis/data-streams/pricing/). * One r6i.xlarge for the API server, using spot instances, for about $60, depending on spot availability. The API server runs the user interface and handles all CRUD operations (e.g. create a job) and settings management via the user interface or CLI. [See the AWS EC2 Spot Instances pricing page.](https://aws.amazon.com/ec2/spot/pricing/) **Variable costs:** * In order to process up to 10TB of data in a month, you will likely need one server, of size 2xlarge (e.g. r6i.2xlarge). Current spot pricing is about $75 per month. By default, Upsolver uses Spot instances, which results in a 60%-80% reduction in compute costs over on-demand instances. The cluster auto-scaling feature allows you to only pay for what you use. [See the AWS EC2 Spot Instances pricing page.](https://aws.amazon.com/ec2/spot/pricing/) * $23 a month per 1TB stored on the data lake. The size of your data lake will depend on many factors, the primary of which is how long data is retained. You can also turn on retention for tables to delete data you no longer wish to pay for. [See the AWS S3 pricing page](https://aws.amazon.com/s3/pricing/). * Upsolver manages table metadata in the AWS Glue Data Catalog which bills based on the amount of metadata stored and the number of API requests. This often represents a small part of the total cost associated with data ingestion and transformation. [See the AWS Glue Pricing page.](https://aws.amazon.com/glue/pricing/) ## Data Usage Fees For the first **500 terabytes of data** ingested, the usage fee is **$225 per terabyte** and drops considerably per terabyte for additional data ingested. ### Data cost estimates per use case The following use cases provide an estimate of costs based on the volume of data ingested. **Ingesting 3TB of data from Amazon S3 over a month** * Upsolver usage fee: 3 \* $225 = $675 Upsolver usage fee. * Data lake: 3 \* $23 = $69 for Amazon S3 storage of newly ingested data and some data retained from previous months. * Computing: $75 for one 2xlarge server. * Infrastructure (Amazon Kinesis and API server): $75. A total estimate of **$894** = $675 paid to Upsolver and $219 paid to AWS. *** **Ingesting 10TB of data from Amazon Kinesis over a month** * Upsolver usage fee: 10 \* $225 = $2,250. * Data lake: 10 \* $23 = $230 for Amazon S3 storage of newly ingested data and some data retained from previous months. * Computing: $75 for one 2xlarge server. * Infrastructure (Amazon Kinesis usage by Upsolver and API server): $75. A total estimate of **$2,880** = $2,500 paid to Upsolver and $380 paid to AWS. *** **Ingesting 100TB of data from Amazon S3 over a month** * Upsolver usage fee: 100 \* $225 = $25,000. * Data lake: 100 \* $23 = $2,300 for Amazon S3 storage of newly ingested data and some data retained from previous months. * Computing: 10 \* $75 = $750 for 2xlarge servers. Each serves 10TB of data. * Infrastructure (Amazon Kinesis and API server): $75. A total estimate of **$28,125** = $25,000 paid to Upsolver and $3,125 paid to AWS. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://upsolver.gitbook.io/content/support-1/faqs/cost-estimator.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.