Q&A

Soluling is a localization platform for software, documents, and data. It scans your source files, gives translators a dedicated grid to work in - with AI, machine translation, translation memory, terminology, and spell checking to help them - and builds ready-to- deploy localized output. It covers everything from scanning to building, not just translation.

Three things in particular.

First, Soluling supports two ways of working. In one, like most other localization platforms, you push your files to the cloud, they're translated there, and you pull the localized files back to use them. In the other, you use SoluMake to scan and build locally, and only the strings and their metadata are pushed to the cloud - your files themselves never leave your infrastructure.

Second, Soluling supports 100+ file and database formats, including complex ones most cloud localization platforms don't touch at all, such as compiled EXEs and DLLs, Visual Studio projects, and databases - not just simple text-based formats like JSON and XML.

Third, Desktop and Cloud aren't separate products bolted together - they're the same platform, so you can scan and build locally with Desktop or SoluMake while translators work in the Cloud web app, moving between the two as a project needs rather than being locked into one or the other.

Desktop is the Windows application you install; Cloud is the same platform accessed through your browser, the REST API, or SoluCLI (a thin command-line wrapper around that API) - nothing to install for the browser or a raw API call, just an npm package if you'd rather use a CLI. Cloud covers almost everything Desktop does.

No. Soluling Cloud's web app runs entirely in the browser, and it signs you in automatically using your existing session on this site. Installing anything is only needed if you want the full desktop experience, the SoluMake command-line tool for local build automation, or SoluCLI to drive the cloud from a CI/CD pipeline.

Desktop application platforms include .NET, .NET Framework, WPF, Windows Forms, Visual C++, Delphi, and Qt. Web platforms include ASP.NET Core, ASP.NET Framework, Blazor, Angular, React, Vue, Django, Go, Ruby on Rails, PHP, Java, and Magento. Mobile platforms include Android, iOS, UWP, Xamarin, and Delphi FireMonkey. Supported file formats include resource formats such as ResX, XAML, XML, JSON, YAML, INI, GetText/PO, TS, and RC; document formats such as Markdown, HTML, SVG, Word, Excel, PowerPoint, DITA, Help & Manual, and LaTeX; databases including SQL Server, MySQL, PostgreSQL, SQLite, Access, InterBase, and Firebird; and other formats such as TMX, SalesForce, SubRip, and WebVTT - and more beyond that list. See the full list of supported formats for details.

Yes. Most cloud localization platforms are built around simple, text-based formats like JSON and XML. Soluling also scans and builds compiled binaries directly, and produces ready-to-deploy localized output such as .NET satellite assembly files - not just translated copies of your source files that still need a build step of their own.

Use Soluling Desktop or the SoluMake command-line tool to scan your project and create a Soluling project file (.ntp). Push that file to the cloud so translators can work on it there; once translation is done, pull the translated project file back down and build it locally - on your development machine, a build server, or a CI/CD pipeline. Your source code and compiled binaries themselves never have to leave your own infrastructure.

Yes. Soluling scans Visual Studio solutions (.sln/.slnx) and projects (.csproj/.vbproj) directly and understands the software project structure inside them, so you don't have to hunt down and select individual resource files by hand.

Yes. Soluling can import your existing translations, so switching from another localization tool doesn't mean starting from scratch.

Yes. Machine translation suggestions appear as you type, from whichever engine your project is configured to use.

Amazon, Azure, DeepL, Google, and LLMs - configurable per project, so different projects (or different teams) can use whichever engine suits them best.

Yes. Translation memory reuses translations from previous work so your team never translates the same sentence twice - built into both Desktop and Cloud.

Yes. Soluling highlights words that exist in your termbase as you translate, with stemming so different word forms still match, and lets you click a highlighted word to see and insert its approved translation - keeping terminology consistent across a whole project.

Yes. Translations are checked against built-in dictionaries for each language, plus per-project custom dictionaries for terms that aren't in a standard dictionary.

Yes. AI-powered validation finds errors as you type - and can even fix them - both interactively and in batch, in the desktop application or through Cloud.

Yes, a few ways: the SoluMake command-line tool on a Windows build server scans, machine-translates, imports/exports, and builds locally, without opening the desktop application. From any platform, the REST API directly or SoluCLI (a thin command-line wrapper around it) does the same job differently - you push your files to the cloud, which does that work there instead.

SoluMake is Soluling's command-line tool for build automation. Run it from a makefile, batch file, or CI/CD pipeline to scan sources, machine-translate, import and export files, and build localized output. It's not a thin CLI that just talks to the cloud and pushes files there - scanning and building are real local work SoluMake performs itself, the same engine the desktop application uses. It ships with every build automation installation, and it's the same tool this site's own servers use to build the localized artifacts published for each project.

