The ecosystem provides a CLI for CI/CD automation and an SDK for tools to read and query inlang project files programmatically. This directly addresses the canonical job through an explicitly documented product workflow.
VerifiedChecked 2026-10-21
inlang (Fink, Sherlock, Paraglide JS)
Part of Opral
An open localization ecosystem centered on translation files kept in Git. Its tools share an inlang project model and include Paraglide JS, a JavaScript internationalization library; Sherlock, a VS Code extension; Fink, a GitHub-based translation editor; and a CI-oriented CLI.
Localization footprint
Where inlang (Fink, Sherlock, Paraglide JS) fits
Localization areas
Primary and supporting use cases
Job coverage
Selected jobs
PartialCatch i18n defects early ↗
Sherlock extracts strings and reports missing translations and configured message lint issues in the IDE. Its documented scope covers message defects rather than comprehensive pseudo-localization or layout testing. This directly addresses the canonical job within the stated component or workflow limits.
Configured plugins read and write the app's translation files, which can be committed and shipped through the team's existing Git workflow. This directly addresses the canonical job through an explicitly documented product workflow.
Paraglide JS is a compiler-based internationalization library that emits typed message functions; its documented usage includes locale-aware message handling. This directly addresses the canonical job through an explicitly documented product workflow.
The CLI can draft missing translations using a default third-party service or configured Google Cloud Translation or DeepL credentials; the default service has no stability guarantee and generated text needs review. This directly addresses the canonical job within the stated component or workflow limits.
PartialRun automated QA checks ↗
The CLI detects missing translations, variables, tags, plural/select forms and inconsistent messages, while Sherlock exposes message issues in the IDE. These checks cover structural resource errors rather than semantic translation quality. This directly addresses the canonical job within the stated component or workflow limits.
Fink edits locale plural forms side by side and checks missing variables and plural forms, with one-click fixes; the editor supports i18next, next-intl and Paraglide resources. This directly addresses the canonical job within the stated component or workflow limits.
Overview
What inlang (Fink, Sherlock, Paraglide JS) does
Inlang supports software localization through developer tools that work with files in a repository. Plugins connect its project model to translation file formats and frameworks. Fink edits GitHub-hosted translation files; Sherlock provides in-editor translation editing, extraction, and linting; Paraglide JS compiles locale-aware message functions; and the CLI runs checks and optional machine translation. The offering is an ecosystem of related tools, not one hosted translation-management service.
Buying context
Fit and constraints
- Best for
- Development teams that want localization files to remain in Git and want developer-facing tools for editing, compiling, and checking software translations. Fink currently supports GitHub repositories and i18next, next-intl, and Paraglide JS workflows.
- Relevant constraints
- The workflow depends on configuring an inlang project and compatible plugins for the relevant translation files or framework.
- Fink supports GitHub only; saving edits requires a free GitHub account, and private repository access requires installing the Inlang GitHub App.
- The official home page says CLI checks find project and message issues but do not judge translation quality; generated translations need review before shipping.
- CLI default machine translation uses a third-party service not operated or maintained by inlang, and its stability is not guaranteed; users can configure their own Google Cloud Translation or DeepL API key.
- Sherlock requires a Git repository and documented minimum versions of VS Code 1.84.0 and Node.js 18.
- Review status
- Reviewed 2026-10-21
Pricing
Plans and billing
Pricing has not been researched yet.
Reviews
Buyer reviews
No buyer review has passed editorial validation yet. Vendor testimonials are never converted into ratings.
Environment fit
Platform & integrations
How inlang (Fink, Sherlock, Paraglide JS) works with your other tools. Open a finding for its source and any plan or setup limits.
Integrations
Tools inlang (Fink, Sherlock, Paraglide JS) connects to.
We haven’t added integration details for this product yet.
Not yet recorded means we haven’t added a finding here. It doesn’t mean the feature is missing. We check these connections and settings separately from the work shown on the fit map.
Product references
LocManic's fit assessments are our editorial opinion. Check inlang (Fink, Sherlock, Paraglide JS)'s website for the latest features, plans and pricing.
Represent inlang (Fink, Sherlock, Paraglide JS)? Contact us to suggest an update, or claim this profile.
- Product website ↗paraglidejs.comCompany source
- App inlang ideExtension ↗inlang.com/m/r7kp499g/app-inlang-ideExtensionCompany source
- App inlang cli ↗inlang.com/m/2qj2w8pu/app-inlang-cliCompany source
- Product website ↗fink.inlang.comCompany source
- Product website ↗inlang.comCompany source