For the person behind the platform
Ask a Docebo admin what they do and watch them hesitate.
The honest answer is a list, and every item on it is your job. d4o takes one thing off that list properly — and starts keeping the record you have been keeping by hand.
Free tier at launch. No card, no demo call, no countdown.
| Key | Source text | Modules | Status |
|---|---|---|---|
Description | 6 | Translated | |
| Untranslated | |||
| Translated | |||
| Untranslated | |||
| Untranslated |
Design preview, not a screenshot. d4o is in development — the counts shown are real figures from a live Docebo instance, and the unlabelled rows carry no invented data at all.
The job
This week you are the instructional designer, the QA team, the brand police, the reporting analyst, the integrations owner, the support rep, and the one who gets a Slack message at 4:50 on a Friday that opens with quick question.
None of that is in your job title. All of it is your job. Underneath the list is the part nobody sees at all: you own the system. Every naming decision. Every branch, group, and catalog assignment. Every permission that determines who sees what.
d4o is being built for that whole surface. We are starting with one corner of it, in public: localization — where the gap between what Docebo can do and what you can manage is widest, and where the fix is provable.
Building now — Localization & key usage
Why we start with localization
The surface area nobody budgets for
- 27,273translatable keys in English
- 280modules they scatter across
- 53languages Docebo supports
- 999keys living in more than one module
English alone. Measured against a live Docebo instance, August 2026.
What you get
Three things you can’t find in Docebo.
Localization view
Filter for what you have actually touched
Search, filter, edit, and track status across the whole string set. Docebo gives you a paginated table and a search box. d4o is what you wish the localization tool could be.
Key usage lookup
See where a key lives before you change it
Look up a key and see every page it appears on. The same text sits in more than one module more often than you would guess. With d4o, find that out before you save rather than after.
Record of change
Know who changed it, and why
Docebo’s localization tool keeps no history — no edit date, no author, no reason. d4o keeps all three, every time an edit is saved.
Key usage lookup
You translate a single key. How many places do you think that changed?
The same words turn up all over the platform. Descriptionis one key string, and it appears in six separate modules. There are 999 key strings in your instance like that — the same text, sitting in more than one place, with nothing in Docebo to tell you where.
Look it up first, and the question stops being a surprise.
DescriptionAppears in 6 modules
Module names withheld — design preview.
Where this goes
Localization is step one, not the whole vision.
Localization is what we are building now. The roadmap past it runs through relationship mapping, audit intelligence, translation packs, and governance across the rest of the platform — the other jobs on that list at the top of this page. Solving the sharpest version first is how you earn the right to solve the rest.
We’re not building a feature Docebo forgot. We’re building the system of record for work that has never had one — and making a case, product by product, that the people quietly holding these platforms together deserve software built for them by name.
- Localization & key usagebuilding now
- Relationship mappingon the roadmap
- Audit intelligenceon the roadmap
- Translation packson the roadmap
- Governance across the platformon the roadmap
Who’s building this
d4o is what I wish I’d had.
Adam Ballhaussen has spent over a decade building customer education programs — at nCino and Docebo, through two IPOs, and now at Varicent. He led customer education at Docebo and founded its 10,000-member community. After years of hand-maintaining spreadsheets to track what he’d changed in the platform, he started building d4o. He’s an educator and a marketer, not an engineer.
What qualifies me here isn’t the code. It’s ten years of running into this exact wall and writing down where it hurt.
Somebody is holding your whole Docebo platform together. It’s probably you.
If you administer Docebo, you already know whether this is for you — because your own version of that spreadsheet is open in another tab right now. Come build it with us.