Licensing details?

Imported Google Group message. Original thread at: https://groups.google.com/forum/#!topic/tyk-community-support/eDMMoi-ta-Y Import Date: 2016-01-19 21:03:25 +0000.
Sender:Marc Calder.
Date:Wednesday, 29 October 2014 17:39:18 UTC.

Can you please post some details on the license for Tyk? Based on the existing documentation, I understand the features that are unlocked with the licensed version, but you haven’t explained the terms of the license. You say that it’s $450 per year (I’m assuming that’s USD). Is that one license per server, per core, or is it a site-wide license? How is the license enforced? Does Tyk “phone home”? If it does, I’ll need to make sure I open the correct outbound port for it to use.

Thanks,
Marc

Imported Google Group message.
Sender:Martin Buhr.
Date:Thursday, 30 October 2014 09:35:22 UTC.

Hi Marc,

That’s a good question - and we’ll update the site to reflect this, the licensing for Tyk was meant to always be incredibly straightforward, flexible and non-interfering:
Licenses are in USD
Licenses are on a per company basis (licensee), so once you have one, you can use Tyk anywhere you like with the license key provided, on as many cores or servers as you like with as many users / API’s as you please, we only request that licensees honour the license and purchase a new one if they are using Tyk in another company.
The license is enforced by being time-limited, it will cease to work once the requisite number of days has passed, so a one-year license will offer full functionality for 365 days, then will revert back to demo mode (no data is lost, though the hot-reload service will not function), naturally licenses can be purchased for any length of time, but we’d need to talk about how that on an as-needed basis :slight_smile:
Tyk will never phone home, we understand that Tyk may be used internally for SOA and therefore think it would be terrible security practice, a burden for end-users and ultimately a performance bottleneck should anything go wrong with our systems, Tyk should be able to work even if we’re not.
Cheers,
Martin

Imported Google Group message.
Sender:Marc Calder.
Date:Friday, 26 December 2014 10:30:39 UTC.

Hi Brandon,

“One API” means one upstream domain, so “http://example.com”, that means all endpoints ("/widgets/{id}", “/sprogs/{id})”) underneath it and all versions (currently either managed by a header or a URL/form parameter, e.g. http://example.com/widgets/{id}?version=1.0).

Let me know if you’d like more detail, you can always get in touch with me directly at mar…@jive.ly

Many thanks,
Martin

Imported Google Group message.
Sender:Martin Buhr.
Date:Friday, 26 December 2014 03:05:48 UTC.

Hello,

Just to have it be explicitly clarified, could you explain what “one API” means? API versus endpoints?

https://api.example.com ?
https://api.example.com/v1 ?
https://api.example.com/v1/customers ?
https://api.example.com/v1/customers/* ?

Imported Google Group message.
Sender:Martin Buhr.
Date:Friday, 26 December 2014 10:30:39 UTC.

Hi Brandon,

“One API” means one upstream domain, so “http://example.com”, that means all endpoints ("/widgets/{id}", “/sprogs/{id})”) underneath it and all versions (currently either managed by a header or a URL/form parameter, e.g. http://example.com/widgets/{id}?version=1.0).

Let me know if you’d like more detail, you can always get in touch with me directly at mar…@jive.ly

Many thanks,
Martin

Imported Google Group message.
Sender:Marc Calder.
Date:Friday, 26 December 2014 17:30:59 UTC.

Oh, great! That is cool. If this works as “advertised” then it is totally worth the yearly fee/subscription.

Maybe also consider some crowd-fund option? I’m totally in Steam and early access games and whatnot, donating $50-100 here and there is worth it to fund great projects. Could be cool to see milestones.

Anyway, I will be downloading and checking this out today, sounds exactly like what I wanted. Lightweight, simple API gateway, dont need all the “enterprise ESB” stuff.