Billable services

Billable services are identified as content, data storage, location services, and pipelines. Additional costs may include transferring and computing data. As a general rule, the more data you send, receive, store, and process, the more you are charged. For current base plan pricing, see HERE Base Plan Pricing. Rates may vary depending on your licensing agreement.

The default workspace pricing model has a tiered structure for built-in volume discounts. The model also uses a partner program, which provides built-in discount rates and free credit for partners. Typically, greater annual savings are seen at higher partner program levels.

You can view your billing usage on the Usage dashboard, under the Usage report tab.

Calculating total cost

You can calculate your current costs at any time, using the Usage API or by accessing a Usage report.

The following figure provides a total cost calculation sample, using sample data for various partner program levels.

Billable services are separated into the following categories:

Content

Content is varied map content such as points, attributes, places, boundaries, and others.

Data storage

The following are available types of billable data storage.

Blob storage

Blob storage is disk storage used to store blob data which is generated by versioned, index, object store layers, or stream layers if message payloads exceed one Megabyte (MB) per month.

• Stream message payloads greater than one MB and stored in blob storage with a TTL of less than one day, are billed for one day. Expired data in blob storage is cleared once per day.
• Blob storage cost is determined by recording the total size of all blobs stored once per day.
• Blob storage is reported per unit in Gigabytes (GB) per hour, and billed per month.
• Monthly prices signify that usage is greater than 720 hours.
• Calculation construct:
  • Sum of all blob data bytes.
• Cost is prorated for a specific billing period based on usage. For example, if a versioned layer is deleted halfway through the month, the monthly cost for blob storage associated with that layer is prorated at 50%.
• APIs which can incur blob storage costs include:
  • Ingest
  • Publish
  • Blob

The following is an example calculation, converting blob data stored for five days into GB-months, then into USD.

Explanation of blob storage use case details:

• Day 1: Customer writes 2.5 TB of data to blob storage.
• Day 3: Customer writes an additional 2 TB of data to blob storage.
• Day 4: Customer deletes 2.5 TB of data.
• Day 5: Customer deletes remaining 2 TB of data before the start of day 6.

Metadata storage

Metadata storage is database storage used for metadata such as layer titles, coverage, tags, descriptions, index layer key/value pairs such as HERE Tile/Time, and object stored layer object metadata. This supports fast search and discovery of your data.

• Usage is measured as the maximum number of bytes of stored records per hour, and is calculated as the sum of data stored in indexes and persistent storage for metadata.
• Metadata is accessed by the Metadata and Index APIs.
• Metadata storage is reported per unit in GB per hour, and is billed per month.
  • Cost is incurred for an hour, if the service is used for any part of that hour.
• Monthly prices signify that usage is greater than 720 hours.
• Calculation construct:
  • Sum of all stored metadata bytes.
• Cost are prorated in a specific billing period based on usage. For example, if you delete your catalog halfway through the month, the monthly cost of the metadata for that catalog is prorated at 50%.
• APIs which can incur metadata storage costs include:
  • Config
  • Metadata
  • Index

Volatile storage

Volatile storage is RAM storage allocated for reading and writing volatile layers.

Volatile storage cost is determined by the total size of the configured storage capacity, including redundancy. Volatile layers configured with "multi-instance" redundancy, increase the storage capacity and cost by a factor of three (initial copy + two replicas).

Volatile layers configured with "single-instance" redundancy do not increase storage capacity because data is not redundantly stored. Configured capacity and usable capacity are the same for "single-instance" layers.

• The configured capacity is three times the usable capacity, as data is redundantly stored three times to ensure data protection.
• Volatile storage is reported per unit in GB per hour and is billed per month.
  • Cost is incurred for an hour, if the service is used for any part of that hour.
• Monthly prices signify that usage is greater than 720 hours.
• Calculation construct:
  • (Configured storage capacity in GB) * (Configured redundancy factor being one for "single-instance" or three for "multi-instance") = X volatile storage in GB.
• Cost is prorated in a specific billing period based on usage. For example, if a volatile layer is deleted halfway through the month, the monthly cost of the layer is prorated at 50%.
• APIs which can incur volatile storage costs include:
  • Config (based on the allocation of data storage capacity and redundancy).

Stream storage

Stream storage is the allocated storage queue capacity for streaming data (consecutive messages read and written if individual message payloads are less than one MB).

• Cost is calculated by the “KB/s In” throughput, which is configured when you create a stream layer.
• Usage is measured as the maximum of your configured throughput.
• Stream storage is reported per unit in GB per second per hour and billed per month.
  • Cost is incurred for an hour, if the service is used for any part of that hour.
• Monthly prices signify that usage is greater than 720 hours.
• Calculation construct:
  • (KB/s In) / (1024) KB to MB / (1024) MB to GB = X stream GB per second.
• Cost is prorated in a specific billing period based on usage. For example, if a stream layer is deleted halfway through the month, the monthly cost of the stream layer is prorated at 50%.
• APIs which can incur stream storage costs include:
  • Config (based on “KB/s In”).

