Infrastructure cost of Gitpod Dedicated

ℹ️ The infrastructure cost of Gitpod dedicated are payed for by the customer. This page helps set expectations for their magnitude. The cost will vary based on usage patterns. Your Gitpod Account Manager can work with you to obtain a customised estimate of the infrastructure costs below and discuss the license costs of Gitpod Dedicated itself.

Projected cost of a Gitpod Dedicated instance

The running infrastructure cost of a Gitpod Dedicated instances can be split into:

• Fixed cost for running the dashboard and supporting services
• Variable cost for running workspaces

The variable cost scale with the number of running workspaces and their size. This makes determining a precise estimate of the overall cost impossible as different usage patterns result in different cost. However, internal and customer data points can be used to extrapolate to following scenarios:

⚠️ The exact cost varies greatly depending on usage patterns, number of users, AWS region used, currency exchange, existing AWS discounts, AWS capacity reservations and more. The numbers presented in the table use AWS on-demand pricing, the most expensive way of consuming AWS compute. Your actual cost will depend on your agreement with AWS. For example, using one-year reserved instanced will create ~25% cost savings and using 3-year reserved instances will create ~50% cost savings on the numbers displayed.

Billable services used by the Gitpod Instance

Below is a list of all billable AWS services that are used with Gitpod Dedicated:

• EC2
• VPC
• Relational Database Service
• Elastic Container Service for Kubernetes
• CloudWatch
• CloudTrail
• Kinesis Firehose
• Elastic Load Balancing
• S3
• ElastiCache
• DynamoDB
• EC2 Container Registry (ECR)
• Secrets Manager
• Lambda
• Key Management Service
• Route 53
• SNS