SoluCLI is Soluling's cross-platform command-line tool for CI/CD pipelines - install it from npm and use it to push the resource files you want localized into a cloud project, trigger a build, and pull the localized files back. Unlike SoluMake, it doesn't scan or build anything itself - it's a thin wrapper around the REST API, so the cloud does that work instead. It runs anywhere Node.js does: Windows, Linux, and macOS.

No. The web pages and the REST API cover the same project management and translation tasks without installing anything on your build server, and SoluCLI wraps that same API in an npm-installable command-line tool if you'd rather not write the HTTP calls yourself. Using SoluMake instead gives you one advantage none of those have: your files never leave your build server - SoluMake scans and builds locally, sending only strings to the cloud, while the REST API and SoluCLI both push your files there.

No, SoluMake is Windows-only. If your build server or DevOps pipeline runs on Linux (or any other non-Windows platform), use the REST API directly, or SoluCLI to drive it from the command line without writing the HTTP calls yourself - either way, you push the resource files to be translated to the Soluling cloud, which scans them there, and you get the built localized files back once they're ready.

They take opposite approaches to the same job. SoluMake runs on your own machine and works entirely locally against a .ntp project file - it scans, machine-translates, and builds there, and only the extracted strings and their translations ever reach Soluling's servers. SoluCLI instead talks only to the REST API - it doesn't scan or build anything itself, it pushes files up and lets the cloud do that work, then pulls the results back down. Pick SoluMake to keep source files off the cloud entirely on a Windows build agent; pick SoluCLI when you're fine with the cloud doing the work, or your build agent runs Linux or macOS, where SoluMake isn't an option.

With JWT access tokens: sign in with POST /users/authenticate and renew with POST /users/refresh. Once signed in, the API covers project management, terminology, translation memory, spell checking, machine translation, project invitations, and licensing - see the full API reference, generated directly from the API so it's always up to date.

No - Soluling never asks for access to your repository, whichever way you use it. With SoluMake, scanning and building both happen locally, on your own build server or development machine, so your source code never has to leave your infrastructure at all. Using the REST API directly works differently: you're the one who pushes the files you want translated to the Soluling cloud for it to scan - but that's still you handing over files you chose, not Soluling reaching into your repository.

With SoluMake, only the extracted strings and their translations - not your source files. Most cloud localization platforms sync your whole repository into their cloud through a repository integration or CLI push and process it there; Soluling's SoluMake gives you the option to keep that step local instead. If you don't use SoluMake or Desktop, you push the file to be scanned to the Soluling cloud yourself instead - but you're still the one deciding what to send, not Soluling reaching into your repository on its own.

Soluling Cloud runs on Microsoft Azure, in the West Europe region.

Translate is a standalone, browser-based version of Soluling's translation grid - the same editing experience as the desktop application, with nothing to install. It's also where you view and edit glossaries and translation memory, not just individual projects.

No. Translate signs you in automatically using your existing session on this site, so there's nothing extra to log into.

Most of them. Spell checking, machine translation, translation memory, and terminology support are all available in the cloud. A few other features are still desktop-only, and we're actively closing that gap — with one exception: the visual editors will remain desktop-only. If you need visual context for your cloud translations, you can attach screenshots.

Yes. Soluling Cloud keeps projects centralized, so multiple translators can work on the same project at the same time instead of waiting on packages sent back and forth.

Dashboard is where you create and manage your Soluling Cloud projects from a browser - creating and configuring projects, adding languages, managing files, and inviting and managing team members, all without installing anything.

OTA delivery pushes finished translations straight to your running applications, without a redeploy - so a translation fix or a newly added language can reach your users without shipping a new build.

Yes, for both. Every Cloud plan starts with a 14-day free trial - your card is saved when you sign up but isn't charged until the trial ends. There is also a tier that is always free. Desktop editions can also be evaluated for free for 30 days after installation with the full feature set, no card required.

Whichever you prefer: choose monthly billing, or switch to annual billing and pay for 10 months instead of 12—giving you 2 months free. Annual billing unlocks your machine translation and AI credits for the entire year at once.

Those features will stop working until your next billing cycle begins or you purchase additional credits.

Yes, anytime, right from Your Accounts. You keep access until the end of whatever you already paid for (or, if you're still in the trial, until the trial ends) - cancelling doesn't cut access off immediately.

Where applicable, yes — tax is calculated from your billing country during sign-up and shown in the order summary before you subscribe, so there are no surprises on your invoice. If you provide a valid VAT ID, EU VAT is not charged to customers outside Finland.

On the Pricing page, which lists every plan's limits and features side by side and lets you toggle between monthly and annual pricing.