Stream TTL storage

Stream TTL storage is allocated disk storage which is calculated by the combination of the TTL data retention configuration (a minimum of 10 minutes up to a maximum of three days), and the “KB/s In” throughput (volume) configuration that is set when you create a stream layer.

• Usage is measured as the maximum of your combined throughput and TTL configuration.
• Stream TTL storage is reported per unit in GB per hour and billed per month.
  • Cost is incurred for an hour, if the service is used for any part of that hour.
• Monthly prices signify that usage is greater than 720 hours.
• Calculation construct:
  • (KB/s In) * (Configured TTL in minutes) * 60 seconds per minute / 1024 (KB to MB) / 1024 (MB to GB) = X stream TTL GB.
• Costs are prorated in a given billing period based on usage. For example, if a stream layer with TTL is deleted halfway through the month, the monthly cost of the stream layer at that TTL is prorated at 50%.
• APIs which can incur stream TTL storage costs per stream TTL configurations include:
  • Config (based on TTL and throughput configured per stream layer).

Interactive map storage

Interactive Map storage is disk storage used to store semi-structured data, such as GeoJSON data stored in interactive map layers, and data indexed by default when using this storage type.

• Interactive Map storage cost is determined by the total size of all records stored per hour.
• Interactive Map storage is reported per unit in GB per hour and billed per month.
  • Cost is incurred for an hour, if the service is used for any part of that hour.
• Monthly prices signify that usage is greater than 720 hours.
• Calculation construct:
  • Sum of all bytes stored.
• Cost is prorated in a specific billing period based on usage. For example, if you delete your catalog halfway through the month, the monthly cost of the interactive map storage for that catalog is prorated at 50%.
• APIs which can incur interactive map storage costs include:
  • Interactive

Data IO

Data IO refers to the data transfer incurred when storing and accessing data, both from within and from outside of the workspace. Data IO is also incurred when entering data, publishing data, and transferring data.

• Reported per unit in gigabytes per hour and billed per month.
• Monthly prices signify that usage is greater than 720 hours.
• Calculation construct:
  • Write volume in GB + Read volume in GB = X Data IO GB.
• APIs which can incur Data IO costs include:
  • Config
  • Ingest
  • Stream (when using HTTP protocol)
  • Publish
  • Metadata
  • Blob
  • Volatile Blob
  • Index
  • Query
  • Notifications
  • API Lookup

Interactive map IO

Interactive map IO refers to the data transfer incurred when storing data in and retrieving data from an interactive map layer, both from within and from outside of the Workspace. Transfers related to the interactive map layer data incur only Interactive map IO charges; no Data IO charges are incurred.

• Reported per unit in gigabytes per hour and billed per month.
• Monthly prices signify that usage is greater than 720 hours.
• Calculation construct:
  • Write volume in GB + Read volume in GB = X Interactive Map IO GB.
• APIs which can incur Data IO costs include:
  • Interactive

Location Services

Location services such as routing, traffic, geocoding and many others are offered.

Pipelines

Compute core

Compute core refers to CPU core hours used by pipelines and notebooks when processing data.

• Reported and billed per unit in core hours per hour (at a resolution of seconds).
• One compute unit = one core and seven GB RAM.
• Calculation construct:
  • ((Worker Size – in compute Unit count) * (Worker Count) + (Master Size – in compute Unit count)) * # of hours run = pipeline core hours.
• APIs which incur compute core costs include:
  • Pipelines

Compute RAM

Compute RAM indicates RAM hours used by pipelines and notebooks when processing data.

• Reported and billed per unit in GB-hours per hour (at a resolution of seconds).
• One compute unit = one core and seven GB RAM.
• Calculation construct:
  • ((Worker Size – in compute unit count) * (Worker Count) + (Master Size – in compute Unit count)) * seven Cluster Cores to Cluster RAM * # of hours run = Pipeline RAM Hours.
• APIs which incur compute RAM costs include:
  • Pipelines

Log search IO

Log search IO logs show the data transfer incurred when pipeline-generated log information is written and indexed for debugging purposes.

• Reported per unit in GB per hour and billed per month.
• Monthly prices signify that usage is greater than 720 hours.
• Calculation construct:
  • Total number of bytes written to the index.
• Costs are not incurred using API requests, rather they are incurred through optional developer code within a pipeline JAR file, which writes to “std-out".

Pipeline IO

Pipeline IO indicates the data transfer incurred when a pipeline reads or writes data to or from the public internet. Pipeline IO also occurs when pipelines make requests over the internet. For example, to confirm the latest XML parsing protocols.

• Reported per unit in GB per hour and billed per month.
• Monthly prices signify that usage is greater than 720 hours.
• Measured at the TCP level.
• Calculation construct:
  • Total number of bytes read from or written to pipelines over the internet.
• Costs are not incurred using API requests but through optional developer code within a pipeline JAR file, which connects to the public internet for read and write.