Field service
Send the right crew to the right door. Valid addresses and zones on work orders in ServiceNow, Maximo and SAP.
The platform, in detail.
What is available today, who it pays off for, how it is built for production teams and where it runs.
What is available today.
Forward geocoding
Address to coordinates, with precision and confidence.
AvailableReverse geocoding
Coordinates to the nearest valid address.
AvailableArea lookups
LGA, electorate, postcode, suburb and custom zones.
AvailableBatch geocoding
Up to 100 addresses per call; Excel connector in alpha. Larger sets run as jobs, below.
AvailableStatistical areas
ABS SA2, SA3 and SA4 on every enriched address.
AvailableRoad distance
Driving distance, time and a 10 by 10 matrix.
AvailableDirections
Turn-by-turn between two points, from the same routing engine.
AvailableZone Manager
Create, edit and archive zones on a map. Backend app, not on this site.
AvailableCustomer console
Keys, usage against quota, request trace and a playground, served by the service.
AlphaAsync bulk jobs
Up to 50,000 rows as JSON or CSV. Download results and an exceptions list; cancel any time.
AlphaWebhooks and idempotency
Signed job-completed events with retries, and an Idempotency-Key so a retry never starts a second job.
AlphaPlans and quotas
Sandbox, standard and enterprise plans with monthly call quotas and quota headers on every response.
AlphaBuilt for production teams.
Six things that exist in the code today, each backed by an automated test. They run on a test database, not yet on a live customer deployment.
Tenants kept apart
Every tenant-owned row carries a tenant id, enforced in one module. A foreign row answers “not found”, and the tenant comes only from verified identity.
Provider licences respected
A provider that bars storage leaves no raw answer behind, only a hash and a time. Caching is off until you turn it on.
Every call traceable
A request id on every response, one id-only JSON log line per call with no key or address text, and Prometheus metrics for the platform operator.
Quotas per tenant
Plan quotas count per tenant across all keys, answer 429
quota_exceededwith a reset time, and one tenant’s use never touches another’s. With several pods the count can overshoot by about 5 seconds of traffic, and the per-key rate limit is per pod.Your data, your exit
Per-tenant retention windows, a full NDJSON export, and erase of one address or a whole tenant. Backups are not reached by erase.
A spec that cannot drift
An OpenAPI 3 spec and a Postman collection, checked against the running API by a test that fails when they disagree.
Tests ran on in-memory sqlite with mocked sign-in. Not yet proven on PostgreSQL, with a real identity provider, or with a customer. There is no independent penetration test and no certification. Read the trust page, including what is not yet done.
Where a correct address pays for itself.
The same engine, applied to the questions each industry already asks.
Insurance and risk
Know which flood, zoning or council layer an address sits in before you quote.
Retail and delivery
Name the delivery zone, fee or store territory for every customer address at checkout.
Government and councils
Match residents to wards, electorates and service areas, with the rule that decided it on record.
Utilities and assets
Tie every asset and customer site to one place, even when three systems spell it three ways.
Logistics
Validate in bulk, then drive distance and time between depots and stops from the same API.
Illustrations are schematic, not customer cases.
Runs where your estate runs.
One codebase, two deployment shells. SAP customers can run AddressIQ on BTP with HANA and XSUAA (designed for it; the HANA runtime is not yet proven in a live subaccount). Everyone else runs the identical product as a Docker or Kubernetes stack on AWS, Azure, GCP or on-prem, with no SAP BTP subscription.
| SAP BTP deployment | Standalone deployment (Docker/K8s) | |
|---|---|---|
| Business logic, routing, zones, billing | Same codebase; the test suite runs on SQLite and PostgreSQL | |
| Database | SAP HANA Cloud | PostgreSQL + PostGIS |
| Identity | XSUAA / SAP IAS (Azure AD federation) | Any OIDC IdP (Keycloak 26 tested with real tokens; Entra ID, Okta and XSUAA not yet tested) |
| Admin UX | Fiori Elements on your launchpad | Generic web admin + the same JS widget |
| BTP subscription required | Yes (you already have it) | None — $0 BTP cost |
Priced to your estate.
Two ways in: an add-on for an existing SAP estate, or standalone for any other. Prices are not set yet, and there is no self-serve sign-up or card billing. Book a briefing to talk about your estate.
How it is packagedPlain answers.
Is the data on this site real?
No. The live demo runs the real routing, zone and enrichment engines against a small synthetic Australian dataset, and every response is labelled dataMode synthetic. Production connects real providers.
Where does production data come from?
From the providers you enable: authoritative national sources, commercial geocoders and open data, on your contracts and keys or managed credentials. AddressIQ routes and enforces licence terms; it does not claim their data as its own.
Does AI see my addresses?
Only the alpha copilot features can, and only for a tenant where a platform administrator has switched them on (off by default) and an Anthropic key is configured. Then at most 20 stored addresses are sent, cut to suburb, state and postcode; text a person types into the copilot is sent as typed. The geocoding and zone path never calls a language model. Without a key the copilot returns grounded data instead of a narrative, and it never saves a change without a human confirming it. Tested with a simulated network call only.
Do I need SAP?
No. The same product is designed to run on SAP BTP with HANA and XSUAA, or as a standalone Docker or Kubernetes stack with PostgreSQL and any OIDC provider.
Which countries?
Routing chains are configured for Australia, the US and the UK; the demo runs on synthetic Australian data only. Zone boundaries are simplified Australian and New Zealand envelopes today; worldwide administrative boundaries are planned.
Can I sign up and try it myself?
Not yet. A free sandbox plan exists in the product (2,500 calls a month), but keys are issued by an administrator today. Self-serve sign-up and Stripe billing are not built. The demo on this page needs no key.
Is it certified or penetration tested?
No. There is no SOC 2, ISO 27001 or IRAP assessment and no independent penetration test yet. The trust page lists what is built, with its limits, and what is not yet done.
Are the plugins in the marketplaces?
Not yet. The Salesforce, ServiceNow, SAP, Dynamics and Excel wrappers are alpha builds. Marketplace packaging is on the roadmap.