{"id":127,"date":"2026-11-14T17:45:13","date_gmt":"2026-11-14T17:45:13","guid":{"rendered":"https:\/\/docs.latw.ai\/uncategorized\/latw-cloud\/"},"modified":"2026-11-14T17:45:13","modified_gmt":"2026-11-14T17:45:13","slug":"latw-cloud","status":"publish","type":"post","link":"https:\/\/docs.latw.ai\/pl\/latw-for-wpml\/latw-cloud\/","title":{"rendered":"Translation Engine &#8211; LATW Cloud"},"content":{"rendered":"<p>With every other engine, translation happens on your own server: WP-Cron picks up the queue, your<br \/>\nserver calls the AI provider with your API key, and the result is written into WPML. LATW Cloud is an<br \/>\nengine that moves that work to LATW&#8217;s servers. You translate exactly as before &#8211; the same buttons,<br \/>\nthe same screens &#8211; but the translating, the retries and the waiting happen on LATW&#8217;s side, and the<br \/>\nresult is written back into WPML.<\/p>\n<p>What that buys you:<\/p>\n<ul>\n<li><strong>No WP-Cron and no timeouts.<\/strong> A job of a few thousand products runs in the background on LATW&#8217;s<br \/>\nside, retries on its own, and does not depend on visits to your site.<\/li>\n<li><strong>No API key needed.<\/strong> Translate with LATW Credits &#8211; included in a LATW plan or bought in packs &#8211;<br \/>\nor use your own OpenAI key in LATW Cloud if you prefer.<\/li>\n<li><strong>One dashboard for all your sites<\/strong>, with the cost of every job per site, language and model.<\/li>\n<\/ul>\n<h2>What you need before you start<\/h2>\n<ul>\n<li>A <strong>LATW account<\/strong> at <a href=\"https:\/\/app.latw.ai\/\">app.latw.ai<\/a>.<br \/>\nThe <strong>Free<\/strong> plan connects one site and translates with LATW Credits.<\/li>\n<li><strong>WPML<\/strong> with <strong>Translation Management<\/strong>, as for any other engine.<\/li>\n<li>A site <strong>LATW Cloud can reach from the internet over HTTPS<\/strong>. LATW Cloud calls your site to read<br \/>\nwhat needs translating and to write the translations, so a site on your own computer, or a staging<br \/>\nsite behind a password, cannot use it.<\/li>\n<\/ul>\n<h2>Switching to LATW Cloud<\/h2>\n<ol>\n<li>Go to <strong>AI Translator \u2192 Settings \u2192 General<\/strong> and choose <strong>LATW Cloud<\/strong> as the <strong>Engine<\/strong>.<\/li>\n<li>Click <strong>Connect with LATW<\/strong>. A LATW window opens; sign in if you are asked to.<\/li>\n<li>Check that the window names this site, then click <strong>Authorize<\/strong>.<\/li>\n<li>The window closes on its own once LATW Cloud has reached the site. The engine section now says<br \/>\n<strong>Connected<\/strong> and shows your plan, your LATW Credits balance, the model the site uses and its<br \/>\nrecent jobs.<\/li>\n<\/ol>\n<p>While the site is connected, LATW Cloud is its engine and the <strong>Engine<\/strong> setting is locked. To use<br \/>\nanother engine, click <strong>Disconnect<\/strong> first; the site then goes back to the engine it had before you<br \/>\nconnected.<\/p>\n<p>If your browser blocks the window, the section shows a link to open it instead.<\/p>\n<p>The <strong>model<\/strong>, <strong>LATW Credits or your own API key<\/strong>, the <strong>prompt<\/strong>, the <strong>glossary<\/strong>, the <strong>website<br \/>\ndescription<\/strong>, the <strong>budget limits<\/strong>, the <strong>target languages<\/strong>, the <strong>translation editor<\/strong> and what<br \/>\nhappens to <strong>outdated translations<\/strong> are set per site in LATW Cloud (<strong>Site settings in LATW Cloud<\/strong><br \/>\nopens them). While the site is connected, the plugin does not let you change them here:<\/p>\n<ul>\n<li><strong>Settings \u2192 General:<\/strong> Model, API key, Processing Mode, Reasoning Effort and Website Description<br \/>\ndisappear.<\/li>\n<li><strong>Settings \u2192 Translation:<\/strong> the Translation Prompt is replaced by a link to LATW Cloud, and the<br \/>\n<strong>Target Languages<\/strong> are the ones set in LATW Cloud, shown but not editable. When you connect, LATW<br \/>\nCloud starts from the languages you had chosen here; after that you change them in the site&#8217;s<br \/>\nsettings in LATW Cloud, and the plugin follows. Your own choice comes back if you disconnect. The<br \/>\nsame goes for the <strong>Translation Editor<\/strong> and <strong>Outdated Translations<\/strong> (PRO): shown as set in LATW<br \/>\nCloud (Site settings \u2192 Plugin), not editable here.<\/li>\n<li><strong>Glossary<\/strong> (PRO): the entries can&#8217;t be edited or imported; <strong>Export CSV<\/strong> still works, and LATW<br \/>\nCloud&#8217;s glossary imports that file as it is (terms in another source language than the glossary&#8217;s<br \/>\nare skipped). The entries are kept and apply again if you disconnect.<\/li>\n<li><strong>Settings \u2192 Automation<\/strong> (PRO): automatic translation is not available &#8211; see below.<\/li>\n<li><strong>Settings \u2192 MCP<\/strong> (PRO): the MCP server is off, so AI assistants can&#8217;t translate on the site past<br \/>\nLATW Cloud&#8217;s settings. Your MCP settings and token are kept and work again if you disconnect.<\/li>\n<li><strong>Settings \u2192 Advanced:<\/strong> Manual Check Responses is not used &#8211; nothing waits for WP-Cron. <strong>Send<br \/>\nOnly Text<\/strong> still applies: LATW Cloud reads the text of each field with placeholders instead of its<br \/>\nHTML, as described in <em>What Gets Translated?<\/em>, unless you turn it off.<\/li>\n<li><strong>Dashboard:<\/strong> Cost Statistics count only translations made on this server. LATW Cloud translations<br \/>\nare billed in LATW Cloud, and the History screen shows &#8220;LATW Cloud&#8221; in their Cost column.<\/li>\n<\/ul>\n<p>Each LATW plugin connects on its own. If the site also runs another LATW plugin &#8211; LATW for Loco<br \/>\nTranslate, for example &#8211; that plugin is a second site in LATW Cloud and counts towards your plan&#8217;s<br \/>\nsite limit.<\/p>\n<h2>Translating<\/h2>\n<p>Nothing changes in how you start a translation. Everything the plugin can translate goes through<br \/>\nLATW Cloud once it is the engine:<\/p>\n<ul>\n<li><strong>Posts, pages and products<\/strong> &#8211; the Translate button, bulk translation and <strong>Translate Again<\/strong> on<br \/>\nthe Translations screen.<\/li>\n<li><strong>Categories, tags and other terms<\/strong> &#8211; the Taxonomy Translation screen.<\/li>\n<li><strong>Strings<\/strong> &#8211; the String Translation screen.<\/li>\n<\/ul>\n<p>After you click Translate, the message says which LATW Cloud job the work became (&#8220;Sent to LATW Cloud<br \/>\nas job #1042&#8221;). The items show <strong>In LATW Cloud<\/strong> in the Active Translation Queue and on the<br \/>\nTaxonomy and String Translation screens, and <strong>Cancel<\/strong> works as for any other engine. When the translation is written back it<br \/>\nappears on the <strong>History<\/strong> screen like any other, at $0.00 &#8211; LATW Cloud bills it, not your own API<br \/>\nkey.<\/p>\n<p>What gets translated follows the same rules as with every engine: a missing translation is<br \/>\ntranslated in full, and an outdated one the way you set under <strong>AI Translator \u2192 Settings \u2192<br \/>\nTranslation \u2192 Outdated Translations<\/strong> (PRO; see <em>Updating Outdated Translations<\/em>). <strong>Translate Again<\/strong><br \/>\nalways translates the whole page.<\/p>\n<p>You can also start translations from LATW Cloud itself: open the site there, go to its <strong>Content<\/strong><br \/>\ntab, select posts, pages or products and click <strong>Translate<\/strong>. The same rules apply.<\/p>\n<h2>Automatic translation<\/h2>\n<p>Automatic translation after a save (PRO) is <strong>not available<\/strong> while the site is connected to LATW<br \/>\nCloud &#8211; it is coming to LATW Cloud in a later version. Nothing is translated on its own, and the<br \/>\n<code>latwaitrp_translate_post<\/code> \/ <code>latwaitrp_translate_post_now<\/code> developer actions do nothing. Your<br \/>\nAutomation settings are kept and apply again if you disconnect. To cap spending, set the <strong>budget<br \/>\nlimits<\/strong> in the site&#8217;s settings in LATW Cloud.<\/p>\n<h2>What is sent, and where<\/h2>\n<p>Nothing is sent until you connect the site. After that:<\/p>\n<ul>\n<li><strong>When you connect:<\/strong> the site address, its WPML languages, the plugin version and the email<br \/>\naddress of the administrator who clicked Connect.<\/li>\n<li><strong>When you translate:<\/strong> LATW Cloud is told which items and languages, then reads their text from<br \/>\nthe site and writes the translations back. For its Content tab it also lists your posts, pages and<br \/>\nproducts &#8211; titles, translation status, word counts. Every request between LATW Cloud and your site<br \/>\nis signed with a key only the two of them know; anything unsigned is refused.<\/li>\n<li><strong>On LATW&#8217;s side:<\/strong> the text goes to the AI provider of the model chosen for the site. LATW deletes<br \/>\nit 7 days after the job finishes; costs and job details are kept.<\/li>\n<\/ul>\n<p>Disconnecting stops all of this; the site then translates with the engine it had before you connected.<\/p>\n<h2>Limitations<\/h2>\n<ul>\n<li><strong>The address must stay the same.<\/strong> LATW Cloud does not follow redirects. If you move the site to<br \/>\nanother domain, switch between <code>www<\/code> and no <code>www<\/code>, or move from HTTP to HTTPS, connect it again.<\/li>\n<li><strong>Translations still waiting in the queue when you switch to LATW Cloud<\/strong> are not sent to it: they<br \/>\nfail with a note saying so. Start them again.<\/li>\n<li><strong>In LATW Cloud&#8217;s Content tab<\/strong> you see posts, pages and products. Terms and strings are translated<br \/>\nfrom this plugin&#8217;s screens.<\/li>\n<\/ul>\n<h2>When LATW Cloud cannot reach the site<\/h2>\n<p><strong>Test connection<\/strong> in the engine section asks LATW Cloud to call the site right now and tells you<br \/>\nwhat came back. The usual causes:<\/p>\n<ul>\n<li><strong>A firewall or security plugin<\/strong> (Wordfence, Cloudflare, your host&#8217;s WAF) blocks the requests.<br \/>\nAllow requests to <code>\/wp-json\/latw\/v1\/cloud\/<\/code>. LATW Cloud has no fixed IP addresses to allow, but<br \/>\nevery request it sends is signed, and the plugin refuses anything that is not.<\/li>\n<li><strong>The REST API is switched off<\/strong> or restricted to logged-in users. LATW Cloud needs it for the<br \/>\npath above.<\/li>\n<li><strong>Password protection<\/strong> (basic auth) on the whole site.<\/li>\n<li><strong>The server clock is wrong.<\/strong> Signed requests are valid for five minutes either side, so a clock<br \/>\nthat is off by more than that makes every request fail. LATW Cloud says by how much it is off.<\/li>\n<\/ul>\n<p>If LATW Cloud refuses a translation &#8211; not enough credits, no API key chosen for the site, a plan<br \/>\nlimit &#8211; the message after Translate says why, and the items are marked as failed with that reason.<\/p>\n<p><strong>&#8220;Connection lost&#8221;<\/strong> in the engine section means the site&#8217;s WordPress security keys changed &#8211; some<br \/>\nsecurity plugins regenerate them &#8211; and the stored connection can no longer be read. Click <strong>Connect<br \/>\nwith LATW<\/strong> again.<\/p>\n<h2>Disconnecting<\/h2>\n<p><strong>Disconnect<\/strong> in the engine section removes the connection from this site; LATW Cloud can no longer<br \/>\nread or write anything, and nothing can be translated until you connect again or choose another<br \/>\nengine. Translations already made stay on the site. To free the site in your plan, remove it in LATW<br \/>\nCloud as well &#8211; disconnecting it there also disconnects the plugin.<\/p>\n<h2>Developer reference<\/h2>\n<ul>\n<li>REST base: <code>\/wp-json\/latw\/v1\/cloud\/latw-ai-translator-for-wpml\/<\/code> &#8211; <code>POST<\/code> only, every route<br \/>\nsigned.<\/li>\n<li>To pair with another LATW panel (development, testing), put<br \/>\n<code>define('LATWAITR_CLOUD_URL', 'http:\/\/localhost:3000');<\/code> in <code>wp-config.php<\/code>, or use the<br \/>\n<code>latwaitr_cloud_url<\/code> filter.<\/li>\n<li>The engine id is <code>latw-cloud<\/code>. Rows translated by LATW Cloud carry that provider and the status<br \/>\n<code>cloud<\/code> while LATW Cloud works on them. They go through <code>latwaitr_translated_strings<\/code> and fire<br \/>\n<code>latwaitr_translation_saved<\/code> like any other translation.<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>With every other engine, translation happens on your own server: WP-Cron picks up the queue, your server calls the AI provider with your API key, and\u2026<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_latwm_translated_slug":"","footnotes":""},"categories":[3],"tags":[],"class_list":["post-127","post","type-post","status-publish","format-standard","hentry","category-latw-for-wpml"],"_links":{"self":[{"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/posts\/127","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/comments?post=127"}],"version-history":[{"count":2,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/posts\/127\/revisions"}],"predecessor-version":[{"id":223,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/posts\/127\/revisions\/223"}],"wp:attachment":[{"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/media?parent=127"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/categories?post=127"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/tags?post=127"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}