wyDay blog

We had a day of unplanned downtime starting the morning eastern time on 7/27/2025. I truly apologize for the downtime and for the work of processing in orders and support tickets that cropped up on your side during our downtime.

The quick bullets are:

1. This was not an attack, but a series of systems failures (electrical systems in the datacenter, followed by the HVAC systems, followed by the fail-over systems).

2. All data is available as it was the moment before the downtime happened. That means you can login to your LimeLM account and it's all there as it was.

3. All data was available encrypted-offsite during the downtime (so there was never a chance of losing your data).

4. While we didn't cause the failure, we're responsible for ensuring a failure like this doesn't happen for this length of time in the future (including more robust failover mechanisms).

---

Let me expand on the bullet points above. We had a day of unplanned downtime starting yesterday morning (Eastern U.S. time, "Boston time") going into this morning. During this downtime our services were unavailable. Unfortunately (and atypically for us) this also meant our mail servers were also down.

For LimeLM customers this downtime meant the following:

1. All web API calls (including things like generating product keys, changing custom license fields, etc.) would have timed-out (i.e. get an error and not be processed by us).

2. Any new customers with product keys that they haven't yet activated would not have been able to activate (they would have gotten an "Internet error", for example in C/C++ TA_E_INET)

3. Any customers attempting to move their product keys between machines (deactivate on an old machine and activate on a new machine) would not have been able to carry out this action.

To sum up: new customers and customers actively changing which machines their licenses were on would not have been able to activate / make that change during the downtime.

The good news is that existing customers that were already activated would not have been affected. Our design of TurboActivate, TurboFloat, and TurboFloat Server is such that it doesn't require constant connections with our activations servers (no one would want that!). So, if you're using our TurboActivate API as designed, existing customers that weren't actively moving their licenses were unaffected.

Data integrity and security

During this entire downtime we had up-to-date encrypted copies of the data offsite. Meaning the data was always available to us outside of this datacenter. So we had a "cold copy" of the data in our possession. We also had a warm backup (a server at another datacenter) with an identical copy of the data. The problem was our failover mechanisms were in the same datacenter that the "primary copy" was residing in.

So, while we had some of the infrastructure in place to handle the data-failover, some of our critical servers were in the failed datacenter. Which is unfortunate, and is a problem we're actively addressing going forward. This is the first time that this type of issue has bitten us.

Long story short: your data was never in danger. We work extremely hard to make sure that backups are accurate, up-to-date, and encrypted.

This downtime issue has been addressed, but we're investigating alternative failover methods to ensure downtime isn't this long again. This includes migrating to a more modern and well-equipped datacenter. We'll be researching and deploying these changes in the background during the coming months. These changes will happen without downtime.

This will be a significant capital and time expense but it will ensure this multi-hour downtime will be extremely unlikely to happen in the future.

Again, I'm truly sorry for the downtime.

— Wyatt O'Day
Founder & CEO of wyDay

Hello Everyone,

On August 1st, 2025 we're raising prices for all new customers and current customers of LimeLM. We're doing this to roughly match inflation and the weakened dollar since we last adjusted the prices.

Here are the new prices:

Plan name	Current price	New price
Max plan	$525 / month	$599 / month
Premium plan	$218 / month	$249 / month
Plus Plus plan	$145 / month	$165 / month
Plus plan	$71 / month	$81 / month
Basic plan	$41 / month	$47 / month
Solo plan	$15 / month	$17 / month
Free plan	Free forever	Free forever

We raise prices every couple years and post about it here on our blog. You can see past price changes by searching "price changes" in the blog search bar above. Also, don't hesitate to contact us if you have any questions.

We've done a ton of work in 2024. A lot of it was behind-the-scenes. In addition to putting the final touches on LicenseChest, here's a few broad things we've been working on:

1. Speed & security: Our servers respond quicker and handle larger loads (all while using less CPU and memory). This means we can serve more customers more quickly. For you this means snappier management of your licenses. For your customers this means even faster activations and verified trials.

   Speed of our servers is something we spend a lot of time and money on. Not only does it make things faster for your customers (activations and deactivations happening faster than the a blink of an eye) but it makes us able to handle larger amounts of customers and “frees up” server resources to handle other planned features.

   And this choice of solving speed with engineering refinements (rather than just throwing money at the problem in the form of newer and more servers) has the added benefit of getting more eyeballs on our code and developing better processes for verifying and securing our code.

   This is a long way of saying we’ve made our services significantly faster and more secure. And we’ll continue to pour a portion of our time and money into making things even faster and more secure.

2. Add TLS 1.3 support to curl on Windows: We've recently added TLS 1.3 support to curl on Windows. Curl is a popular command line tool for downloading files on every platform. We didn't create curl, but we spent the time and money to add TLS 1.3 support to Windows (SChannel specifically) because we (and many other companies) use the curl library to "talk" to the internet.

   So, not only will TurboActivate, TurboFloat, and the TurboFloat Server all support the faster and more secure TLS 1.3 standard, but other apps that use the curl library will get those benefits too.

   We've continued upon our initial contribution with additional refinements and bug fixes (working around Windows bugs, for instance).

   That's part of the beauty of open source: mutually beneficial self-interest.

3. Accessibility: We’ve made our forum software more keyboard and screen-reader accessible. This makes things better for everyone. Also, because our forum software (soon to be open sourced) shares components (both UI and backend) with the soon-to-be-released LicenseChest and refreshed LimeLM interfaces these accessibility changes will benefit all of our customers (and your customers too).

   Accessibility positively effects everyone whether you’re “fully able bodied” or you have any type of neuro-divergence or physical needs outside the “norm”. Our products aren’t perfect, and there’s always new work to be done, but this has been a focus of our company.

4. TA / TF / TFS 5.0 releases for Windows: We’ve released TurboActivate, TurboFloat, and TurboFloat Server 5.0 for Windows. We’ve released it early (before the Unix builds are finished) to work around broken network drivers that Intel and Qualcomm have been releasing lately. Get them now on your API page.

   We’ll release the Unix builds of TA/TF/TFS soon and we’ll have the updated changelog and blog post announcing it when it’s done.

End of 2024 and beginning of 2025 will bring even more behind the scenes progress (TLS 1.3 support for other Unix platforms, updated TA, TF, TFS builds, even faster server performance, etc.). Plus we'll actually release the updated LimeLM interface and LicenseChest.

We also have a couple projects that have been brewing that we think people will like. More about those in the coming months.

We’re very happy with what we’ve accomplished this year. While we always wish we could get more done, but we think we’ve had a good balance of features, speed improvements, and accessibility improvements this year.