Pricing

• The map. Unauthenticated, no key, no account. It is the public face of the open data and it should not sit behind a form.
• A developer tier of the API. A real quota, enough to evaluate and to build a small internal tool, free of charge. The fastest way to lose a market is to charge before anyone can see whether the data is right.
• The source. The core is AGPL-3.0; self-hosting is always an option and always free.

Above the free tier, usage is metered in units, where one route or one isochrone is one unit and a matrix is metered per pair. The meter already exists (`client_usage`), so a future invoice and the usage page count the same thing.

Rate limits, scopes and the history window are per plan. Prices are not published and are quoted per deployment; a plan change that lapses downgrades to the free tier rather than revoking the key.

A small proprietary layer under ee/: SSO, audit export, and an OEM licence for embedding the platform in another product. Licensed annually per organisation with a seat count. It does not change the map, the data or the API — those are the same code you can self-host.

• Invoices in SGD, monthly or annually, in advance for subscriptions.
• Cancel at any time; the plan runs to the end of the paid period.
• Usage already consumed is not refundable. A billing error is corrected in full, including any overcharge.
• No payment integration is live yet; nothing can be charged by this deployment.

No uptime SLA is offered today. The status page reports what this deployment can actually check, and there is no 24/7 on-call rota. When an SLA is offered it will be written here with its credit terms, not implied by a marketing page.

Commercial enquiries: no address is configured for this deployment yet — set NEXT_PUBLIC_CONTACT_EMAIL before launch.

Access to data its licence does not allow to be resold, removal of the attribution, or a different answer from the routing engine. The tiers sell capacity, support and enterprise integration — not a better version of the facts.