Questions we get asked

No. Signing up creates a free workspace with a 14-day trial — one project, 100 keys and a single seat. Add a card only when you are ready to move to a paid plan.

Yes. Import Web JSON, iOS .strings and .stringsdict, or Android XML, and export the same formats back. Glotra sits between them rather than replacing them.

By invitation. Every account — including the first owner — is created without a password and gets an email link to set one, so nobody ever sets another person's password and no account can sign in before its address is proved.

The workspace locks until you pick a plan. Your projects, keys and translations are untouched and come straight back when you upgrade.

Every key records the platforms it belongs to, so an iOS export contains only the keys marked for iOS. You can also filter the key list by platform while you work.

No. The language is read from the filename or the folder around it, so en.json, en.lproj/Localizable.strings and values-fr/strings.xml all land in the right place as they are. Anything unrecognised is reported rather than silently dropped.

A zip laid out the way each platform expects it: lang/strings.json for web, lang.lproj/Localizable.strings plus .stringsdict for iOS, and values-lang/strings.xml for Android.

Yes. Plural forms are stored per language and exported in each platform's own syntax — .stringsdict on iOS, plurals elements on Android, and nested JSON on web.

No. AI drafting is optional and runs per key across about 30 languages — nothing is translated behind your back, and a suggestion only becomes a translation once someone saves it.

Yes. Every key keeps a per-language history with the previous text, who saved it, whether it came from a manual edit or an import, and when.

Admins and editors can edit; viewers read and export only. Grants narrow access further to specific projects, for one person or for a whole team.

Two separate things. At the organization level there is an owner (one per org, full control including billing), admins who can do everything except transfer ownership, and members. At the project level, a person is either a viewer or an editor.

Yes. A grant is either org-wide or scoped to a single project, and can go to a person or to a team. When someone qualifies through more than one grant, the most permissive one applies.

It depends on the plan — up to three seats on Explorer, five on Growth, and unlimited on Advanced. Invitations stop once you reach the cap.

Immediately, on their next request. Permissions are resolved fresh each time rather than baked into someone's session, so you never have to wait for them to sign out.

Your workspace goes read-only. You keep your plan, your projects and your keys, and reading, exporting and delivery to your apps all keep working — so a missed renewal never breaks something you have already shipped. Only changes pause until the payment goes through.

Cancelling stops the renewal; it does not take back the time you have paid for. You keep full access until the end of the current billing period, and the billing page shows you that date.

Yes. We email the organization owner seven days before each renewal, once per billing period. Cancelled subscriptions do not get one.

From the billing page, which opens the secure Stripe portal. Card details never touch Glotra.

Call the export endpoint with a project API key and you get back JSON keyed by language, with simple strings and plurals separated — so a copy change ships without a new build.

Revoke it from settings at any time, including while a payment is outstanding. Keys are shown once when created and only a hash is stored, so an existing key can never be displayed back to you — or to anyone else.

Yes. Glotra is an MCP server, so Claude, Cursor, VS Code and other MCP clients can list your projects, search keys, and add or edit keys while you work. Paste the server URL from Connected apps in your dashboard, sign in with your Glotra account, and approve what the app may do.

Only your project's base language. Glotra machine-translates the text into every other project language in the same step, and reports any language it couldn't fill so a translator can finish it.

No. A connection can never exceed your own role: a viewer stays read-only even if they approve editing. You also choose, per app, whether it may add and edit or delete keys (deleting is off by default) and which projects it can see.

Open Connected apps in the dashboard and click Disconnect; the app loses access on its very next request. Owners and admins can see and disconnect every member's apps from settings.

All of them, including the 14-day free trial. There is no extra charge for connecting AI tools.

Each organization is provisioned its own database for its projects, keys and translations, so no tenant shares storage with another. The accounts and permissions layer is separate again, with database-level row security as a second backstop.

Short-lived access tokens with rotating refresh tokens. Signing out revokes the token straight away rather than waiting for it to expire.