For the last few years GeoBlazor has shipped as two things: a free, open-source Core and a paid Pro that added the tools for editing your data. With GeoBlazor 4.7, that split is over. Pro is now free and open source under the MIT license, the same license as Core, and its source code is public in the GeoBlazor repository right next to Core.
The minor version bump marks the license change, not a pile of new API. If you're on Core, this is a quiet upgrade. If you're on Pro, it's still a quiet upgrade in your code, but there's more to say about your license, so keep reading.
Why Did We Make GeoBlazor Pro Open Source?
First, because the commercial machinery cost more than it was worth. We spent real engineering time on license validation, obfuscation, a separate build, and a private repository that had to stay in sync with the public one. On top of that was the licensing/payment tracking and renewal system. Every one of those pieces had to be maintained, updated, and tested.
We built GeoBlazor for our clients and partners in the GIS software space. We always had an open-source mindset, which is why the free Core library was the first that we released. When we added Pro, it was with the intent to support the development through professional fees. However, when we look back, we can see that partner engagement and helping clients with support is a better fit for who we are at dymaptic—a professional services organization that builds custom GIS software for clients.
What Changed in GeoBlazor 4.7?
- Pro is MIT licensed:
dymaptic.GeoBlazor.Prois published withPackageLicenseExpressionset to MIT, so NuGet no longer asks you to accept a license when you install it. The package IDs did not change. - Pro's source is public: the projects, tests, and templates live under
pro/in the GeoBlazor repository, and one set of build scripts builds and publishes both packages. - No more license failures: in 4.6.1, Pro threw
InvalidLicenseExceptionfor a missing key, a key for an older major version, an unlisted URL referrer, or an unlisted MAUI assembly name, and the map didn't render. All of those checks are gone. - A security update: Core's bundled JavaScript picks up
protobufjs7.6.5 with the upstream security fix.
Do You Still Need a License Key?
No. If there's no key in your configuration, or GeoBlazor finds a key it doesn't recognize, it writes this message to the browser's developer console once per app run. On Blazor Server, it also appears in the server log:
Thank you for using GeoBlazor! Please visit https://licensing.dymaptic.com to register.
That's the whole consequence. Your map renders either way. If you already have a key, leave it where it is: existing Core registration keys and Pro license keys keep working unchanged, under either name, and a valid key prints nothing at all.
{
"GeoBlazor": {
"RegistrationKey": "your-existing-key"
}
}
GeoBlazor:LicenseKey works the same way, since a lot of Pro projects were set up with that name. You don't need to rename anything.
What If You Have a Paid Pro License?
Nothing breaks today. We stopped selling paid licenses on October 13, 2026, and here is what that means for the ones already out there:
- We will honor your license through the end of its current term, including any support credits you haven't used.
- It won't renew. We've turned off auto-renewal, so you won't be charged again.
- Applications you've already deployed keep running after the term ends. That was always the deal, and it still is.
- Your current version keeps working with your existing key, and 4.7 doesn't need the key at all.
If you want dymaptic engineers available for help desk, integration, or deployment work on your own application, paid support is available as a separate, optional service. It's a service, not a different version of the library: there is no private build, and fixes ship in the public releases for everyone.
How Do You Upgrade to GeoBlazor 4.7?
Update the packages you use to 4.7.0. Pro 4.7.0 depends on Core 4.7.0, so if you're on Pro, upgrade both together:
dotnet add package dymaptic.GeoBlazor.Core --version 4.7.0 dotnet add package dymaptic.GeoBlazor.Pro --version 4.7.0
Both packages still target net8.0, so there's no framework change to worry about. Run your app, and you should see your map exactly where you left it!
What Comes Next With V5?
In V5, Pro's code will merge into Core, and what you install will become one package, dymaptic.GeoBlazor, under one namespace. V5 won't require a key either. We're targeting late 2026. The ArcGIS 5.x upgrade has been completed on our private V5 branch. When V5 is ready, you'll get a migration guide covering the package and namespace changes, and a shorter post than this one with the upgrade steps.
Frequently Asked Questions
Is GeoBlazor Pro free now?
Yes. Starting with GeoBlazor 4.7, the dymaptic.GeoBlazor.Pro package is published under the MIT license, the same as GeoBlazor Core, and its source code is public in the dymaptic/GeoBlazor repository under pro/. Dymaptic stopped selling paid Pro licenses on October 13, 2026.
Do I need a license key or registration key to use GeoBlazor 4.7?
No. Neither GeoBlazor Core 4.7 nor GeoBlazor Pro 4.7 requires a key to render a map. With no key, or a key it does not recognize, GeoBlazor prints one message to the console each time the app runs and keeps working. Existing Core registration keys and Pro license keys are still accepted under GeoBlazor:RegistrationKey or GeoBlazor:LicenseKey, and a valid key prints nothing.
What happens to my paid GeoBlazor Pro license?
Dymaptic honors every paid Pro license through the end of its current term, including any support credits you have not used. It will not renew, and auto-renewal has been turned off, so you will not be charged again. Applications you have already deployed keep running after the term ends.
Are there breaking changes in GeoBlazor 4.7?
No. GeoBlazor Core 4.7 and GeoBlazor Pro 4.7 make no breaking changes to the APIs you use, so upgrading is a package version bump.
How do I upgrade to GeoBlazor 4.7?
Update the dymaptic.GeoBlazor.Core NuGet package to 4.7.0. If you use GeoBlazor Pro, update dymaptic.GeoBlazor.Pro to 4.7.0 at the same time, because Pro 4.7.0 depends on Core 4.7.0. Both packages still target net8.0, and you can leave your existing key configuration in place.