ScreenshotOne

A screenshot API that handles browser rendering and capture options.

API subscription + usageDeveloper tools
Visit website
Reported revenue$200,000ARR · Unspecified $Historical ARR milestone reported April 2025Original disclosure
Business modelAPI subscription + usageDeveloper tools
Profile depthResearched profileProduct facts and editorial breakdown
Source checkedOct 19, 2026Observation date, not revenue cutoff

Business overview

Public positioning

A screenshot API that handles browser rendering and capture options. The April 2025 founder post describes outside design and part-time frontend help, with no immediate full-time hiring plan. The current About page describes a founder-operated business using specialists.

How it makes money

Free request allowance followed by paid API tiers and optional overage.

Business breakdown

Researched Oct 19, 2026

Source-linked product facts, followed by MRRTrace analysis of the customer problem, workflow, trade-offs and questions to test.

The customer problem

A developer may need website previews inside an existing product without becoming responsible for browser maintenance and rendering edge cases. The sale is therefore reliable output inside another workflow. A small-team opportunity lies in owning a troublesome technical boundary while allowing the buyer to keep its own interface and customer relationship.

Core workflow

  1. Send a page address or supported document input to the rendering API with the required capture options.
  2. Receive the rendered output and incorporate it into the application's preview, report or visual-analysis workflow.
  3. Observe request usage, resolve problematic captures and select an allowance or optional overage policy appropriate to recurring demand.

What customers pay for

Rendering credits make usage tangible, while throughput and feature availability separate tiers. Evaluation should also measure whether screenshots arrive with usable content: a technically successful request can still require inspection or support.

Distribution signals

Observed channels and entry points; their performance is not inferred.

  • Search and public founder updates

    The April 2025 founder article describes Google-origin customers and public business updates. It does not establish channel attribution percentages or acquisition cost.

    Evidence

Trade-offs

  • A focused API limits product scope, but changing websites can expand maintenance work without introducing a new feature.
  • Usage pricing can align bills with demand, while infrastructure cost and difficult support cases may vary substantially between customers.

Open questions

  • Which capture failures are expensive enough that a customer prefers a managed API to its own browser script?
  • Can onboarding help buyers estimate recurring demand before they encounter a quota or unexpected output issue?

A MRRTrace reading of public product material. Trade-offs and questions are editorial analysis.

Revenue evidence

Founder disclosure
$200,000ARR · Unspecified $ · Historical ARR milestone reported April 2025
Reporting period
Historical ARR milestone reported April 2025
Figure as of
Not provided
Reporting method
Founder disclosure
Source checked
Oct 19, 2026
Source updated
Apr 10, 2025

The founder reports a $200,000 ARR milestone and more than 400 paying customers in an article updated April 10, 2025. Exact financial cutoff is not supplied. It is not current revenue, annual recognized revenue or profit. The income source uses $ without an explicit currency code; preserved as Unspecified $ and excluded from USD comparisons.

Dmytro Krasun official operating update
This historical disclosure is separate from any current Stripe connection shown on this page. MRRTrace has not audited the business. Revenue is not profit, and historical figures are not current earnings guarantees.

Free allowance and paid request tiers; see current limits

The source page may change its prices, limits, or offer after the recorded check date.

What founders can learn

Editorial notes

Turn recurring browser-rendering maintenance into a focused API.

Before you build something similar

  • Historical founder disclosure with unspecified dollar currency.
  • Browser compatibility, infrastructure and support require ongoing work.

These are MRRTrace observations, not statements by the founder or proof of a repeatable outcome.

Source material

4 sources
  1. ScreenshotOne official website Public source · Checked Oct 19, 2026
  2. Official company / founder disclosure Public source · Checked Oct 19, 2026
  3. Official company / founder disclosure Public source · Checked Oct 19, 2026
  4. Official pricing Public source · Checked Oct 19, 2026