Wire ingest
Reuters, TT, AP or an in-house feed.
Wires land as drafts, categorised by IPTC topic and prioritised on arrival.
Modes
Simple mode or planning mode - your team, your choice.
One setting decides whether editors see the full planning desk (assignments, workflow chips, roles, audit trail) or a stripped-down write-and-publish view. Change it back at any time, without migrating anything.
Simple mode
Write, edit, publish.
Planning and workflow controls stay out of the way. Draft, headline, publish - that is the whole thing.
Planning mode
Assignments, desks, deadlines.
Plan the day as a list of stories with assignments and deadlines. Every article carries a workflow state and a full audit trail of who changed what.
Workflows
Editorial workflows your newsroom defines.
Draft, review, cancelled, withheld, published - or whatever your desk actually calls those steps. Draw the states, connect the arrows between them and decide which roles are allowed to move an article from one step to the next. Version bumps, confirmation prompts and AI steps are all tied to individual transitions, so you have precise control over what happens each time an article moves.
Role-gatedEach step names the roles that can move an article into it. The button greys out for anyone without permission.
Versioning built inAny workflow step can mark a new version of the article. A version pill on the article header shows the current cut.
Confirmation promptsHigh-stakes moves (publishing, withdrawing) can carry a confirmation dialog. You author the prompt in the workflow editor, no code required.
Wires and AI
Coverage in. AI on the workflow. Human on the last mile.
Wires come in from Reuters, TT, AP or an in-house feed. They land categorised by topic and can trigger AI steps at any point in your workflow - translate the story, summarise it, rewrite it in your house voice. The output always arrives on an editor's desk before it reaches a reader. Use your own AI provider or run the models included with Tidenda.
AI on the workflow
Bound to a step, snapshot on every run.
Translate, categorise, rewrite, summarise. A snapshot is taken before every AI step, so a bad model output can never corrupt an article - it is always one click to roll back.
Local models included
NLLB-200, mT5-XLSum and mDeBERTa run inside your deployment.
NLLB-200 (translation), mT5-XLSum (summarisation) and mDeBERTa (categorisation) ship with Tidenda and run inside your deployment at no per-request cost. Point at OpenAI, Anthropic or Mistral whenever you need to.
Audio
Interviews arrive transcribed, verifiable and ready to quote.
Upload a recording. By the time you open the file the transcript is written, with speakers separated on their own lines. Approve a segment and Tidenda signs it cryptographically - a permanent record that this text is what the recording actually contains. Drag a sentence from the transcript into an article and it lands as a blockquote a reader can play back and check for themselves.
Transcribed on arrivalWhisper runs the moment a file lands. Segments, timestamps and detected languages are all filled in before you open the recording.
Speakers separatedEach speaker's lines are labelled separately (Speaker A, Speaker B, Speaker C). Rename them once and the correct name follows through every quote drawn from the recording.
Signed and verifiableAn editor approves a segment; Tidenda signs it with Ed25519 (a strong cryptographic signature). When you drag the quote into an article, the signature travels with it - a reader can verify the quote against the original audio.
Assets
An image library inside the newsroom.
Photographs, illustrations and graphics live next to the articles that use them. Captions, rights and photographer credit follow the image wherever it goes - into an article, out to a webhook, or onto the public site. Every image is signed cryptographically (Ed25519) at upload, so a downstream reader can prove it hasn't been altered.
One archive, one searchFilter by article usage, byline, restrictions, date or tag. Drop an image into an article and the caption pre-fills from the file metadata.
Content provenanceA cryptographic signature (Ed25519) is attached at upload. If the image also arrives with a C2PA manifest - the industry standard for content provenance - we validate it and preserve it end-to-end. Anyone downstream can verify either one.
Rights that travel with the fileRestrictions, usage terms and photographer credit stay attached through every downstream path: webhooks, RSS feeds and the public site.
Publisher
A live site, one click away.
Turn on the publisher and your organisation has a working public site immediately. Pick a template, publish an article, it appears on the site. When you are ready to run under your own domain, add a DNS record; we handle verification and HTTPS certificates for you.
Custom domain, no ops workAdd a tidenda-verify DNS record and we handle verification and HTTPS certificates automatically. Until your domain is ready, the site is live on a preview address you can share.
Follow-up story clusteringGroup related articles under a lead story - a running feature, a rolling breaking-news thread. The layout renders the lead and its follow-ups without any manual markup.
RSS feeds includedA site-wide RSS feed and one per section, ready for aggregators, newsletter tools and downstream mirrors.
Integrations
Connect the newsroom to what you already run.
When an article moves through your workflow, a webhook fires and downstream systems - a print system, an archive, an analytics pipeline - can react. The delivery is cryptographically signed so they can verify it came from you. Going the other way, a scoped API key lets an external system push wires, planning items or article writes into Tidenda. The docs cover the full details your operations team needs.
Signed outbound webhooks
Every delivery is signed twice: HMAC-SHA256 on the request body, and Ed25519 on the article snapshot. Receivers can verify authenticity in any language. Deliveries are idempotent and replayable from the admin UI.
Webhook docsContent injection API
Push documents into your organisation via a scoped API key. Good for custom wire importers, upstream editorial systems and migrations from a legacy tool.
API referenceEvent stream
Every document transition is published as an event. Downstream consumers subscribe and stay in sync automatically, with a catch-up cursor for consumers that fall behind.
All docsGet started
Fits the way you already work.
Start with one user, free for a year. Add colleagues as you grow.