Inline on any page
GitHub readmes, vendor portals, intranet wikis — Krendo runs as a content script and shows the overlay next to your selection. The host page is unchanged; the overlay closes on outside-click.
For developers
Stop looking up Aufzeichnung four times a week.
Release notes from a Berlin vendor. SDK docs translated from Japanese. An RFC discussion in Mandarin. You don’t want to learn the language — you want to read the document without breaking your flow. Save the jargon once, get the inline gloss every time it shows up again.
Why it works for technical reading
Built like a tool, not a tutor.
The default mode for most language extensions is to ask for an account, push you into a streak, and try to monetize your vocabulary. Krendo is the opposite shape — quiet, local, optional. You can use it for six months without ever opening the companion dashboard if all you wanted was the inline gloss.
Captures the sentence and the URL
Every saved word remembers the page it came from. The next time you need to find that specific definition, the source link is one click away in your library.
Tag by vendor or project
Save a German term and tag it "vendor: berlin-co" or "project: payment-rewrite". Filter your library by tag later. The taxonomy is yours — Krendo doesn't prescribe one.
.apkg + CSV, no lock-in
Export to Anki when a new word should join your serious deck; export to CSV when you want it in a spreadsheet, a wiki, or a personal glossary. Your data is local and yours to take anywhere.
What’s under the hood
For people who want to know.
- Chrome MV3, plain Plasmo.No esoteric build pipeline. The content script mounts a shadow DOM so host-page styles can’t leak.
- Translation hits the public Google Translate endpoint.No API key, no logging on our side, no identifier attached. We acknowledge openly that this endpoint is undocumented — multi-engine support with BYO key (DeepL, OpenAI-compatible) is on the roadmap as the mitigation.
- Saved words live in IndexedDB via Dexie. The companion web app at
krendo.app/appreads from the same browser-local store via a cross-context bridge limited tokrendo.appas the only allowed origin. - Architectural decisions are versioned in the repo.Things like “no AI features in v1.x” or “the translate-save-review loop will not be paywalled” live as written ADRs, not as marketing copy that can change between blog posts.
A small concrete example
A week of reading German vendor docs.
Monday: you encounter Aufzeichnungin a release-notes article and save it (it means “recording” or “log” depending on context). Wednesday it shows up in a different article from the same vendor — Krendo auto-appends the new sentence to the same saved word, not a duplicate. Friday you skim a third doc and your eyes glide over the term because you now recognize it. The next time Krendo’s review queue surfaces it, you mark it stronger and move on. Three reads, zero typing, the word is yours.
Try it on the doc you have open.
Two minutes to install. Free. No account.