ProBackup's answer

Infrastructure runs on AWS. Backup files are stored in AWS S3 and metadata (IDs, tree structure, webhook registrations) in AWS RDS, encrypted at rest with AES-256 via AWS Key Management Service. Customers can choose from nine AWS regions (Ireland, Frankfurt, London, North Virginia, Montreal, São Paulo, Sydney, Singapore, Tel Aviv). ProBackup connects to each source app through its official API over OAuth, with all tokens AES-256 encrypted using unique initialization vectors. Data in transit is secured via SSL/TLS on port 443, enforced with HSTS. The backup engine is incremental and versioned, creating independent snapshots each cycle.

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.

ProBackup's answer

ProBackup started in 2017 as Momentum Tools, originally built to back up Podio. As more teams moved their operations into a growing range of SaaS apps and hit the same blind spot — that vendors don't protect customer data from customer-side mistakes — the product expanded. In August 2020 it relaunched under the ProBackup brand, adding Asana as the first new platform, and grew steadily from there to cover 20+ apps. A major platform refresh came in September 2023, SOC 2 compliance was achieved in May 2025, and the current version (3.0), with a completely redesigned UI, launched in August 2025. Today ProBackup is a lean, product-led company (ProBackup BV) serving ~2,500 customers.

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.

ProBackup's answer

ProBackup is purpose-built for SaaS productivity and CRM apps — not files or servers. It backs up the data living inside Asana, ClickUp, Monday, Airtable, HubSpot, Trello, Notion, Jira, Slack, Podio, and 20+ other tools, fully automatically every 24 hours. The key insight: your SaaS vendor backs up their own infrastructure for their disaster recovery, not to protect your work. If your team — or an AI agent acting inside the app — deletes or overwrites a record, the vendor can't bring it back. That gap is what ProBackup fills. Backups are incremental and versioned, so you get point-in-time recovery and can restore exactly what you need: a single field, a comment, a whole project. Optional Google Drive sync adds a second, independent layer of redundancy you control.

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.

ProBackup's answer

A few reasons. Breadth: one account covers 20+ platforms, and you can add unlimited apps on any plan. Granularity: restore a single record or an entire board, with point-in-time recovery to any previous day. No setup overhead: backups run automatically every 24 hours — no scheduling, no maintenance. Independent redundancy: unlike tools that dump a new CSV after every cycle, ProBackup syncs to a live Google Sheet you own, so you keep a usable copy even if ProBackup is unavailable. And trust: SOC 2 compliant, AES-256 encryption, isolated key management (no one at ProBackup can read your raw data), and a choice of nine AWS storage regions worldwide. It's a focused, product-led tool — self-serve onboarding, simple UI, transparent pricing.

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.

ProBackup's answer

Teams that run their daily operations inside SaaS productivity and CRM apps and can't afford to lose that data — typically SMBs and mid-market companies, often without a dedicated IT/backup function. The buyer is usually the admin, operations lead, or team owner responsible for an Asana, ClickUp, Monday, HubSpot, or Airtable workspace who recognizes that accidental deletion, a rogue integration, a departing employee, or an AI agent gone wrong could wipe out work the vendor won't restore. ~2,500 customers today, with a 35% trial-to-paid conversion rate.

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.