Revyl logo

Revyl

AI-Native Mobile Testing

Fall 2024active2024Website
Developer ToolsB2BInfrastructureAI
Sponsored
Documenso logo

Documenso

Open source e-signing

The open source DocuSign alternative. Beautiful, modern, and built for developers.

Learn more →
?

Your Company Here

Sponsor slot available

Want to be listed as a sponsor? Reach thousands of founders and developers.

Report from 2 months ago

What do they actually do

Revyl is a hosted testing platform for mobile apps (iOS and Android) with a web testing surface. Teams upload their app builds, define tests in plain English or record flows, run them on Revyl’s cloud simulators/devices, and get session video, crash replay, and triaged reports they can share docs product page.

It integrates into CI via a GitHub Action so pipelines can upload the exact build, trigger tests, and receive report links and machine‑readable outputs for gating merges and debugging CI docs GitHub Action repo. Tests can be written in natural language and executed by Revyl’s AI agent or created by recording steps in the editor creating a test.

Who are their target customer(s)

  • Mobile app engineers (iOS/Android) who own builds and releases: They lose time on device‑only issues and slow crash reproduction from user reports. They need reliable, fast feedback tied to the exact build so regressions are caught before shipping.
  • QA engineers focused on mobile testing: Cross‑platform suites are repetitive and fragile, breaking across simulator/device differences. They need tests that are easy to author and maintain while staying stable across environments.
  • CI/CD/DevOps owners running pipelines: Pipelines struggle to upload the correct build, run device tests reliably, and emit machine‑readable results to gate merges. They want reproducible runs and clear outputs that fit their workflows.
  • Engineering managers and product owners for release quality: They lack clear, actionable signals about which failures matter and how long fixes take. They need triaged reports and replayable failures to make ship/rollback decisions confidently.
  • Security/compliance or enterprise platform leads: Many testing tools miss enterprise audit, access, or workflow requirements, blocking adoption. They need team controls, auditability, and dependable integrations before rolling tools out broadly.

How would they acquire their first 10, 50, and 100 customers

  • First 10: Run tightly scoped paid pilots via YC/founder networks and GitHub Action watchers; offer free credits, 1‑hour onboarding, and a 2‑week pilot proving crash replay plus CI traceability on a real build with hands‑on support.
  • First 50: Turn pilots into short case studies and playbooks; list the GitHub Action in GitHub Marketplace, run targeted webinars and sponsor React Native/Flutter meetups, and share CI guides in DevOps/mobile communities to drive self‑serve starts.
  • First 100: Add an SDR and a sales engineer to run outbound to mid‑stage mobile teams, close pilots, and handle initial enterprise needs (e.g., SSO/audit logs). Expand CI/crash‑tool integrations and use wins to craft repeatable vertical messaging.

What is the rough total addressable market

Top-down context:

Global software testing and test automation spend is on the order of USD 50–60B in 2024–25, based on industry estimates for software testing (~$55.8B in 2024) and automation testing (~$35.5B) GMI Precedence.

Bottom-up calculation:

Mobile testing is estimated around ~$21.7B in 2024; automated testing represents roughly ~46% of mobile testing, implying an automated mobile‑testing segment near ~$10B GMI Mordor.

Assumptions:

  • Market reports differ on whether they include services vs. software subscriptions and device clouds; figures use conservative, published estimates.
  • Revyl’s near‑term focus is automated mobile testing integrated with CI, not the entire testing TAM.
  • Expansion beyond mobile (web/backend/observability) and enterprise features would be needed to access the larger testing budgets.

Who are some of their notable competitors

  • BrowserStack: Large cloud of real devices and simulators for manual and automated app testing with CI integrations; overlaps on device/cloud execution and artifacts. Revyl differentiates on natural‑language test authoring and AI‑driven triage BrowserStack.
  • Sauce Labs: Enterprise real‑device cloud plus emulators/simulators and diagnostics for large automated suites with CI/CD. Revyl emphasizes AI agents for plain‑English tests and triage vs. running existing frameworks Sauce Labs CI.
  • Firebase Test Lab (Google): Cloud device lab integrated with Google tooling and gcloud for large‑scale instrumentation tests from CI; infrastructure‑first and not focused on AI test generation or triage like Revyl.
  • HeadSpin: High‑end platform combining global SIM‑enabled devices, deep performance metrics, session replay, and AI issue cards. Revyl is currently focused on AI execution of plain‑English functional tests and CI triage HeadSpin.
  • Kobiton: Mobile device cloud with scriptless recording, Appium support, session videos/logs, and CI integrations; includes self‑healing for scripts. Revyl’s pitch centers on natural‑language authoring and an autonomous AI agent for multi‑step flows Kobiton capabilities.