Compare evaluation and paid organizations in Apigee

This topic compares the lifespan, infrastructure allowances, and scaling capabilities of Apigee's free trial (evaluation) and paid organization offerings.

You can evaluate Apigee at no cost for 60 days with a trial (evaluation) Apigee organization. Evaluation organizations are an excellent way to test the functionality and feature offerings of Apigee, subject to the following limitations:

  • Free trial (evaluation) organizations are limited to a 60-day lifespan, after which the organization is deleted.
  • Evaluation organizations are subject to Google's Pre-GA Offerings terms and should not be used for production workloads or to store sensitive data.
  • Apigee's evaluation organizations are not regularly updated with the latest Apigee features and security patches.
  • Evaluation organizations can't be converted to paid organizations.

The following table shows the key differences between Subscription, Pay-as-you-go, and evaluation organizations:

Function
Org Type
Description
Paid/Subscription
Paid/Pay-as-you-go
Evaluation
Lifespan
Based on contract
Until decommissioning of Pay-as-you-go org
60 days
For an eval org, you will get a notification after 30 days that its lifespan is limited. After 60 days, Google deletes the eval org. You cannot extend its lifespan. For more information, see Apigee Pricing or contact Apigee Sales .
Requires VPC peering?
No
No
No
You can choose to provision with or without VPC peering. See Apigee networking options .
Required network size with the VPC peering option
/22 + /28
/22 + /28
/22
For more information, see Peering ranges .
Required network size with the non-VPC peering option
N/A
N/A
N/A
For more information, see Apigee networking options .
External or private/local access
External or private/local access
External or private/local access
By default, API proxies can be accessed internally only. You can, however, configure your load balancer to accept external requests for either an eval or paid account.
Supported instances
Based on contract
Billed by usage
1
The number of runtime instances.
Environments
Based on contract
Billed by usage
2

The number of runtime environments. Does not affect the number of environment groups.

Apigee creates two environments during provisioning, so an eval org must delete one to create a new one.

Runtime fault tolerance
Regional
Regional
Regional

Runtimes for production and evaluation orgs use regional clustering, which means that if a zone goes down, Apigee can re-route requests to the runtimes in other zones within the region.

For more information about regions and zones, see Regions and zones .

Analytics data
Regional
Regional
Regional

Analytics data is regional for all.

Customer managed encryption keys for runtime data
Yes
Yes
No
Scalability and sizing
Evaluation orgs have limited/restricted infrastructure. They are not suitable for performance/load testing.
JavaScript execution time
Configurable
Limited to 200 ms.
For more information, see the JavaScript policy .
Integrations and Connectors
No
No
Based on Subscription contract
  • Maximum execution of 500 tasks per day across all the integrations
  • Maximum of 2 integrations can run in parallel
  • You can only use the connectors supported in the Apigee eval org's region
  • Maximum of 4 connections can be created
Organization policy constraints
Yes
Yes
No
If you have CMEK organization policy constraints on your Google Cloud project, Apigee will enforce compliance with those constraints, guide you in choosing a valid configuration, and prevent you from using Apigee features that are not CMEK compliant.
Create a Mobile Website
View Site in Mobile | Classic
Share by: