The name Alaio has started appearing on invoices, in app listings and in vendor documents where Bitrix24 (Alaio) used to stand alone — and the first reaction is usually "did we just switch products?". The short answer: no. Alaio is the brand under which the platform is distributed in international markets, the product behind it is the same portal. This article collects what is known, what actually changes for an administrator, and what needs no action at all.
Is Alaio a new product?
No. Alaio is a rebrand of the international distribution of the platform, rolled out gradually through 2025–2026, not a separate CRM. The legal entities behind it are Alaio, Inc. in the United States and Alaio Cloud Limited in Cyprus — the names you may already see on payment documents and in the app catalog. The software itself — CRM, tasks, drive, telephony, the workflow engine — continues as before, on the same infrastructure and with the same release cycle.
What changes for an existing portal?
Operationally, nothing that requires your attention. The portal address stays the same, logins and passwords keep working, data does not move, plans and their limits are unchanged. What does change is paperwork: the vendor name on invoices and contracts may read Alaio instead of the previous entity, and interface or marketing materials adopt the new brand step by step. If your finance team keeps a vendor registry, updating the record there is the whole migration.
Do Bitrix24 Market apps keep working?
Yes. Applications installed from Bitrix24 Market are tied to the portal and the REST API, not to the brand name, so nothing is reinstalled or re-purchased. You may notice first-party applications published under an "Alaio, inc" developer name in the catalog — that is the same rebrand, not a new vendor. Third-party apps, including the Roboteka robot catalog and field types, are unaffected: registrations, tokens and subscriptions carry over untouched.
Does automation change under Alaio?
No. Automation rules, the workflow designer, triggers and the REST API are part of the product, not the brand, so every process you built keeps running — the mechanics described in the automation rules guide and the workflow guide apply verbatim. Market robots installed in your processes continue executing under the same subscriptions. If you maintain internal documentation with product screenshots, expect cosmetic drift as branding updates land, and little else.
How should administrators prepare?
Three small things. First, tell finance and procurement that Alaio on a document is the same vendor, so payments are not flagged as unknown. Second, if your security policy whitelists sender domains or vendor names, add the new brand before a renewal notice lands in spam. Third — and this is the only genuine risk of any rebrand — stay alert for phishing that exploits the transition: a message claiming your portal "must be migrated to Alaio" with a login link is not how this works, because no migration exists. When in doubt, verify through the portal itself or official channels, not through links in mail.
Where to go from here
If you are settling processes on the platform anyway, this is a good moment to audit them: the automation examples collection shows what runs natively and what a Market robot adds, and the custom field types guide covers extending the CRM card itself. The platform under the new name rewards the same thing it always did — processes built inside it rather than around it.