What's New?

Your go-to source for all BeLazy software release updates. Whether you’re tracking enhancements, checking compatibility, or planning your next integration.

Jun 2026

More automation with Plunet

BUSINESS MANAGEMENT SYSTEM

At BeLazy, our main aim is to enable fully automated projects from beginning to end, no matter the tool combination. Plunet AutomationManager contributes to this goal by allowing Plunet users to automatically select vendors and create integrated CAT projects, among other things. Up to now, if you deployed an automatic job as the first job in the workflow, BeLazy was not able to bundle multiple incoming pieces of work into this job – with this update now it can. If you have AutomationManager, enable this option under Manage my business management system in BeLazy.

Another functionality for Plunet users is that while BeLazy still detects deliveries in the connected systems, it will now only change the job status to Delivered if the current job status is earlier in the chain – so invoiced, not invoicable, etc. job types are not tampered with. This convenience feature does not need configuration.

May 2026

Into TMS: full localization lifecycle

TMSBUSINESS MANAGEMENT SYSTEMCUSTOMER PORTALSEMAILTECHIESTMSUSE CASE

From any content source, into a TMS, and back: the loop is closed

Into TMS now runs a project from any content source (a CMS, another TMS, an internal request portal, a vendor portal, an email, or a custom API call) through a complete, automated lifecycle

The source files are uploaded to a project created from a memoQ or Phrase TMS project template, prepared, and analysed. The analysis is transferred to a BMS project (Plunet, XTRF, Protemos, custom systems or just BeLazy’s own representation), and the systems stay in sync in both directions: vendor assignments made in the BMS are pushed into memoQ or Phrase, and a job closed in one system closes in the other. When the workflow finishes, the target file is exported from the TMS and uploaded back to the origin system, ready to publish.

Into TMS lets a single project ingestion API call manage everything a localization project needs: linguistic processing and operational tracking. That makes BeLazy the simplest framework for building TMS-neutral content integrations. Hours, not days, of development time. The same flow built on a generic orchestrator like n8n means wiring each step by hand. With Into TMS, you call one endpoint and BeLazy handles the rest, even if you change TMS or BMS. Your CMS integration is built once, no matter which TMS you or your vendors use. Your operational picture in the BMS stays consistent.

Into TMS also allows interoperability scenarios – automatically export XLIFF from one TMS, import it into another TMS, and at the end of each step, return the XLIFF into the original TMS.

Into TMS extends supercharges the Email Assistant as well: just push a project from the Email Assistant and everything gets analysed and created. Anybody receiving projects in emails can immediately feel the productivity boost.

Finally, Into TMS together with the other BeLazy APIs allows anyone to create customer portals in a quarter without worrying about the backend. Improve your relationship with your customers.

Are you using another TMS as your main TMS? Let us know and we’re happy to add other integrations – Phrase and memoQ are just the first two.

May 2026

See, Upload, and Download Localization Files Directly in BeLazy

EMAILFUNCTIONALITIESMANAGERS

Upload and download files directly from BeLazy’s user interface! In the past, BeLazy used to be API-only, moving files between systems silently. Now, if you allow BeLazy to store your files, every source file, every bilingual file at every workflow step, and every deliverable file is visible and downloadable from the BeLazy interface.

Most enterprise localization programs do not run a localization-specific BMS. They orchestrate vendors through internal tools, ticketing systems, or spreadsheets. With this release, BeLazy can serve as their complete operations layer:

Source files arriving from a CMS or a vendor system are stored and tracked inside BeLazy.
Bilingual files are downloadable at any workflow step for review, QA, or automated processing.
Deliverable files can be uploaded through the BeLazy UI. When the job is closed, BeLazy delivers those files automatically into the originating system (vendor portal, CMS, internal tool).

For an enterprise that wants one screen across many vendors and many TMSes, this turns BeLazy from an automation engine into an operations cockpit.

This functionality also enables small organizations who do not have a BMS to simply use BeLazy for all the portal and TMS-based jobs, and keep track of every continuous localization project automatically.

What’s more, the system even matches file counts and file names across workflow steps. If 79 source files went in and only 78 target files came back, the system flags it before delivery. Where a single release can ship hundreds of files across dozens of locales, this prevents the silent miss that creates project management overhead later.

May 2026

From Red Flags to Notifications: a Calmer Way to Manage Exceptions at Scale

FUNCTIONALITIESMANAGERS

Red flags used to be scary, right? We retired them. The new notification panel keeps you informed without making every issue feel like a fire.

Each notification card now shows when the issue last occurred. If a client’s system was unreachable two hours ago but not since, you can see at a glance that the regular synchronizations have already cleared it. Most notifications relate to system issues that BeLazy retries and resolves on its own. Humans are only needed if information is missing for the system: the connection password stopped working, the system does not know the username of a linguist in the other system, or has never seen a certain workflow and does not know which one to select in your systems, or the language does not appear in your business management system.

Notifications are now separated into four categories: actionables, errors, warnings, and information. At a glance, the team can tell what truly needs attention and what does not.

User feedback so far has been overwhelmingly positive. Exception management is a calmer, faster task than it was in the red-flag days, and managers spend less time investigating issues that BeLazy has already fixed itself.

May 2026

Google Sheet, the Swiss knife of project management

GOOGLE SHEETSBIBUSINESS MANAGEMENT SYSTEMMANAGERSTASK MANAGEMENTUSE CASEVENDOR PORTAL

A self-filling sheet that records every project and job

The Google Sheet project tracker is the Swiss army knife of project management. It is the visibility layer most enterprise localization programs are missing. It records and updates every project and every job that passes through BeLazy, automatically. Forget manual data entry and end-of-quarter reconciliation.

If you have Plunet, XTRF, Protemos, it helps you with visualizing and searching the data. If you don’t, you can use it as a simplified project management system.

Connect it to Looker Studio or Power BI in minutes for the leadership dashboards. Use AI coding tools to extend the tracker’s capabilities with simple Google App Scripts to automate vendor assignment, capacity planning and other decisions.

Using the IMPORTRANGE functionality of Google Sheets to base other sheets on the master sheet, you can give your customers a shared real-time overview of project progress, give your project managers customized project trackers with the information they like to see, give your vendors a way to self-claim jobs from a pool of jobs, and give your finance a real-time invoicing view.

NOTE: The Google Sheet project tracker is still in a closed beta. If you are interested in trying it, get in touch!

May 2026

Clone Connections and Create Workspaces from the BeLazy UI

APIIMPROVEMENTMANAGERSTMSVENDOR PORTAL

Adding a connection was a tedious, manual process even if you just wanted to change a small thing. Now you can clone any connection from the same Connections dialog. The cloned connection inherits both access data and configuration, then lives a separate life from the original. Useful when you want to add a near-duplicate account, or test a configuration change without touching the live one.

The Connections dialog also got a tab to create a workspace. Workspaces are the equivalents of connections when you wish to submit projects via an API.

The systems that submit via API are the ones enterprise localization teams care about:

CMS sources: Storyblok, Sanity, Contentful, Backstage, AEM, Sitecore.
Orchestrators: Make.com, n8n, Workato.
AI agents: Claude and custom assistants that route content into translation.
Internal request portals built on the BeLazy API.

From this release, you can:

Create workspaces from the UI.
Set their tags.
Delete them.

This release is also the first visible piece of a larger picture: BeLazy’s Content and Project hub. The hub is where every content source (CMS, TMS, PIM, knowledge bases, vendor portal, customer portal, orchestrator, AI agent, email, internal portal) will be managed in a uniform way.