RegDossier.eu's answer

Plain HTML, CSS and JavaScript, no framework and no third-party scripts.

TranscriptFetch's answer:

Next.js with TypeScript and Tailwind on the front end and API layer, Clerk for auth with SHA-256 hashed API keys, Neon Postgres with Drizzle ORM, Redis for caching, and Stripe for billing. The extraction layer is a Python and FastAPI service. Speech-to-text uses Whisper-class models. The MCP server is published in the official Model Context Protocol registry with a DNS-verified namespace.

RegDossier.eu's answer

Every calculation carries a citation to the specific Article it comes from. A compliance officer can open the tool, read the result, and check the maths against EUR-Lex without taking our word for it. Where penalties vary by member state, as they do under NIS2 and DORA, the tools say so instead of showing a single EU-wide number that does not exist.

TranscriptFetch's answer:

Most short-form video has no caption track to download. TikTok’s auto-captions are opt-in per upload, Instagram never publishes a downloadable track, and many captions on both are burned into the video frames where no parser can read them. TranscriptFetch transcribes the audio when no caption track exists, on the same endpoint, with the same response shape. Your code never branches on which method produced the text. It also covers YouTube, TikTok, Instagram, X and Facebook plus any web page as clean Markdown, so a pipeline spanning several sources is one integration rather than five.

RegDossier.eu's answer

Most tools in this space are lead magnets. They ask for an email, produce a generic score, and route the result to a sales team. These are free, need no signup, store nothing, and end with a link to a fortnightly newsletter rather than a call with an account executive. They also answer the question people actually have, which is whether a regulation applies to them at all, before the question of how to comply.

TranscriptFetch's answer:

Three reasons. Coverage: one API key and one response shape across five video platforms and the open web, instead of stitching together a library per platform. Reliability: requests run through rotating infrastructure, so code that works locally keeps working from a server, which is where most open-source approaches break. Billing that matches reality: one credit per successful response, with failed, blocked and empty results never charged. That last point matters on short-form video, where a meaningful share of any batch is music with no speech in it. There is also an MCP server, so AI agents can fetch transcripts as a tool without a custom integration.

RegDossier.eu's answer

Compliance officers, DPOs, risk managers and COOs at EU companies with roughly 50 to 1,000 employees. They are not lawyers. They usually cover several regulations at once with a small team or alone, and they need to know whether something is in scope before they need to know how to implement it. Smaller companies without a compliance function use the tools for the same reason, usually a founder or COO who has been handed the file.

TranscriptFetch's answer:

Developers and technical teams building on video and web content. The common cases are RAG and retrieval pipelines that need video as text, AI agents that need to read a link mid-conversation, content teams repurposing short-form video at scale, and media monitoring and research tools. It is an API first, so the buyer is usually the person writing the integration rather than an end user. The free browser tools exist for one-off transcripts and for evaluating output quality before writing any code.

RegDossier.eu's answer

RegDossier is a editorial project covering eight EU regulations. The tools came first because the questions readers were searching for, such as whether NIS2 applies to them or what the AI Act fines actually are, were being answered with 3,000-word articles when a two-minute checker does the job better. The rule from the start was that no number goes into a tool unless it can be traced to an Article in the Official Journal text.

TranscriptFetch's answer:

It started with discovering there is no good way to get the text of a video. YouTube’s official Data API will confirm a caption track exists and then refuse to hand it over, because captions.download requires the video owner’s OAuth token. The popular open-source libraries work until you deploy them, at which point platforms start refusing datacenter IPs. And YouTube is the easy case: TikTok and Instagram publish no caption file at all. Every workaround solved one platform, worked locally, and broke in production. TranscriptFetch is the version that handles the failure cases as first-class behaviour rather than edge cases.

RegDossier.eu's answer

The tools are free and anonymous, with no accounts and no tracking, so we do not know who uses them. RegDossier is an editorial publication rather than a vendor.