Plans & Pricing

Build Faster & Ship Safer for Teams of all sizes

Telepresence

Set up your ideal development environment for Kubernetes in seconds. Accelerate your inner development loop with hot reload using your existing IDE, and workflow.

PlanFreeTeamBusiness
Servicesup to 3up to 510 and up
Team Membersup to 5up to 1020 and up
SupportCommunityEmail onlyBusiness hours
Price

Enterprise Plan: Have sophisticated requirements that need strategic solutions?

Contact Sales

Enterprise Plan: Have sophisticated requirements that need strategic solutions?

Contact Sales

Edge Stack

Route and secure traffic to your cluster with a Kubernetes-native API Gateway built on the Envoy Proxy.

PlanFreeTeamBusiness
Clustersup to 2up to 510 and up
Requests per second*up to 5up to 1025 and up
SupportCommunityEmail onlyBusiness hours
Price

*Only applies to authenticated or rate-limited requests

Enterprise Plan: Have sophisticated requirements that need strategic solutions?

Contact Sales

Enterprise Plan: Have sophisticated requirements that need strategic solutions?

Contact Sales

*Only applies to authenticated or rate-limited requests

Frequently Asked Questions

What is an Active Service?

“Active Service” means an intercept, rollout, etc. has been performed on the service in the last 28 days.

What is a Team Member?

The number of users from your organization that have been added to your Ambassador account. Active users and viewers count against the Team Member quota for your organization.

What forms of payment are accepted?

Major credit cards are accepted. Charges will be billed in US Dollars.

How are the “Requests per second” defined and calculated?

Request per second (RPS) is the maximum usage in the cluster between Rate Limited Traffic and Authenticated Traffic. With multiple clusters, RPS is the sum of the maximum usage of each cluster.

RPS is calculated from a database snapshot sent by Edge Stack every 30 seconds.

What's the difference between Emissary-ingress and Ambassador Edge Stack?

Emissary-ingress is a CNCF Incubating project and provides the open-source core of Ambassador Edge Stack. Originally we called Emissary-ingress the "Ambassador API Gateway", but as the project evolved, we realized that the functionality we were building had extended far beyond an API Gateway. In particular, the Ambassador Edge Stack is intended to provide all the functionality you need at the edge -- hence, an "edge stack." This includes an API Gateway, ingress controller, load balancer, developer portal, and more.