Servicestack client/text licensing [closed]

We started using servicestack v4, rest assured that there where no licensing limits on the client. At least that's what I could read out of servicestack's download page.

We are building our project according to mythz' answer to this question on servicestack how to structure an api.

The generic client works (so far) as expected without setting a license, but when a colleague created a test-client against the service, using the .Dump() method, he ran into this exception:

The free-quota limit on '20 ServiceStack.Text Types' has been reached. Please see https://servicestack.net to upgrade to a commercial license or visit https://github.com/ServiceStackV3/ServiceStackV3 to revert back to the free ServiceStack v3.

Let it be said: the .Dump()-method is not the issue here, we could do without it :) But, I really dislike these sudden exceptions! They suddenly blows up your project, reaching some sort of licensing limit. The last time something like this happended, it was inside an ormlite integration test. Everything works just fine, then KABOOM, you have to add your license to your NUnit test project.

Is there any more gotchas in this framework? Can we recommend to consumers of our API to use the servicestack client to connect, or will it suddenly come back and haunt us? I fully understand the need for licensing the framework, but this all boils down to me not trusting the framework which now is the core of my service!

What can you freely use the client-package and it's dependencies to, and what can you not?

Do you have any words of reconciliation? Will the ServiceStack.Client-mines be removed, or should we recommend all customers using the servicestack.client-package to buy a license to avoid their application from suddenly crashing if we add another property in a POCO-class? If ServiceStack.Client is not a "free", rather a "free-but" package, how can I know when calling a method if it's under some sort of quota or not?

As of v4.0.62 ServiceStack.Text is now free where now all restrictions have been removed from ServiceStack.Text as well as all client libraries depending on ServiceStack.Text including: