Over the past two and a half years, I spent over seven thousand hours on building and improving one of the most intricate modular systems available for WordPress yet: the Extension Manager. Conjoined with WordPress, The SEO Framework, and my purposely-built API servers, it features hundreds of first party innovations to make working with it effortless and to make various unique features possible.
This was all for nothing.
Well… that’s a bit harsh. Let me rephrase that, and literally iterate on what I’m trying to convey.
The SEO Framework (TSF) is free, and it will stay free. The Extension Manager is free, and it will stay free. But free means that time spent on research and development won’t be paid for.
Now, don’t get me wrong: I love working for approval and praise. Every word from the community is great, and it makes me rest well knowing that people are happy because of what I did well. But unless the approval and praise are monetary (although some are), I can’t afford to spend more time on the free (did I mention literally?).
The plugin pays for itself; but, whilst abstaining dishonesty and spamming you with ads, the company running this show is still categorized as a start-up – this can’t warrant sustainability. So, I either need to start throwing ads in your face, or I need to change the delivery of the premium products.
TL;DR: The Extension Manager plugin is intended to provide both free and premium software and services. Unfortunately, at the end of the developing the initial release, I learned that some of the things planned weren’t allowed on WordPress.org. I pushed through anyway, and I still released it—hoping for the best—, but I now face various restrictions that hinder further, sustained development. So, I’m now providing the Extension Manager plugin from my servers. Download it here.
Before I continue, I do want to thank the WordPress.org plugin, meta, and forum teams, and all the reviewers, translators, and customers. It’s thanks to you I didn’t have to abandon the project, and it’s thanks to you I’m still more than willing to improve and sustain both my free and paid solutions.
Plugins on WordPress.org may not lock any functionality that’s not bound to an API service. So, if you wish to publish premium software, you may only restrict its functionality when it requires your remote API servers to operate as intended. In short, it must be Software as a Service (SaaS).
SaaS is a great model for many businesses, and it even is for SEO. However, there’s a big problem with it: SaaS is expensive, complicated, and requires a lot of maintenance to prove security, scalability, and stability.
Unleashing a single full-stack web developer on both the server and the software is feasible. However, each solution brought will be a full-time job to maintain. Now, I have created multiple solutions, because I must allocate the company to various markets.
Apart from that, the Monitor extension, which is far from what it’s supposed to be, will require me to expend at least twenty thousand USD, yearly, to make the promised uptime monitoring feasible. And another ten thousand to introduce per-page reviews. These expenditures are apart from time spent on development.
The Local and Focus extensions require me to pay third parties up front to access petabytes of data, and I depend on their competence on manipulating that data; which is why, for now, only the English language is API-supported for Focus.
Now, I want to spend my time on simpler, more robust, and more beneficial solutions. Like Articles and Honeypot: two amazing enterprise-grade extensions that don’t require SaaS. They were forced to remain free, even though they weren’t meant to be. Non-SaaS solutions are more fun to create, too, as they deploy much faster.
But, once again, I can’t generate revenue building non-SaaS solutions published on WordPress.org.
So, the solutions users want to pay for are either free or aren’t created, and the solutions users are paying for are too expensive for all parties involved.
WordPress is subconsciously anti-competitive
The WordPress.org algorithms will not recommend any plugin that isn’t brought by Automattic or isn’t a member of the topmost installed. For newer plugins, this means that all your work is subverted and diluted into arcane desolation, never to be appraised for what it might’ve been.
Now, I’m not accusing WordPress—I’m explaining these events. Automattic’s software is exemplary and built according to the most rigorous standards. I would recommend their products over all comparable others at any day, and I’m glad they’re put in the spotlight. And the way WordPress.org is set up is to help users get started quickly, and this is a good thing; unfortunately, this also has apparent repercussions for new plugins.
So, if you want to write plugins for WordPress, I can guarantee that you’ll only make it if your solutions are niche, or when your competition’s products are terrible.
I consider myself lucky with TSF, but I also know that if I were one of the first to release a plugin of this kind and caliber, it would’ve gained millions in users. It deserves millions of users.
This all leads to an issue: My software lacks the numbers to sustain the current pricing model. This issue might be less severe in a few years as the plugins keep growing, but I can’t risk nor afford to wait for that to unfold.
I don’t doubt that TSF will be active on a million sites simultaneously in a few years. However, I do want to ensure this fate by implementing better practices.
Commence new commerce
So, I want to ensure revenue which sustains the operational costs of the plugins, a few developers, designers, system administrators, and more, with plenty of room for gratifying, precarious innovation.
I also want to branch out of meta-SEO with the Extension Manager, delivering solutions that people need and want in other sectors. Even more so, I think the Extension Manager plugin has the potential to branch out to be the all-in-one modular solution for your website. Think of Jetpack, but then for more than just blogging.
To make this happen, I can’t afford spending all my time providing new, free software. There will be a few intermediate changes; thereupon, I might decide to adjust or reiterate on some of these changes based on your requisites.
Now, I will never take free features away from you which were brought in The SEO Framework. It will keep receiving updates at the same pace and quality as before. It is, after all, supporting software for the company. It is what makes my job as a WordPress plugin developer possible. I’m only changing how I’m delivering the extensions for the Extension Manager.
A new shop
For the keen-eyed, you’ll notice that the shop has been redesigned and reclarified.
It will no longer offer you to choose the number of sites, as almost no one made use of this. Instead, I doubled and fixed the number of websites you can connect to per license by default, without additional costs. This allows you to migrate your site, set up a sister site, or even pay it forward to a client, all with a peace of mind.
Coincidentally yet conveniently, even with the bulk discounts at our competitors, you’re still better off with us. So, when you need more sites than shown in the shop, you should increase the number of licenses in your cart.
Moreover, the shop now differentiates subscriptions based on the needs for your site. Not all sites require the premium extensions (yet), and not all sites have a dozen authors. The sites that make more use of my services will have to pay more. Fair? Fair.
New API services
A new API service has been set up that quantifies the API requests you’ve sent to it per calendar month, and it can tell you how many requests you still have left. Setting this limit will allow me to expand the services confidently without risking damages. I will close the old service somewhere in Q1 2019.
For current subscribers: Aside from a few exceptions, all currently active subscriptions will be upgraded to get 5000 requests per calendar month—which is what the newly introduced Premium license pertains—while maintaining the previously provisioned pricing, indefinitely. Depending on your needs, some of you are better off with the old pricing model, while others might find the new model more suiting; you must determine this yourself. For your convenience, you may repurchase or cancel the old licenses via your dashboard.
Soon, I will jump on providing extra support for the new Gutenberg editor. And, a new extension is planned for 2019 which makes great use of the new API services: Real content quality assessments.
New extension and subscription types
I’ve added a new extension type, lying between Free and Premium, there’s now Essentials. To use this type, you’ll require an Essentials or higher subscription.
Now, some extensions that were free (but, which were never meant to be) will be moved to this type. I thoroughly understand that not every user is too fond of this change; so, I’m placing a significant introductory discount on the Essentials subscription. The discount will hopefully make the transition easier for many users. Don’t miss out, because you might regret not being able to access future extensions and other improvements.
Another subscription type that has been added is called Enterprise. This subscription allows for even more simultaneously connected sites, and many more monthly API requests – ideal for news publishers and large blogs with subdomains.
Removal from WordPress.org
The Extension Manager will be removed from WordPress.org in a few days. To make sure my users notice and aren’t left with non-updating software, I will send out notifications to most users via various routes.
With this, I am no longer imposed by the WordPress.org plugin guidelines (…rules) that limit my flexibility and innovation. This freedom means I can start delivering awesome extensions, tailored par excellence and with stupendous love and care, that don’t need to be SaaS, available via a subscription.
The plugin will stay free and open-source software (FOSS), and you can view it on GitHub. So, you’re free to browse, share, improve, and even fork the code.
I have also set up a secure update service from which you can download the Extension Manager and update it on your website. Every site will get free updates for the plugin; but, the plugin needs to be activated to request updates.
Moreover, the support will remain public; now via GitHub.
I believe that all these changes will ultimately benefit my users. Definitely so in the long run.
With more revenue to invest in third-party services, developers, translators, copywriters, marketers, and designers, our plugins will become more accessible, powerful, beautiful, and potent. The content provided on this site will be more helpful and insightful. And, most importantly, I can prove fairness works in open source, too.
This should benefit everyone. I hope you’re with me on this.
Comments are closed.
Appreciate the very detailed update and planned roadmap of changes coming but perhaps don’t include a click-bait title next time. It obviously wasn’t all for nothing and the first thing most people will think, myself included is that the plugin was being abandoned. Not a good feeling to start reading and think you have to now migrate all of your sites to another solution after recommending it to many people :-( But I’m glad that’s not the case and perhaps the title helps push more people to read it. We all have unforeseen circumstances but the time spent isn’t wasted, I’m sure a LOT has been learned during that time and will help shape the product going forward.
The big reason I switched my sites is that you keep things simple. It does exactly what it says it will and it’s not bloated with lots of features no one needs and this is the kind of product I’ll happily pay for.
Will definitely continue with the plugin and see how it evolves. Have switched over to your new version of extension manager now. Keep up the excellent work and it will continue to grow :-)
My apologies for the double entendre! In this article, “for nothing” means “free”… with a dramatic aftertaste. It does go a bit against my advice, but I did want to try it out and see the effects :)
I’m not only keeping things simple, but I also want to do them right. Each feature takes months to perfect; unfortunately, this can’t be marketed. And, with the rise of new SEO plugins (which are doing things wrong), they’re pushing this plugin away with catchy phrases like “more features” (that are harmful to your site).
I’m glad you’ve put your trust in me, Brendan :) Thank you!
You’re very welcome buddy, keep up the excellent work. Good quality trumps all the others any day of the week. And you’re the only SEO plugin I and many colleagues recommend when discussing WordPress SEO!
You dont have unlimited sites can connected in the same time to use it for many websites and blogs in the same time so it will be too much expensive if i used it for 8 website by 300$ and there is no guarantee that the price will not increased year after year.
Also about the free extensions there is no guarantee that is will not be paid also!
And the updates for free extensions will work with not paid or activated extensions manager or need to be removed and reinstalled everytime we need to get updates?
Really your post about this topic very complex and we dont know what will happen exactly so please let us know to decide what we should do.
Waiting your reply,
Hi there, Ahmed!
I apologize for the confusion. I’ll try to be more concise below.
The SEO Framework won’t be affected by this, at all. It’ll only get better!
This change is only for the Extension Manager. I’ll be hosting the new plugin, instead of WordPress.org.
As of v2.0.0, the subscription requirements for the extensions won’t change. All free extensions will stay free, forever. The SEO Framework plugin will stay free as well. So, you don’t need to worry about that!
I will never remove features unless it’s absolutely necessary to comply with WordPress’ inner workings or Google’s search engine.
The Extension Manager software package includes all extensions. You’ll always get free updates for this package, even without a subscription, delivered right to your WordPress dashboard.
The new update server is already live and working. The new plugin, which you can download via this site, will connect to my update servers. These servers are compatible with WordPress’ update API; so, you’ll receive updates in the same manner as before, but no longer from WordPress.org.
I am not allowed to change the old plugin so it can get updates from my servers. You’ll only have to delete v1.5.3 if you wish to migrate to v2.0.0, which is to prevent clashing of the old and new plugin. No settings will be lost in this process.
As for the licensing, you can get more sites for less when you purchase the Premium subscription rather than the Enterprise one. The Enterprise subscription is meant for larger corporations with many people working on a single network; this is why there are many more API requests available. So, it’ll be $198 for eight websites (and 10,000 API requests) when you purchase Premium twice.
This change in licensing was necessary to provide new extensions, new services, better updates and support, and a neater experience overall.
I hope this summary clears it all up for you!
Thank you for make more clear.
The problem is that i and my colleague used it for about 31 websites and blogs and also in next year will be up to 50 to 60 websites and blogs and the cost for all this huge for us so we think very seriously, we have to try something else if there no solutions fair with fair price for this numbers of websites and blogs and it’s up to you if you provide a solution for agencies or licence type fit this type of business with reasonable price we can go ahead with it.
Also i have one more question please.
is that one website means the plugin will work for website with its blogs as subfolder by one licence or one licence per wordpress installation
this the type of the sites and blogs that i use as subfolder by two WP installations one for site and one for blog in the same domain so is that need one licence or two how the plugin will count?
Hope i can get good solution and support from your side to help us to go on with our business.
Waiting your reply,
Thanks for leaving your concerns. I discussed my stance of fair pricing on the about us page.
I also showed some calculations under the “A new shop” header in this blog post, and the amount you pay for any number of sites is less with us than at most companies in the same field.
I’m not forcing you to pay for my products. However, I do need to run a business. If you don’t think my products are worth the price, then you don’t know the time invested in optimizing them. I’m not here for a quick buck; I’m here to deliver a lasting solution that’s perfect.
I tried giving bulk discounts for two years. But, given that 99% of the users didn’t make use of those, I know I’m better off simplifying the process for most users and giving more sites by default.
As for your last question: yes, one site means one unique WordPress installation. The new pricing model covers the example you provided.
Many have not fit into the wordpress.org ecosystem for a long time. For many plugins I use GitHub Updater: https://github.com/afragen/github-updater
Upgrading the Extension Manager to version 2.0 was no problem. Settings saved. At the moment I have only one question left – localization. Now this is not the main thing, but in the future I hope to see a solution for support localization
Thank you, Sybre!
Hi Vitaliy :) I’m glad to see you around here, too!
I don’t want my users to install additional tools to keep their site updated, so the plugin has the update API embedded. With this, it’s also possible to send out translation files per site localization requirements.
What I love about hosting on WordPress.org is that everything is taken care of with excellence. They bring so much value that I even wanted to risk the business over it. Now, I need to bring all that value myself, and I want to make the experience similar to what WordPress gives, so it’s seamless.
Unfortunately, I couldn’t find the underlying software of WordPress.org’s translation system. But it closely resembles what Weblate offers. With something like this implemented, translating the plugin should be as accessible as before. I’ve planned to introduce this, but due to the complexity and overhead it brings, it has a low priority.
For now, I’ve included all translations in the plugin package. And, the POT file is also included in the
/language/folder of the plugin. So, with desktop translation tools, like Poedit, you can bring translations to me. I’ll be happy to compensate for your time :)
Great move into this new adventure of yours :), Congratulations!
I just wanted to let you know that today I downloaded version 2.0. I checked the language folder and notice that there where only a couple of language files. I did see the Spanish mo file but not the po file. Anyhow I just thought of letting you know.
I have a copy of my old translation so I copied that over to the language folder and will review the changes before I submit the latest updated version.
I will keep the Spanish language up to date :)
Thank you so much for your ongoing and widespread contributions, Manuel!
I didn’t include the
.pofiles in the plugin package as they’re not used in operation of the plugin. But, I’ve just uploaded them to Github, and fixed the text-domain loader, too :)
Hi there so perhaps this is to detailed in short what is happening? in “lame terms” and what do i need to do as a user?
Hi there :) I left a “Too long; didn’t read (TL;DR)” paragraph in the first section for the time-constraint readers. The rest of the blog explains why I had to take these actions and what’s changed (and going to change) in the way I deliver services.
To further demystify the course of action for those not able to read the full blog post, here is the essence, in one paragraph:
The plugin guidelines on WordPress.org forced me to deliver services that are currently too expensive for both the company and the user. They also forbade me to ask a price for my time spent on innovation. So, I’ve changed the pricing model, the delivery of extensions, and the API services. Henceforth, the API requests are enumerated to quantify expenses on current and future services, and I’ll start bringing amazing “Essentials” extensions that don’t require API services, for a lower price.
To ease the migration, there’s also a discount at the shop.
Here’s what users need to do:
1. Visit the new Extension Manager plugin page.
2. Follow the installation instructions. For current users: note the N.B. below.
3. That’s it!
FYI – several of the “free” extensions in 1.5.3 are no longer free. Such as focus, articles, and honeypot. I thought you said all “free” extensions would remain free?
The plugin on WordPress.org, at version 1.5.3, still provides those extensions for free. However, I’m going to stop supporting that plugin.
The plugin I deliver from this site is at version 2.0.0, and I will provide support for this indefinitely. The free extensions I bring in this version will stay free, forever; which is what I tried to convey in my comment above.
I didn’t plan for the Honeypot and Articles extensions to be free forever. I first released them as Premium extensions. Soon after that, I received a notice from the WordPress.org plugin team that I must deliver those for free or face removal of the plugin.
And unfortunately, with Gutenberg (WordPress 5.0), I can’t provide Focus for free anymore. I learned that I must rewrite large parts of the extension to support both the old and the new editor. This shift with the new editor will bring many developers an uphill battle for at least a year, especially for those who work with the page content.
Thanks for the reply, Sybre. I understand now – sorry I didn’t get that right away. I’ll use the 1.5.3 until we can afford to pay the annual fee for Essentials. The fee you charge is fair – but things are tight for us at the moment, so we’ll wait until times are better! Thanks again for your hard work.
PS – can you shed some technical details how the “notify search engines” aspect of the framework plugin works? Does it keep a log somewhere? I was having indexing issues with Google (i.e., my site wasn’t appearing in search results). I had to use Google Search Console to manually submit my sitemap in order for it to index… just figured I’d ask while I have your attention!
It’s always good to ask when you’re unsure :) And thank you so much for your support!
As for your question on notifying search engines: TSF pings search engines the sitemap location whenever it updates. The technical details can be found on their support page, under “Submit a sitemap“.
I’ve also noticed that Google doesn’t honor this request as of lately, but I couldn’t find enough evidence. This behavior could be related to a “patched” vulnerability in Google’s system.
I know, the vulnerability issue is a juicy subject; but, before this thread goes off-topic even further, I must ask you to inquire other/further questions you have that are unrelated to this blog post on the plugin support forums. You’ll get my attention there regardless :)
could you put it in laymans terms as to what will be different without the “Articles” plugin (for free) anymore? I am on the fence whether to get the new Extension Manager or keep the old one and disable the (what seems to be a) permanent nag manually. Is that a terrible idea?
“For news articles, it allows them to be displayed prominently within Google’s search carousel.”
“For blog postings or investigative reports, it improves search presence for recurring visitors.”
Is the SEO framework with free extensions still the best free option compared to other plugins?
Could the new Extension Manager include alternate versions of the now-paid plugins as free “legacy” versions that just don’t receive updates anymore?
Hi there FlyingHawk :)
The Articles extension relies on The SEO Framework for its data. If The SEO Framework changes (which it will do), the extension needs to be updated accordingly.
I’ve explained the repercussions here. There, I also provided a snippet that disables the nag.
However, as both WordPress and The SEO Framework are ever evolving, I can’t promise compatibility indefinitely. Eventually, something will stop working.
I’m not going to ship software that’s not up to the highest standards; as such, I won’t send out legacy versions.
Although I wish all my time and efforts were free of charge, unfortunately, I’m unable to sustain this.
I also firmly believe that The SEO Framework is the best option for SEO out of the box, with or without extensions.
Hey Sybre, I understand your changes with moving away from (rigid, old fashioned) WP. It would be nice though if you would add a `composer.json`. 😉 Thanks and keep up the good work! 🙂
Hi Henk! I think Nathan caught up to your comment and did an awesome job by submitting a pull request! :)
Ahh, Nathan, thanks (again)! 🙂
Should I overwrite the extensions plugin with the new download link provided by you? How will the migration take place from the current WordPress repository to your repository?
You can safely overwrite the plugin files via FTP. Or, you can follow the installation instructions provided on the plugin page, but you’ll have to delete the old plugin first.
As a response to your question, I just added some extra details on that page, including that no settings will be lost when migrating.
When the plugin is active, it adjusts the WordPress plugin updating API for the Extension Manager so that it can request updates from my servers.
I just want to say that I wish you good luck in your business. I used TSF since it’s first days, it’s the best SEO Plugin in the market, no doubt.
Thanks a ton
Thank you so much, Charaf!
Hello Sybre! The same as Charaf, I want to wish you luck and success! I understand your problem and I’m sure you are trying to give a good answer to it, that will be satisfactory to you an your users.
Unhappily enough I can’t substantiate my good wishes paying for the essentials, at least not this year, maybe not even the next, as I’m the “front-end” of a very small nonprofit organization that depends on our own private resources to maintain some historical archives. Not only we make do with a very tight budget, but the political crisis situation in Brazil means that dollars became very expensive in the past two years.
Nonetheless, I will continue to use and recommend your plugin, as it is the best! And I believe that from December onward I will be able to contribute with the Brazilian Portuguese translation.
Finally, if you are interested in the effects of your opening statement, I too thought that the plugin would be abandoned and almost had a heart attack! (lol) Young man, I’m too old for this kind of scare!
Best wishes ever!
Thank you so much for your support Arutha!
Although I don’t have the (technical) resources to offer special discounts and donations to nonprofits (yet), I’m always happy to compensate for your contributions. Feel free to reach out to me via my contact page (link in the footer).
I do hope your mission won’t be hindered by this change.
And you too, best wishes!
G’day Sybre, not sure what it all means, might have to reread a couple of times :).
No matter, I’ve migrated nearly all the sites that I look after to your plugin long ago. After reaching out to you in the past you’ve been very helpful and friendly, so from a born-in-Australia-dutchman to a real one, good luck and I hope you get the support that you deserve as well as the monetary dividend you need. After all, we all gotta live.
Hi Tim, I’m glad to see you around and have your support, too! :)
To get a better understanding, you might find the summary found in my comment here useful.
I have learned that when you build your solutions/apps/plugins on top of another platform there always comes a time where you have to break away. We have seen this many times i.e the App Store story and the Twitter API Story. I respect your decisions and will continue to support you and your developments by using your plugins on client WP projects.
Hope this all goes well.
Yes, like on other platforms, with so many rapid developments going on in WordPress, it’s very time-consuming to keep up. We can never finish the plugins, which could’ve left us time to innovate and take a step back. Even more so, we’re sometimes forced to steer away from what we have envisioned. A great use case is the upcoming Gutenberg editor, which hopefully will keep its promise by easing future development. Fingers crossed!
could you possibly give discount for pro package, it’s way to high in my opinion.
I only give discounts on rare occasions, like with the Essentials introduction price. So, I’m afraid I can’t offer discounts on the Premium package. Luckily, the price with us is less than at our competitors; even without discounts.
I downloaded your plugin today. Found out the old ext manager will no longer be supported. Got rid of my other SEO plugin (Squirrly). Then, saw that a new ext manager is available. I can’t afford the Essentials price at the moment (fixed income is truly wrong and so evil…lol) so I will be sticking with the old Ext Manager until I can afford the new updated version.
I still have SmartCrawl (an SEO plugin). Why? Don’t know. lol
I didn’t realize WordPress was like that. I don’t know how to code plugins. Speaking of plugins…are you going to rewrite The Seo Framework Plugin so you can have it on your server instead of at WordPress? Just a thought. Probably more work that you don’t need. lol
Reasons to keep your plugins:
1. You care about your plugins and customers.
2. No ads. They are so annoying.
3. So far, I haven’t had any problems with it. With Yoast, I had a security issue.
4. I can tell that you work really hard on the plugins to make them better than the ‘Big Name’ ones.
Although I must admit I’m a big fan of WPMU DEV, I can’t say if our SEO plugins should work alongside.
The SEO Framework will stay a community project, and it’ll be on WordPress.org indefinitely. I have no plans of removing it.
You can use the old version of the Extension Manager with confidence for now, as I’m still supporting it until January 1st, 2019; although I stated differently in this blog post.
And thank you so much for your kind words, it means a lot! :)
How is this going to affect current subscription?. I bought into your deal 2 years ago for a set price for life. Will this continue?
Are we going to need to remove everything now and reinstall for each website? If so, when should this be done?
I’m glad you’re still around :) You may renew and resubscribe to the Early-Bird subscription indefinitely, it’s also compatible with the new plugin.
What it truly means for your subscription is described in the 2.0.0 changelog, at the bottom.
I recommend switching over before January 1st, 2019. As from then, I’ll stop providing security support for the old version.
When you say renew and resubscribe is this at a cost? We are in the middle of a paid current contract with you. If it is a cost then that won’t work as we have pushed the charge to clients and they won’t pay twice (neither would you). Are you in effect saying that there is an increase onto charge we already paid? Or have I read this incorrectly, which I hope I have?
I want to stay with you, however, if we have to pay twice then the answer is no and you should honour what you have in place with your current customers who are yearly subscribers. I’m reluctant to start moving to the new system if we have to remove all existing plugins and pay again.
Your above response implies that we need to re-sign up again and pay further and you re saying if we do that we get a discount. Again I ask you, is this what you re saying?
Don’t get me wrong here, I agree with what you are doing and understand your reasoning, however, we need to understand how this affects us as we have existing customers using this software. I don’t think you have been clear about this.
No, currently running subscriptions haven’t changed in price nor the number of sites. Whoever has signed up for a subscription previously may resubscribe to it for the amount paid initially.
I explicitly didn’t want to affect my current subscribers negatively in any way; you are who made this project sustain. I think the term that describes this is “grandfathered in.”
However, it’s up to you to decide whether upgrading to the newer licenses is more beneficial than staying with the older.
I hope this clears up the confusion :)
Yes, it does clear up the confusion, somewhat. So, is it a matter of just resubscribing and this will pick up any credit we have left?
The gist is that nothing has changed for you, other than that you’re now seeing the number of API requests tied to each subscription, which resets every first day of the month.
Subscriptions renew automatically. May you’ve chosen to cancel a subscription, or if you want another key, then you can select what you had previously, again, from your dashboard.