What is the Joshu Crowdin connection?

Joshu connects to Crowdin through OAuth and monitors the localization projects and string files you authorize. It tracks translation completion rates, uploads new source strings, surfaces translator questions, and connects localization readiness back to your release calendar and engineering tickets. You work with an assistant who has a desk, a computer, and persistent memory, not another dashboard you have to check manually before every release.

Is my Crowdin data secure?

Yes. Every Joshu runs in its own isolated, sandboxed cloud computer. Source files, translations, and localization glossaries Joshu reads stay in that private sandbox. Joshu only accesses projects you authorize, and your data is never used to train public AI models.

Will Joshu approve translations or change strings without asking?

Joshu monitors progress and drafts files by default. Approving translated strings, downloading language packs, or modifying source keys follows approval rules you configure, ensuring translation quality remains verified.

What can Joshu access in Crowdin?

Only the Crowdin projects and organizations granted during OAuth authentication. Joshu cannot view confidential localization projects in other enterprise accounts you do not connect.

What is the difference between Crowdin AI and Joshu?

Crowdin AI generates suggested translations for individual strings inside the editor. Joshu is an assistant with long-term memory across Crowdin, GitHub, Linear, Slack, and email. It coordinates source string updates with engineering releases and notifies you when key locales are ready for deployment.

Do I need a paid plan?

Joshu is $95 a month with a simple flat rate. That includes your sandboxed cloud computer, a dedicated US phone number, an @joshu.me email address, eight-level cortex memory, and all tool connectors, including Crowdin. There are no surprise usage tiers or seat markups.

Home ConnectConnect Joshu to Crowdin

Connect Joshu to Crowdin

Connect Crowdin so Joshu can monitor localization progress, sync updated source strings, and flag missing translations before release.

Crowdin

“Which languages in our app translation project are below ninety percent completion?”

Joshu checks the project translation progress bars, lists incomplete locales with remaining string counts, and drops a summary on your desk.

“Upload our new strings file to Crowdin and notify the German localization team.”

Joshu stages the file upload, drafts the translator notification, and holds the action for your approval before syncing.

“List all translation keys currently flagged with translator questions.”

Joshu scans open string discussions, compiles translator queries with their context, and formats a quick review sheet.

Localization projects, source strings, and translation progress in Crowdin connect directly to your release planning and sprint cycles.

What Joshu does

Joshu keeps track of your Crowdin projects to ensure internationalization stays on schedule. It monitors completion rates across target languages, flags untranslated strings before major feature launches, and pulls translator questions into your morning brief so developers can clarify context quickly.

What you do

Connect your Crowdin account with OAuth and select which localization projects Joshu may inspect. Decide whether source string uploads require confirmation on your desk before syncing to translators.

Why it sticks

Releasing software across multiple languages often creates bottlenecks when teams forget to check whether translations are complete. Joshu keeps an eye on translation progress in the background and alerts you well ahead of release day.

Permissions and limits

Joshu accesses Crowdin through official OAuth tokens. It reads project progress, lists file keys, and stages uploads according to authorized scopes. It cannot alter translations outside the permissions of the connected Crowdin user.

Frequently asked questions

: Joshu connects to Crowdin through OAuth and monitors the localization projects and string files you authorize. It tracks translation completion rates, uploads new source strings, surfaces translator questions, and connects localization readiness back to your release calendar and engineering tickets. You work with an assistant who has a desk, a computer, and persistent memory, not another dashboard you have to check manually before every release.
: Yes. Every Joshu runs in its own isolated, sandboxed cloud computer. Source files, translations, and localization glossaries Joshu reads stay in that private sandbox. Joshu only accesses projects you authorize, and your data is never used to train public AI models.
: Joshu monitors progress and drafts files by default. Approving translated strings, downloading language packs, or modifying source keys follows approval rules you configure, ensuring translation quality remains verified.
: Only the Crowdin projects and organizations granted during OAuth authentication. Joshu cannot view confidential localization projects in other enterprise accounts you do not connect.
: Crowdin AI generates suggested translations for individual strings inside the editor. Joshu is an assistant with long-term memory across Crowdin, GitHub, Linear, Slack, and email. It coordinates source string updates with engineering releases and notifies you when key locales are ready for deployment.
: Joshu is $95 a month with a simple flat rate. That includes your sandboxed cloud computer, a dedicated US phone number, an @joshu.me email address, eight-level cortex memory, and all tool connectors, including Crowdin. There are no surprise usage tiers or seat markups.