<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Coordable (Posts about here)</title><link>https://coordable.co/</link><description></description><atom:link href="https://coordable.co/categories/here.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><copyright>Contents © 2026 &lt;a href="mailto:contact@coordable.co"&gt;Nikola Tesla&lt;/a&gt; </copyright><lastBuildDate>Tue, 28 Apr 2026 16:26:40 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>HERE price increase by 6% in 2026</title><link>https://coordable.co/blog/here-geocoding-price-increase-2026/</link><dc:creator>François Andrieux</dc:creator><description>&lt;p&gt;HERE Technologies is updating its pricing from April 2026. This post summarizes what matters for geocoding users: effective date, what changes, and who is affected.&lt;/p&gt;
&lt;p&gt;&lt;img src="https://coordable.co/images/providers-logo/here-logo-large.png" alt="HERE Technologies logo" width="200" class="d-block mx-auto"&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Table of contents:&lt;/strong&gt;&lt;/p&gt;
&lt;div class="toc"&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://coordable.co/blog/here-geocoding-price-increase-2026/#what-here-announced"&gt;What HERE announced&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://coordable.co/blog/here-geocoding-price-increase-2026/#what-this-means-for-you"&gt;What this means for you&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://coordable.co/blog/here-geocoding-price-increase-2026/#where-to-go-from-here"&gt;Where to go from here&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;
&lt;hr&gt;
&lt;h3 id="what-here-announced"&gt;What HERE announced&lt;/h3&gt;
&lt;p&gt;From April 1, 2026, the price of the &lt;strong&gt;HERE Base Plan&lt;/strong&gt; will increase by &lt;strong&gt;6%&lt;/strong&gt; for new contracts, renewals, and extensions. Existing contracts remain unchanged until renewal or extension.&lt;/p&gt;
&lt;p&gt;HERE Technologies communicated the following:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The prices of &lt;strong&gt;all 35 HERE Location Services and Data IO&lt;/strong&gt; using the pay-per-transaction model will increase by &lt;strong&gt;6%&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;This price increase applies to &lt;strong&gt;all new subscriptions and (auto-)renewals from April 1, 2026&lt;/strong&gt; onwards.&lt;/li&gt;
&lt;li&gt;The price of the &lt;strong&gt;Developer technical support plan&lt;/strong&gt; remains unchanged.&lt;/li&gt;
&lt;li&gt;These pricing updates will be reflected in all future contracts and invoices from April 1, 2026 onwards.&lt;/li&gt;
&lt;/ul&gt;
&lt;hr&gt;
&lt;h3 id="what-this-means-for-you"&gt;What this means for you&lt;/h3&gt;
&lt;p&gt;If you sign a new contract or renew on or after April 1, 2026, you will see the new 6% pricing. For coverage, rate limits, licensing, and current pricing details, see our &lt;a href="https://coordable.co/provider/here-geocoding-api/"&gt;HERE Geocoding API&lt;/a&gt; guide.&lt;/p&gt;
&lt;hr&gt;
&lt;h3 id="where-to-go-from-here"&gt;Where to go from here&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://coordable.co/provider/here-geocoding-api/"&gt;HERE Geocoding API&lt;/a&gt; — coverage, rate limits, and licensing.&lt;/li&gt;
&lt;li&gt;&lt;a href="https://coordable.co/blog/geocoding-prices-2026/"&gt;Geocoding prices in 2026&lt;/a&gt; — compare HERE with other providers.&lt;/li&gt;
&lt;li&gt;&lt;a href="https://coordable.co/comparison/google-vs-here-geocoding-2026/"&gt;Google vs HERE for geocoding&lt;/a&gt; — head-to-head comparison.&lt;/li&gt;
&lt;/ul&gt;</description><category>2026</category><category>api</category><category>geocoding</category><category>here</category><category>pricing</category><guid>https://coordable.co/blog/here-geocoding-price-increase-2026/</guid><pubDate>Fri, 06 Mar 2026 12:00:00 GMT</pubDate></item></channel></rss>