Pricing is not set yet.

We would rather say so than publish a number we have not decided. Below: the two ways to take AddressIQ, and the plan structure that already exists in the software.

Two ways in, one product underneath.

BTP add-onStandaloneDatabaseSAP HANA CloudDatabasePostgreSQL + PostGISIdentityXSUAA / SAP IASIdentityAny OIDC identity providerAdmin UIFiori ElementsAdmin UIWeb adminOne codebasebusiness logic, routing, zones, billing
Both routes run the same code; only the database, identity and admin UI change. The HANA runtime is not yet proven in a live subaccount.
Existing SAP estate

BTP add-on

Deployed to your SAP BTP subaccount (HANA and XSUAA). The design is ready; the HANA runtime is compile-checked only and has not been proven in a live subaccount.

Suits SAP-first estates that want the Fiori experience.

Non-SAP estates

Standalone

The same product as a Docker or Kubernetes stack on your own infrastructure: PostgreSQL and any OIDC identity provider. No SAP BTP subscription is needed.

Suits Salesforce, ServiceNow, Oracle or Maximo-centred estates.

How either route is charged (licence, subscription, usage, or a mix) has not been decided. No price has been published for either.

The plan structure in the software.

Every tenant is on a plan with a monthly call quota and limits. These are the defaults in the code today. They show how plans are shaped, not what they cost, and an administrator can override them per tenant.

  • Sandbox

    A free tier to try the API.

    Calls a month
    2,500
    Requests a minute
    60
    Rows per bulk job
    1,000

  • Standard

    For a team running one integration.

    Calls a month
    100,000
    Requests a minute
    600
    Rows per bulk job
    50,000

  • Enterprise

    For several systems and heavy volume.

    Calls a month
    5,000,000
    Requests a minute
    3,000
    Rows per bulk job
    50,000

Bulk job rows count against the quota. Over quota, the API answers 429 with a reset time. Plans are assigned by an administrator: self-serve sign-up and card billing are not built, so you cannot buy a plan on this site. Quota is tested on a test database only.

Usage is recorded, not estimated.

Geocoding providers charge in very different ways, which is why routing across them matters. AddressIQ writes each call, each fallback attempt and the provider that answered to a usage ledger per tenant, so any bill can be reconciled to evidence.

Provider typeTypical sourceWhat the ledger shows
MeteredCommercial global geocodersCalls per provider, so per-call cost is visible.
Subscription or licensedAuthoritative national or state address sourcesCalls per provider, so a flat fee can be spread over real volume.
Open dataCommunity-maintained open datasetsCalls per provider, with no provider fee.

No live provider contract is signed, and provider costs and licence terms are still being confirmed. Whether provider cost is passed through, and on what terms, is part of the pricing decision. Today all data is synthetic.

Talk to us about your estate.

The briefing sizes your systems, volumes and provider mix. Bring last month’s geocoding invoices.

addressiq@vrdigital.solutions

See also the limits and quotas in the developer docs and what is not yet done.