Usage Limitations

This page describes the usage-based limitations applicable to the Port Platform and the methodology used to measure usage and bill for over-usage.

By using the Port Platform, Customer agrees to the usage measurement and billing practices described below.

1. Definitions

1.1. Seat

“Seat” means a unique end user or service account that, at any time during the applicable subscription term, has logged in or otherwise accessed the Port Platform.

For purposes of the foregoing, a “login” includes any authenticated interactive or programmatic activity initiated by a user or service account across any Port-supported interface (including, without limitation, the web application, API, Slack application, IDE extension, or any future Port-provided interface), such as viewing data, executing actions or workflows, or performing similar authenticated operations.

A Seat associated with a user (i.e. not a service account) may be reassigned only after four (4) months have elapsed since the last recorded activity of the applicable user. Users that are deleted or disabled but had activity within the prior four (4) months will continue to be counted as Seats.

Service accounts count as Seats without any reassignment grace period.

1.2. Entities

An “Entity” refers to any uniquely identifiable, structured item in Port’s software catalog. Each Entity is counted once based on its unique identity in the catalog, regardless of how frequently it is updated, synchronized, or modified. Entities that are automatically created or maintained by Port solely for internal system functionality (“System Entities”) are excluded from the Entity count. System Entities include Port-managed Entities that are generated or maintained by the Platform itself, and do not include customer-defined Entities that reference or interact with those features.

1.3. Action and Automation Runs

A “Run” refers to a single execution of an action or automation. All Runs are counted regardless of where they are executed from, except for manual executions initiated by a user directly through the Port user interface (UI).

2. Usage Measurement

2.1. General Principles

Port measures Customer’s usage of the Port Platform on a monthly basis. Each calendar month constitutes a “Measurement Period” for purposes of usage calculation and billing. Usage is determined based on Customer’s actual activity and consumption of the applicable usage metrics during the Measurement Period.

During each Measurement Period, Customer’s usage is measured based on: (i) the number of Seats, (ii) the number of Entities, and (iii) the number of Runs, as calculated in accordance with the monthly measurement method set forth in Section 2.2 and the quantities licensed under the applicable Order Form.

2.2. Monthly Measurement Method

Port measures usage during each Measurement Period as follows:

• Seats usage: measured based on the maximum number of Seats recorded at any point during the Measurement Period.
• Entities usage: measured based on the maximum number of Entities recorded at any point during the Measurement Period.
• Runs usage: measured based on the aggregated number of Runs executed during the Measurement Period.

3. Usage Visibility

Customer may review its current usage for applicable metrics via the usage dashboard, available at:
If Customer is located in the US, LATAM or Canda - https://app.us.port.io/settings/usage-dashboard

If Customer is located in other locations - https://app.port.io/settings/usage-dashboard

The usage dashboard is provided to help Customer monitor its usage and entitlements. Usage data in the dashboard is for informational purposes only and may be subject to processing delays or temporary differences from Port’s internal usage records.

Port’s internal usage records constitute the authoritative source for usage measurement and billing purposes. In the event of any discrepancy between (i) usage data displayed in the dashboard or any other usage data or report, and (ii) Port’s internal usage records, Port’s internal usage records shall prevail for billing purposes.

4. Over-Usage and Billing

4.1. Over-Usage Determination

If Customer’s usage of Seats, Entities, or Runs, exceeds the applicable quantities licensed in the applicable Order Form (the “Licensed Limits”) during a Measurement Period, such excess usage (“Overage”) is subject to additional charges.

Overage is calculated, for Seats, Entities, and Runs, based on the difference between (i) the usage measured in accordance with Section 2.2, and (ii) the applicable Licensed Limit set forth in the Order Form.

Customer’s usage for billing purposes shall not be measured at a level lower than the applicable Licensed Limit set forth in the Order Form.

4.2. True-Ups and Invoicing

Overage is calculated on a monthly basis in accordance with Section 2 and invoiced on a quarterly true-up basis, aligned with calendar quarters ending on March 31, June 30, September 30, and December 31.

For each calendar quarter, Port will review Customer’s monthly Overage during such quarter and invoice Customer for all applicable Overage amounts in accordance with the pricing set forth in the applicable Order Form.

Usage entitlements are measured on a monthly basis and do not roll over. Reductions in usage below the Licensed Limits in a subsequent month do not offset or reduce Overage incurred in a prior month.

Customer agrees to pay all applicable Overage charges in accordance with the applicable Order Form and the payment terms governing the provision of the Services.

Customer must notify Port in writing of any dispute regarding usage data or Overage charges within thirty (30) days of the applicable invoice date. If no dispute is raised within this period, the invoice will be deemed accepted.

5. Changes to Usage Limits

Customer may increase licensed usage limits at any time by executing an updated Order Form.

Port may update usage metrics, definitions, or measurement methodologies from time to time to reflect product changes, provided that such updates do not materially reduce Customer’s licensed usage entitlements during the then-current subscription term.