
Gleef
AI localisation platform for product teams. Gleef pairs a free Figma plugin, a web Studio and a developer CLI so designers, engineers and UX writers generate, review and ship context-aware translations without leaving their own tools.
What is Gleef?
Gleef is an AI localisation platform built for product teams rather than for translation agencies. It is published by Gleef SAS, a French company registered in Paris on 6 August 2024, and it groups four pieces under one brand: a Figma plugin, Gleef Studio (a web workspace at app.gleef.eu), the Gleef CLI (the open-source npm package @gleef/cli, MIT licensed), and a Chrome extension for A/B testing website wording.
The premise is that localisation breaks at the seams between roles, so the product addresses four named personas at once: product manager, designer, developer and UX writer. A designer selects text layers in Figma and gets translations generated, keys created according to the project's naming convention, and a live preview of how the copy sits in the frame. A developer runs the CLI, which detects JSON, XML, YAML and .strings files, respects .gitignore, and offers init, login, push, translate and pull commands that slot into a CI/CD pipeline. A reviewer opens the Studio and sees the Figma frame attached to each string, so the review happens with context and without needing a Figma licence. A content owner writes Rules, which the AI then applies across every language.
Two mechanisms carry the quality claim. Translation memory works by semantic matching over embeddings held in encrypted vector databases, so existing wording is reused rather than re-translated. Rules encode tone, formality and protected terms. The homepage claims 87% native-sounding translations and a fivefold faster workflow, with unlimited AI generations on all plans.
Named customers appear on the product pages with quotes: Alan, the French health insurer, Cellublue, an e-commerce brand selling across seven markets, and Wisear, a deep-tech company. The site claims 200+ companies on the homepage and 300+ on the Figma plugin page. Documentation covers all four products, and eight languages are named alongside a claim of more than 150 supported. Backers shown on the about page are Agoranov, Antler, Bpifrance and La French Tech.
What it does
- Generate context-aware AI translations from Figma, the CLI or the web Studio
- Create and manage localisation keys automatically, following the project's own naming conventions
- Preview translated copy inside the Figma frame to catch overflow and layout breaks before development
- Apply brand, tone and terminology rules to every language without anyone memorising the guidelines
- Reuse existing wording through semantic matching against the translation memory
- Review, approve and version translations in context, then publish or request changes
- Run A/B tests on live website copy through the Chrome extension and read the significance automatically
When to use Gleef / When not to
A quick filter to help you decide if Gleef is the right fit.
When to use Gleef
- Product managers who need releases to ship in every language on the same day as the source build
- Product designers working in Figma who want to see translated copy inside the mockup before hand-off
- Front-end and mobile developers who would rather run two CLI commands than shuttle locale files by hand
- UX writers and content designers who need brand and tone rules applied automatically across languages
- Small product teams and e-commerce operators localising interfaces or product sheets without a dedicated localisation department
When not to use Gleef
- Anyone looking for a mobile app: Gleef publishes none, on either the App Store or Google Play
- Solo users or occasional translators, since the only paid entry point is 145 EUR per month
- Teams that never touch Figma and want the free tier, which is the Figma plugin and nothing else
- Organisations that need a live connector to an existing TMS, as the Phrase, Lokalise, Crowdin and Transifex integrations are still documented as coming soon
- Buyers who require a named security certification, because Gleef publishes no standard, number or certifying body
How to use Gleef
A typical end-to-end flow, from setup to results.
- Create an account from app.gleef.eu/sign-up, which is free to start
- Install the Gleef plugin from the Figma Community if your team designs in Figma
- Select text layers in Figma, generate localisation keys and let the AI produce the translations
- Preview each language directly in the frame to spot overflow and layout problems early
- Define your brand and tone rules in the Studio so the AI applies them to every language
- Publish the strings to the Gleef ecosystem, or export the files if you only need the plugin
- Install the CLI with npm, then run gleef init to detect your locale files and write .gleef/config.json
- Authenticate with gleef login using your API key, then use gleef push, gleef translate and gleef pull
- Wire those commands into your CI/CD pipeline so translations follow every build
- For copy testing, install the Chrome extension and add the JavaScript snippet, with setup guides for Webflow, WordPress, Shopify, Wix, Bubble and Framer
Pros & Cons
Pros
- Covers the whole chain from design to review to code without switching tools
- The Figma plugin is permanently free, and AI generations are unlimited on every plan
- Migration is advertised as a five-minute job using two CLI commands
- Brand and tone rules are centralised and applied automatically instead of being memorised
- Reviewers can work in context without holding a Figma licence
- European posture is coherent: French publisher, EU-based servers, explicit no-training commitment, DPA on request and a named DPO
- The CLI is published openly on npm under the MIT licence
Cons
- No mobile app exists on either store, and none is claimed
- Only one price is public: 145 EUR per month, with everything above 30,000 translations quoted on request
- There is no legal notice page at all, and the registered office address never appears on the site
- The Customer Business Agreement declares its scope as the A/B testing Chrome extension, which narrows every contractual guarantee
- Security certifications are asserted in the terms without naming a standard, a number or a certifying body
- No subprocessor list is published, and the connectors to Phrase, Lokalise, Crowdin and Transifex are still marked as coming soon
- The site's own llms.txt advertises eight pages that do not exist, and the seventeen FAQ answers are never served in any HTML
Pricing & Plans
There is a permanent free plan: the Gleef Figma Plugin costs nothing and includes free AI translations, in-context preview, localisation key generation and file exports. The lowest paid entry point is 145 EUR per month for the Gleef Ecosystem tier, which covers workloads under 30,000 translations and adds Studio and CLI access, unlimited AI translations and unlimited brand guidelines. Beyond that volume, the Gleef Enterprise tier is priced on application. An annual commitment is advertised at 10% off. Fees are payable in euros, are non-cancellable and non-refundable except where the law requires otherwise, and subscriptions renew automatically. No free trial is advertised on the pricing page.
- Free - translate directly in Figma
- with free AI translations
- in-context instant preview
- localisation key generation and file exports
- 145 EUR per month - for fewer than 30
- 000 translations
- adding Gleef Studio and CLI access
- unlimited AI translations and unlimited brand and tone-of-voice guidelines
- described as great for small apps
- price on application - for more than 30
- 000 translations
- adding the full Gleef ecosystem
- translation API access
- custom integrations and a one-hour support response
- described as being for larger teams
- Annual billing is offered at 10% off the monthly rate
Data, GDPR & hosting
A consolidated view of how Gleef handles your data.
GDPR overview
GDPR treatment is stated in concrete terms. The privacy policy, effective 1 May 2024, sets out the categories collected, gives users rights of access, rectification and deletion, and names a Data Protection Officer reachable at dpo@gleef.eu who is described as ensuring GDPR compliance. The security documentation goes further: GDPR compliant processing and storage, data minimisation, privacy by design, regular privacy impact assessments, and a Data Processing Agreement available upon request. All data is declared to be processed and stored on EU-based servers. Gleef SAS is established in Paris, so no Article 27 representative is required and none is named. One caveat: the Customer Business Agreement declares its own scope as the A/B testing Chrome extension, so contractual guarantees read narrower than the product range.
Who owns the data?
The Customer Business Agreement keeps intellectual property with each side: Gleef reserves its own rights and takes only a limited right to use Customer Data in order to run the service. For the translation memory, the security documentation is explicit that embeddings are stored as vector representations rather than raw text, that they are accessible only by your company, and that they are neither shared nor used for any training. On termination, Gleef undertakes to delete Customer Data in its possession on the customer's written request, within a commercially reasonable time, unless the law requires it to be kept. Full export and selective deletion are offered at any point.
Reuse rights
Customers keep the working material they put into Gleef and can take it back out: the platform advertises full data export, selective key deletion and complete removal on request, and the CLI pulls translations straight back into the customer's own repository as ordinary JSON, XML, YAML or .strings files. Nothing in the published terms restricts what the customer then does with those translated strings inside its own product. On Gleef's side, use is bounded. The security documentation states that embeddings are not shared and are not used for any model training. The privacy policy separately describes anonymous usage and technical data, collected through Microsoft Clarity and Microsoft Advertising, that is used to analyse and improve the website; that instrumentation concerns the marketing site rather than the translation workspace.
Data retention & training
Hosting summary
Gleef states that all data is processed and stored on EU-based servers. No country and no hosting provider is named, so the declaration is regional rather than specific. Translation memory is not held as raw text: the documentation says embeddings are stored as vector representations in secure, encrypted vector databases, that access is controlled through authentication tokens, and that regular backups are taken for durability. Embeddings are described as accessible only by the customer's own company, and as neither shared nor used for any training. Access controls include end-to-end encryption, multi-factor authentication, single sign-on, role-based access, IP whitelisting and audit logging. No subprocessor list is published. Separately, the marketing website itself is served by Framer from a content delivery network, which says nothing about where the platform's data sits. Gleef SAS is established in Paris, so French and EU law applies, and the terms give jurisdiction to the courts of Paris.
Things to keep in mind
Risks and trade-offs to weigh before adopting Gleef.
- Machine output still reads as fluent when it is wrong: the in-context review exists precisely because unreviewed strings can ship a confident mistranslation into production
- Four different postal addresses circulate for this company, and the registered office in the French register appears on none of the site's pages
- The customer agreement states that it governs the A/B testing Chrome extension, so any contractual guarantee you rely on for the rest of the platform is on weaker ground
- The terms claim industry-standard security and privacy certifications without naming a standard, a number or a certifying body, and the security page names none either
- No subprocessor list is published, so you cannot see which third parties touch your strings before signing
- Automating the whole pipeline can quietly remove the human step: rules and translation memory make consistency cheap, and skipped review cheaper still
- The company was registered in August 2024 and is small, which is a normal risk for an early-stage supplier holding your product copy
Setup & Integrations
Technical difficulty
Low to moderate, depending on the entry point. The Figma plugin installs from the Figma Community and needs no technical skill. The Studio is a web application with nothing to install. The CLI requires npm and a terminal: gleef init detects your locale files and writes .gleef/config.json, then login, push, translate and pull do the work; Gleef advertises a five-minute migration using two commands, and documents CI/CD integration. The A/B testing extension needs the Chrome extension plus a JavaScript snippet on the site, with step-by-step guides for Webflow, WordPress, Shopify, Wix, Bubble and Framer.
Deployment
Integrations
Supported languages
Behind Gleef
Fundraising
Social
Resources
All the official URLs gathered for verification and reference.
Alternatives
Tools that compete with or complement Gleef.
Frequently asked questions
What does Gleef actually do?
How much does it cost?
Is there a free plan or a free trial?
Do I have to use Figma?
Which file formats and languages does it handle?
Is there an API?
Is there a mobile app?
Where is the data hosted, and is it used to train models?
What about GDPR and a data processing agreement?
Who publishes Gleef and how do I reach support?
Should you pick Gleef?
Gleef is a young but unusually coherent answer to a problem most teams solve with duct tape. Rather than being one more translation management system, it follows the string through the places it actually lives: the Figma frame where a designer writes it, the review screen where someone judges it in context, and the locale file a developer pulls into a build. That continuity, plus rules that encode tone once instead of asking everyone to remember it, is the real argument here.
The compliance posture will suit European buyers. The publisher is French, data is declared to sit on EU servers, the no-training commitment is unconditional rather than an opt-out, a DPA is offered on request and a DPO is named. The CLI being open source on npm under the MIT licence is a further signal of good faith.
The reservations are mostly about disclosure rather than capability. No security certification is named, no subprocessor list is published, there is no legal notice page, and the customer agreement declares a scope narrower than the product it is meant to govern. The connectors to the incumbent platforms are announced but not yet delivered. Only one price is public, and the 145 EUR monthly entry point puts the paid tiers out of reach for individuals.
For a product team already designing in Figma and shipping in several languages, the free plugin makes the evaluation cost close to zero, which is the sensible way in. Larger buyers should ask for the DPA, for the certifications the terms allude to, and for a written scope covering the whole platform rather than the A/B testing extension alone.
- Choosing a selection results in a full page refresh.
- Opens in a new window.