> Under Apache 2.0, every version we've released stays under those terms whatever we do later.
But isn't that true of all licenses? While you can relicense anything, doesn't a published/released codebase stay under the license its released with?
> You may not move, change, disable, or circumvent the license key functionality in the software, and you may not remove or obscure any functionality in the software that is protected by the license key.
So a fork would have to keep any code related to or protected by a license key, even if it is no longer possible to obtain a license key (say because the copyright owner went out of business).
One of the big advantages of using open source software is that you are much less dependent on continuity of service from the vendor. If the software maker goes out of business it is possible for the project to continue life in a fork made by a community or another business, foundation, etc. However, the limitations in the Elastic license make that less likely to happen, and limit what you can do with your own fork.