A potential customer reached out recently with a question about GeoBlazor Pro pricing. They were planning to deploy their solution to hundreds of customers and wanted to understand the licensing costs. The question: "We have to purchase one of those for every customer, right? When we deploy?"
The answer is "absolutely not!"
GeoBlazor Pro is a developer license. You pay per developer who's working on the code, not per deployment. If you have three developers building your mapping solution, you need three licenses. When you deploy that solution to 50 customers or 500 customers, you don't pay anything additional to us.
What are registration keys then?
The confusion comes from our registration key system, so let me explain that. You do generate separate keys for separate customers and solutions. But you're not paying per key. The keys are just identifiers (so we can help you debug issues, so you can track which deployment is which, etc). The thing you're actually purchasing is the developer seat.
If a developer leaves your team, you can unassign their license and reassign it to someone else. That's all handled in the licensing portal once you're set up.
When does Enterprise make sense?
One edge case worth mentioning: the Enterprise license exists for teams who need to develop and deploy entirely behind a firewall with no outside connection. The Pro license validates against our servers during build, not at runtime, so your deployed applications don't need to phone home. But if your developers can't reach our servers even during the build process, that's when Enterprise makes sense.
We're here to help
There's only so much we can fit on a pricing page, so we're writing posts like this one to fill in the gaps. And thanks to this customer's question, we'll soon be adding a FAQ section to the pricing page to cover this stuff directly.
If you've got questions that our docs or website don't answer, please reach out. Every question helps us figure out what needs explaining better.