# What happened to Waii after Salesforce bought it The room usually agrees that a plain-language question may now read the warehouse, because Salesforce bought the company that turns a sentence into SQL. That agreement is the problem: a question is not a grant. **Published:** 2026-08-13 **Canonical:** https://synconai.com/what-happened-to-waii **Author:** SynconAI Architecture Team ## In short Before a plain-language question is treated as access to the warehouse, settle what the 15 August 2025 close actually planned, which identity runs the SQL, what the 14 October 2025 rename changed, where a fee would appear, and whether anyone ordered a shutdown or a copy of every table. Waii turns plain language into SQL. Data Cloud is now Data 360. A question is not permission to read every table. ## Sources - **Salesforce Signs Definitive Agreement to Acquire Waii** (retrieved 2025-08-15) https://www.salesforce.com/news/stories/salesforce-signs-definitive-agreement-to-acquire-waii/ > Salesforce completed its acquisition of Waii on August 15, 2025. - **About Salesforce Data 360** (retrieved 2025-10-14) https://help.salesforce.com/s/articleView?id=data.c360_a_data_cloud.htm&type=5 > As of October 14, 2025, Data Cloud has been rebranded to Data 360. ## What to take away - Decide whether 15 August 2025 is being used as a completion of a planned path into Data Cloud, or as proof that a natural-language box is already installed in the tenant. - Decide which named identity runs the SQL, because a courteous question does not narrow a broad role and does not open a table that identity cannot read. - Decide to put Data 360 on new work and leave Data Cloud as the historical label, because the 14 October 2025 rename did not move tables or widen a grant. - Decide that any fee sits on the order form, and refuse a sunset or a full warehouse copy that the cited pages do not describe. ## The guide An analyst hears that Salesforce bought a company which turns a sentence into SQL, and the room agrees that any colleague may now question the warehouse. The sentence the analyst wants to ask is a business question, not a request to bypass a control. The warehouse will still treat the result as a query. That is the distinction that matters. A plain-language question is a way to ask. SQL is a way to read. The right to read sits on the identity that runs the statement, and the acquisition does not replace that identity with anyone who can type. The completion sentence is the one to read before the agreement hardens: "Salesforce completed its acquisition of Waii on August 15, 2025." The deal is done. Waii turns plain language into SQL. Salesforce planned to integrate that work into Data Cloud. Planned is not the same word as installed. A second sentence, from Salesforce help text, belongs on the same page of the brief and is not a Waii shutdown: "As of October 14, 2025, Data Cloud has been rebranded to Data 360." The rename changes a label. It does not add a table, remove a grant, or decide that a question is allowed. What follows separates a finished acquisition, and a renamed product, from a decision about which tables a sentence may touch. A general answer becomes a connection string later, offered as if a password were a catalogue. | Question | Who has to answer it | What a bad answer usually means | | --- | --- | --- | | What did the 15 August 2025 close actually plan | The person briefing the analysts, from the completion sentence | Planned integration is being briefed as a box already installed in the tenant | | Which identity is allowed to run the SQL | Whoever owns the warehouse role, by name | A courteous question is treated as permission to read every table | | What did 14 October 2025 change, and what did it leave | Whoever labels the diagram and the statement of work | The Data 360 rename is treated as a data load or a wider grant | | Where a price or a fee would have to appear | Procurement, with the order form in the room | A remembered number, or a free trial, is written into the brief | | Is there a shutdown, or an order to copy the warehouse | Whoever is proposing to load every table into Salesforce | A rename is used as a sunset, or a copy is treated as the design | ## What did the 15 August 2025 close actually plan? The question is not whether Salesforce bought Waii. It did. The question is what "planned" is allowed to mean in a tenant that already has a warehouse, a CRM, and a habit of treating a demonstration as the design. The useful reading is narrow. A person may, in time, ask in ordinary language and receive SQL, or the result of SQL, on a path Salesforce planned to reach through Data Cloud. Which tables that path may see is a later decision. The close only stops the claim that the question is the permission. **A good answer sounds like** the completion sentence dated 15 August 2025, the phrase "planned to integrate that work into Data Cloud" kept as a plan, and a named person who will not tell an analyst that the tenant gained a natural-language box on the day of the close. The order form is what says whether anything was bought. The completion sentence is a fact about the companies. **A bad answer sounds like** the warehouse is open now, because Salesforce owns the company that writes SQL. Owning the company is not a grant on the warehouse. Salesforce can own a product that writes SQL and still have no right, through that ownership, to read a table the data team closed. The right to read sits on a user, a role, or a service account. The acquisition does not replace that identity with "anyone who can type a sentence". Why Salesforce acquired Waii is only as large as the cited page. The page says what Waii does, and that the work was planned for Data Cloud. It does not publish a board minute or a founder letter. Do not add a motive so a case study has a second paragraph. Why Waii sold is the same gap from the other side. The seller's reason is not here, and a profile is not a source for it. Customers feel the impact in one place: a polite sentence can become a query. That is a change in how a question is asked, not a change in who may see a row. If a briefing says the acquisition opened the warehouse, send it back. The warehouse stays closed except where a grant is written down. ## Which identity is allowed to run the SQL? A question is not permission to read every table. Plain language is a way to ask. SQL is a way to read. If the identity that runs the SQL can select from a table, a well formed question can return those rows. If the table was meant to stay closed, the politeness of the sentence will not close it. The grant will. This is the line people skip because the interface is courteous. The analyst did not ask to bypass a control. They asked a reasonable business question. The tool did what it was built to do. The failure, when it happens, is upstream of the sentence. A broad role was chosen so a demonstration would return rows, and it was left in place after the demonstration became the way the business reads data. Natural language also hides which tables were used. A statement can be reviewed. A sentence cannot, unless the SQL is kept beside the answer. That practice is part of the design, not part of the acquisition story. The decision in the room is smaller, and it comes first: refuse the claim that any colleague may ask anything. **A good answer sounds like** a named role, dated to a review rather than to the close, with the tables it may read written down, and the SQL kept beside any answer a sentence produced. The person who owns the role can say which demonstration grant was removed when the demonstration ended. **A bad answer sounds like** anyone who can ask a sensible question should see the row, because the question is only asking. Sensible is not a grant. A connection string proves someone once had a password. It does not prove the table is one finance still trusts. If a proposal titles itself a Waii data migration before anyone has said whether saved questions even exist, the title is ahead of the inventory. Do not copy the warehouse into Salesforce so a sentence can see it. The planned path was into Data Cloud, now Data 360. A load of every table into CRM objects is a different programme, and it is not what the close describes. ## What did 14 October 2025 change, and what did it leave? The acquisition date is 15 August 2025. The vendor writes August 15, 2025. Same day. Do not invent an earlier signing date and treat it as the close. This source gives the completion. The rename is a different day and a different document. Data Cloud was renamed Data 360 on 14 October 2025. Put the current name on the diagram, in the statement of work, and in the briefing given to a new analyst. The rename does not add a table, remove a grant, or decide that a question is allowed. Do not blur the two days. Waii closed on 15 August 2025, while the product was still being described as Data Cloud. The rename landed on 14 October 2025. A design written between those dates can be right about the intent and wrong about the label. Update the label. Re-read the grants. They do not update themselves because the product changed its name. Between the August close and the October rename, people wrote Data Cloud on purpose. Those documents are history. They are the wrong label for work that starts now. Change the label, then re-check the role. A renamed box with the old admin connection is still the old grant. **A good answer sounds like** two lines only. Completion: 15 August 2025. Data Cloud renamed Data 360: 14 October 2025. The person who owns the diagram can say which documents are historical labels and which grants were re-read after the name changed. There is no third line for a cutover of schemas. **A bad answer sounds like** 14 October 2025 is the day every dataset moved, or the day Waii was switched off. Nothing in the help sentence says the data moved. It says the name changed. The rename is not a migration of Tableau, of a warehouse, or of a CRM. Teams that treat the day as a load have misread a label change. A timeline that adds a schema cutover is a drawing. Ask which sentence it comes from. The sentences you have are the completion and the rename. A feature date needs a sentence you can point to. You do not have one here. ## Where a price or a fee would have to appear The pages cited here do not publish a purchase price or a licence fee. How much Salesforce paid for Waii, how much Waii was sold for, and the acquisition price are the same unanswered search. A remembered number is a second source. There is no Waii licence fee in this record. Company ownership is not a price list. A free trial is not in the completion notice. Do not tell a colleague the close included a trial. If a commercial offer exists, it is on a page that is not the source for this decision, or it is on the order form. **A good answer sounds like** procurement, with the order form, stating that the cited pages publish no purchase price and no licence fee, and that a fee this organisation pays is a contractual line or it is not established. Finance receives that admission, not a clip. **A bad answer sounds like** a spend figure from a short video, used because the close felt expensive and the room wanted a number. Spending, in a clip, is the same request wearing a different title. A DVD, a Reddit thread, a YouTube video, a TikTok, a course, a book, or a certification is not a source for the date, the price, or a shutdown. A founder profile and a later job advert are not a grant and not a price. Impact on customers is not a discount and not a new invoice line inferred from the close. The impact that can be defended is the plan to put plain language in front of SQL, aimed at what was then called Data Cloud and is now called Data 360. Any fee is contractual. A briefing that adds a fee has left the record. A case study, a demo, and a roadmap with feature dates are not in the cited pages. The dates that may be written down are 15 August 2025 and 14 October 2025. ## Is there a shutdown, or an order to copy the warehouse? There is no end date for Waii in the cited pages. Do not invent a sunset because the surrounding product changed its name. Data 360 is a rename of Data Cloud. It is not a notice that Waii was switched off, and it is not a notice that every older label must be deleted from history. History can keep the old name. Work that starts now should use the current one. A judgement that the product declined after the acquisition is not something a close notice can score. The notice is not a usage chart. Quiet, in a community or a changelog that was not cited, is not a shutdown. If a Waii tenant was held before the close, the people who hold the login can say whether it still opens. The announcement cannot. "Users forced to Salesforce" overstates a completion. Nobody on this source is ordered to copy the warehouse into Salesforce so a sentence can see it. Copying the warehouse is the wrong project. Naming the tables a question may use is the project. Forced migration is a story. It is not a sentence in the notice. **A good answer sounds like** no end date, the rename described as a label, and a refusal to load every table into CRM objects. The person proposing the work can say whether saved questions even exist before the word migration is used. Worth is not scored. The company was bought, the path was planned, the name of the destination changed in October 2025, and a question is still not a grant. **A bad answer sounds like** the product was retired on 14 October 2025, so the warehouse should be copied in before the old name disappears. That sentence joins two events the sources keep apart. The rename is not a shutdown. The close is not an instruction to duplicate tables. A courteous sentence does not make a broad role narrow, and the Data 360 name does not widen it. :::warn A question is not permission to read every table. The question becomes SQL. The SQL runs with a grant. A courteous sentence does not make a broad role narrow, and the Data 360 rename does not widen it. ::: ## What to do with the answers Read the five together. Specific answers mean the room can tell a planned path from an installed box, and a rename from a load. General answers mean the decision rests on a shared feeling that a polite question is the same thing as access, which the close does not say. Which tables the path may use, which role runs the SQL, and which questions must return nothing are set out in [Waii, plain-language SQL, and the Data 360 rename](/waii-data-360). Bring a catalogue to that conversation. A blank catalogue means the work is earlier than a quote. The close does not fill the blank. ## Questions ### What happened to Waii after Salesforce acquired it? Salesforce completed the acquisition on 15 August 2025. Waii turns plain language into SQL, and Salesforce planned to integrate that work into Data Cloud. Planned is not the same as installed in a tenant. On 14 October 2025 Data Cloud was renamed Data 360. The cited pages do not give Waii an end date. ### Does a plain-language question read every table? No. A question is not permission to read every table. The question becomes SQL, and the SQL runs as an identity: a user, a role, or a service account. If a demonstration role can read every schema, the demonstration is the defect. The Data 360 name does not narrow that role. ### When did Salesforce acquire Waii, and when was Data Cloud renamed? The close is 15 August 2025, written by the vendor as August 15, 2025. Data Cloud was renamed Data 360 on 14 October 2025. Documents written between those dates that say Data Cloud are history. They are the wrong label for work that starts now. The rename is not a schema cutover. ### How much did Salesforce pay for Waii? The cited pages do not publish a purchase price or a licence fee. A free trial is not in the completion notice. Do not supply a number from memory or from a clip. A fee, if this organisation has one, is on the order form. ### Should the warehouse be copied into Salesforce so a sentence can see it? No. The planned path was into Data Cloud, now Data 360. A load of every table into CRM objects is a different programme, and the close does not describe it. The rename on 14 October 2025 is a label change. It is not an order to copy data and not a Waii shutdown. --- SynconAI is a Salesforce Select Partner and an OpenAI Select Partner, delivering architect-led Salesforce and AI programmes across the United States and Australia. Related service: Data 360 (https://synconai.com/salesforce-data-360-services.html).