A block in your platform, not a script in your pages
Some newsrooms do not assemble their pages with JavaScript: they compose them server-side from blocks supplied by external services, and their rules forbid iframes. We are a block provider. You declare ours, you place it in a template, and your own engine renders the HTML.
Your team controls every script in your pages, and a third party it cannot stop is out of the question. So is the iframe: it escapes indexing, your ad stack and your orchestration. The result is that you get offered an API and three months of development to rebuild everything.
A block in your platform, not a script in your pages
You read our contract
A public address returns the declaration of our blocks: template, parameters, cache policy, version. It reads without a key, so your validation tool can check it without us.
You place the block
In the article template, wherever you choose. A second block carries the synchronised text, to place in the body of the article.
Your engine renders the HTML
We only return data. The markup leans on your own design system's components: the player looks like your site because it is your player.
No iframe, no third-party script
Our JavaScript is served by your platform, concatenated with yours, with no global variable. Nothing is loaded from our domain at runtime.
Within the render budget
One hundred and forty milliseconds on a fresh instance, zero on a page already served. The route runs next to the data, with a declared cache.
No stylesheet from us
The player uses your classes, your colours, your icons. A change of brand guidelines on your side follows through without us touching anything.
Everything our player does
Word-by-word highlighting, chapters, summary, reading comfort, resume where you left off, listening measurement. This path costs you no feature.
Large news sites whose platform composes pages server-side, technical teams that forbid third-party scripts, press groups with an in-house design system.
Ready to give your articles a voice?
Book a 30-minute demo: we set WeDispatch up with you, no complex setup.
How much work for my team?
Hours, not days. Declare the block and place it in a template: there is no player to write, no API call to integrate, no manifest page to serve.
What if my design system renames its classes?
The template is a string in the contract: we publish a new version of the block, you validate it. The contract is versioned and immutable, exactly as your platform requires.
Does it work with subscriber-only content?
No, and that is deliberate. The block is called by your server with no visitor token: it cannot know the rights of the person who will read the page. An account that protects its files goes through the API, where your server vouches for each visitor.
Who hosts the audio files?
We do, by default, with a year of caching. You have no storage to provision and no retention to manage.