Stonly and Paligo Bet on Opposite Futures for Documentation

A help center is where good intentions go to die. Someone writes an article, ships it, and moves on. Six months later the product has changed, the screenshots are stale, and the customer who needed it has already opened a ticket. Everyone in software knows this failure. Two companies decided to do something about it - and, oddly, they arrived at almost opposite answers.

One is Stonly, out of Paris. The other is Paligo, out of Sweden. Both are frequently listed as alternatives to each other in the crowded knowledge-base market. But calling them competitors misses the point. They are not two runners in the same race. They are two answers to a question most teams never bother to ask out loud: should documentation react to the person reading it, or scale to the person writing it?

01 / The ForkSame broken article, two exits

Start with the customer who is stuck. They do not want a 2,000-word article. They want the one path that gets them unstuck, and nothing else. Stonly's bet is that the article itself is the problem. Instead of a static wall of text, it turns support content into interactive guides that branch - ask the reader a question, then show only the next step that matches their answer. It reads less like a manual and more like a conversation that keeps narrowing until the problem is solved.

Now start with the writer who is drowning. A technical writer at a hardware or life-sciences company is not maintaining one article. They are maintaining the same safety warning across forty documents, six languages, a PDF, a web portal, and a help desk. Paligo's bet is that the copy-paste is the problem. It is a component content management system, or CCMS: you write content once as structured, reusable blocks, then publish those same blocks everywhere. Change the warning in one place and it updates everywhere it appears.

Look at the founders and the split makes sense. Stonly was co-founded by Alexis Fogel, who spent nine years building Dashlane, the password manager, before leaving in 2018. Password managers teach a specific lesson: the hard part of software is rarely the feature - it is getting a real human to the right answer at the right moment. Paligo's Anders Svensson came from the opposite trench. He and his colleagues spent years consulting on DITA and XML documentation, watched teams suffer under heavyweight desktop tools, and built the affordable, browser-based CCMS they kept wishing existed.

02 / The MoneyTwo rounds, two theses

The funding tells the same story from a different angle. Stonly has raised roughly $25.5M, including a $22M Series A led by Northzone and Accel. That is venture capital betting on a front-end land grab: own the moment a customer needs help, across every product's website and app. Paligo took a different path - a $29M growth investment led by GRO, with existing backer Alfvén & Didrikson following on. That is growth capital betting on infrastructure: the unglamorous, sticky back end where enterprise content actually lives.

03 / The OverlapWhy the smart move is often both

Here is where the "versus" framing breaks down. Nothing stops a team from running both. In fact, the pairing is natural. Paligo is the source of truth - the place where a company authors structured, versioned, translated content and keeps it consistent. Stonly is the delivery layer - the place where that content meets a confused human and becomes an interactive path. Author once in a CCMS, deliver adaptively on the front end. The back end scales; the front end reacts.

This is why the industries barely overlap in the way you would expect. Paligo lists customers across software, manufacturing, life sciences, insurance, and finance - regulated, product-heavy worlds where a wrong or outdated instruction is a liability, and where content must survive audits and translations. Stonly clusters around support, product, and customer success teams whose main pain is ticket volume and drop-off. One is measured in compliance and consistency. The other is measured in deflection and adoption.

04 / The AI TurnBoth are pointing at the same wall

The recent AI wave has nudged both companies toward the same anxiety: stale content. Stonly has leaned into AI that monitors knowledge against source material and incoming tickets, spotting what has gone out of date and drafting updates for a human to review. Paligo's whole architecture is, in a sense, a pre-AI answer to the same problem - if content is single-sourced and structured, you fix it in one place and the fix propagates. Different mechanisms, same target: the moment documentation quietly stops being true.

That shared anxiety matters more now that AI assistants read your help content on the customer's behalf. If the underlying knowledge is wrong, the assistant confidently repeats the mistake at scale. Structured, well-maintained content stops being a nicety and becomes the thing that keeps an AI answer honest. Both companies, from their opposite ends, are effectively arguing that the knowledge layer is now load-bearing.

05 / The TakeawayPick by who is suffering

If you are choosing between them, the cleanest test is not a feature checklist. It is a question about pain. Who in your organization is suffering most? If it is the customer who can never find the one answer they need, and the support team fielding the same ten questions forever, the interactive, adaptive delivery Stonly is built for is likely the sharper tool. If it is the technical writer maintaining the same content across dozens of documents, languages, and channels - and the compliance officer who needs it all to stay consistent - the structured reuse Paligo is built for will pay for itself.

And if the honest answer is "both," then you have just discovered why these two companies can raise money in the same market without truly fighting over it. The most durable documentation stack of the next few years may not be a single winner. It may be a back end that scales and a front end that reacts, wired together. Stonly and Paligo each grabbed one half of that future. The interesting teams will take both.