Easyling release notes February, 2026

February was a particularly productive month for us. Over the 4 new versions of Easyling, we released 25 different features and fixes. Many of those are new features added to the Dashboard 3.0 that I recently wrote about. There are many many many juicy details, so I definitely recommend you read the full article.

New features for the Dashboard 3.0

Eventually, our goal is to migrate every feature from the Dashboard 2.0 and sunset it. This month, we moved three options.

Alarm

Alarm allows you to be notified about events concerning the usage of your project. The usual three options familiar from the Dashboard 2.0 are also present. These allow you to monitor the usage when using the older, pay-as-you-go pricing model. On top of that, we added an option to warn about the word count as used for the newer, package-based pricing.

Notes

Project notes allow you to document important details of the project. It’s highly beneficial to have these notes available on the Dashboard 3.0 because otherwise it’s too easy to forget about them.

Audit log

The Audit log contains information about crucial events in the lifetime of the project. These options are now available regardless of which Dashboard you’re on. We added a few quality of life improvements too, like the option to search for specific event types and the sidebar not going over the main body.

OPTIONS requests in the proxy

According to the Mozilla Developer Network, “HTTP defines a set of request methods to indicate the purpose of the request and what is expected if the request is successful”. There are many kinds, but the most common are GET for getting data and POST for sending data to the server. A third type is OPTIONS requests which are most commonly used to check whether a cross-origin request can be made (e.g. can a request be made to example.com when the current page is easyling.com?). This month, we added support for this in the translation proxy.

Crest - better handle changes on the page while translations are loaded

This will get technical. I’m sorry, but we’re about to dive under the hood. Feel free to skip this section.

Crest works by first loading an initial set of translations which are the segments in the JavaScript-type export that we create. These translations are then applied for as much of the content as possible. It’s very likely that there are segments that can’t be translated in this round. These are gathered in a queue and then sent to our servers so that the translations can be received. However, that request to our servers is not immediate. It needs time for the data to be downloaded to the browser. The time it takes is usually measured in milliseconds, but the code of the original website can (and does) change the content during this time.

This month, we focused on this exact scenario. The upgraded version can now handle these changes. From the server response, it’ll take the translations for the segments that aren’t changed, while requesting the rest of them in the next round.

Improved Sales tool wizard

The Sales tool wizard is designed to quickly create demo sites as well as count the words on sites on your leads. This month, we added new features to the version on the Dashboard 3.0. While most of the features are identical to the old one, the most crucial upgrade is AI translation. Large language models can create more culturally relevant translations for your demo pages. The higher quality automated translation will provide a better first impression, which will result in better conversion.

Miscellaneous

There are a few smaller items as well.

• We added a link to the Dashboard 3.0 to the Dashboard 2.0, making it more discoverable.
• The way staging domains are handled for the Proxy and Crest are harmonised. Crest now matches the documented behaviour of the Proxy.
• For configuring Gemini, it is now possible to specify a custom endpoint. This way, the different versions of the API can be used.
• We improved the interface for ContentGuard by better surfacing the options for training it.
• ContentGuard can now function well even if there are no similar entries in the training dataset.
• All the supported AI engines are now available for ContentGuard.
• We added further options for testing Automatic Post Editing (APE) configurations while you’re tweaking the prompt.
• The publishing wizard allows you to pause the process and return to it later. This is now available for subdirectory publishing too.
• AI Translation can now send emails with links to the downloadable logs.
• We fixed an issue that crashed the Dashboard 3.0 for users who have a credit or debit card saved.
• We improved the placeholder text for the Page content override section.
• Previously, in some locations of the Dashboard 3.0, whether the site is Published wasn’t displayed consistently. We worked to ensure they are throughout the interface.
• We fixed a bug where wildcard options for excluding query settings would miss the * from the end.
• A bug was fixed where Automatic Post-Editing configuration was being unintentionally deleted