About

Desvelio did not come out of a product meeting. It came out of a newsroom.

We are a small team in Salamanca. For more than a year we have been building a local newspaper’s software and watching, every afternoon, how a real homepage gets decided.

A newsroom gathered around printed homepage proofs at the end of the day.

First we made the newspaper. Then, what it was missing.

Hands at a newsroom desk at night, building a newspaper’s site.

Before Desvelio we built the CMS, the site, and the app of a local newspaper. Not as a vendor that delivers a project and disappears: inside, with the newsroom, answering when something broke on a Sunday night and hearing what they asked for when nobody was in the room.

More than a year like that teaches you things that do not show up in any report. That a local publisher puts out dozens of pieces a day and decides all day long. That the homepage is not locked once — it is reshuffled fifteen times. That at eight in the evening someone looks at a story that is not taking off and has two minutes to change the headline, move it up, or let it die.

And that for all of that they had Google Analytics open in another tab. When they opened it.

The problem was not a lack of data. It was where the data lived.

An editor reading printed pages while a second screen sits unused.

The analytics tools publishers use are well made, and they do not serve what the shift needs. They are built to analyse last month, not to decide the next ten minutes. They speak in sessions, bounce, and engagement rate. And they live somewhere else: you leave the site, open a dashboard, find the story, read a chart, and come back.

That trip is only taken by the person who has analytics in the job description. The rest of the newsroom never does it. Not for lack of interest: at that hour there is no time.

So we turned it around. If the decision is made looking at the site, the information has to sit on top of the site. No dashboard, no new tab, no translation. You open your publisher the way you open it every morning and you see what is happening and what is worth doing, on the story itself.

That is Desvelio. And it is what we would have wanted when we were on the other side.

Four things we are sure of.

A printed homepage on a table, marked by hand on one story.

Analytics you have to go and open do not get opened.

That is why Desvelio has no dashboard to log into. It sits on top of your site, where you are already working.

A newsroom does not speak in metrics. It speaks in decisions.

The numbers are there, and for whoever needs them they are complete. But the first thing you read is not a percentage: it is what is happening and what you can do.

Your readers are not merchandise.

We measure without cookies and without storing anything on the reader’s device. The data is yours, it stays in the European Union, and there is no sharing or selling to third parties, and no cross-site tracking.

If we have to lock you in, the product is not worth it.

Month to month, with no lock-in and no penalty. If a month does not help you, you leave. We would rather know.

What you can expect.

A conversation across a table, no ticket and no queue.

You talk to the people who build it.

No ticket, no tier 1, no “I’ll escalate this to the product team.” The product team is us.

It goes on in days, not months.

A script on your site, a DNS name, and a legal paragraph. It works with any CMS. Nothing to migrate and nothing to change in your layout.

We do not ask for your history.

We start measuring from zero, with our own system. We do not need access to your Analytics or to your past data.

We listen, and it shows up fast.

A good part of what Desvelio does today came from a newsroom telling us “this is no use to me.” We still work that way.

Where we are today, with no polish.

A young editor at a desk today, laptop open, printed pages still in progress.

Desvelio is a young product and we would rather say so ourselves. It is running on two real publishers, in production, every day. The first two readings, Readers and Competitors, are finished and in use. Searches and Content have dates on the roadmap and are not on the panel yet.

We will not tell you we do more than we do. A small team cannot compete on catalogue size, so we compete on the opposite: we do one thing, we do it whole, and we do it well before we move to the next.

If you want a large vendor with twenty modules, there are better options than us. If you want a tool your newsroom will actually use, and someone who picks up the phone, we think this will fit.

Why from Salamanca.

A sandstone street in Salamanca in late afternoon light.

Because it is where we live and because it suits us. The publishers we work with are not in a Madrid tower: they are newsrooms of ten or fifteen people who do journalism with what they have. We work the same way, and that is why we understand each other quickly.

It also explains the price. We are a small team, with no funding round to pay back and no structure to keep up, so we can start at €80 a month instead of a thousand. That is not a launch offer: that is what it costs.

Shall we put it on your own site?

A laptop and printed pages of a homepage on an empty newsroom desk.

The best way to understand Desvelio is not for us to tell you. It is to see it on top of your homepage, with your stories and your readers. We install it in a few days and we look at it together — thirty days, on your own publisher.