Dmytro Krasun: ScreenshotOne from Solo API to $33K+ MRR
Ukrainian backend engineer who left high-load systems work and built ScreenshotOne into a reliable, bootstrapped screenshot API funded by customers.
- MRR
- $33K–$36K
- ARR
- ~$400K
- Users
- 1,000+ paying
- Founded
- 2022
- Team
- Solo (specialists as needed)
- Stack
- Go, Kubernetes, Playwright, Puppeteer, Docker
How did ScreenshotOne start?
Dmytro Krasun spent more than ten years building server-side systems that handled high load and distributed complexity. Taking a screenshot of a website looks simple until you confront the reality: browsers, cookie banners, ads, dynamic content, timing, and endless edge cases. Developers need the result. They do not want to operate the infrastructure.
He launched ScreenshotOne at the end of May 2022. The product is a hosted API that turns a URL (or HTML/Markdown) into screenshots, PDFs, or videos. Users call it and get the image back. The service handles the browser cluster, blocking, and reliability. Early on he gave himself a short window to find the first paying customer. The first sale arrived within a couple of months. Growth was slow and steady rather than explosive.
The decision to build an API matched his background. He had already tried a Twitter analytics idea and dropped it for lack of interest. The screenshot concept let him stay in the technical domain he knew while still serving a clear customer pain. Existing competitors validated the market instead of scaring him away.
How did the numbers grow?
Krasun has shared figures publicly for years. In April 2025 he published a blog post noting that ScreenshotOne had reached $200,000 ARR with more than 400 paying customers, fully bootstrapped and funded by those customers. On the four-year anniversary (29 May 2026) he posted on X that the product had grown to $33K MRR, over 1,000 paying customers, and more than 100 million API requests executed. Later updates referenced roughly $36K MRR still growing.
These are self-reported numbers. Third-party directories sometimes list different snapshots; the figures above come from the founder’s own posts and site. The business has remained profitable without outside funding. He has described infrastructure costs (clusters, storage) as a material but manageable part of the operation and has continued to invest in reliability rather than pure growth at all costs.
The path was not linear. Early Indie Hackers updates showed small revenue and the usual conversion experiments. Later public reports tracked churn, new customers, and API volume. He has noted periods where marketing was light and growth continued on inertia from prior work, followed by renewed focus on distribution.
What does distribution and customer work look like?
X has been a consistent channel. Krasun posts product updates, technical details, monthly-style reports, and candid thoughts on running the business. He also writes longer pieces on the ScreenshotOne blog and has appeared on indie founder podcasts. SEO and direct customer conversations matter. He has said he regularly asks users about their use cases in support chats and uses the answers to shape the landing page, features, and positioning.
The product itself has expanded into AI-agent use cases. A hosted MCP server lets agents request screenshots or Markdown of pages without local browser management. Customer stories on the site cover website builders, content tools, outbound marketing, and research products that need reliable page captures. Integrations include Make, Zapier, n8n, and official SDKs in multiple languages.
He runs the business mostly alone and brings in specialists for specific projects (for example a marketing-site redesign). The about page states he stays close to support, feature requests, documentation, and rendering edge cases. In public posts he has argued against fully automating support early, because talking to customers builds the mental model needed to improve the product.
What does the work look like now?
Infrastructure is real. Rendering at scale means browser processes, caching, storage, and reliability work. He has shared that the service runs across multiple providers. Product quality remains the daily focus: lower error rates, faster renders, better handling of cookie banners and long pages, clearer docs, and playground improvements. New surface area includes scheduled captures, archival, difference detection, and richer organization features that customers request.
He has also been transparent about the limits of the niche. Screenshot APIs are competitive and the total addressable market is not infinite. Growth has been steady rather than hockey-stick. In one conversation he discussed a plateau around the low-to-mid $30K MRR range and explored what would be required to push further. Side experiments and personal time (family, travel, reading) appear alongside the product work.
Margins are healthy enough for a solo operation because the core value is reliable rendering that customers prefer not to build and maintain themselves. The main ongoing costs are infrastructure and his own time. He has expressed interest in more automation and occasional help so he can take real time offline without the service depending on him every day.
Lessons that still feel true
Play to your existing skill. Building an API let Krasun ship something useful without inventing a new identity as a product designer. The market already existed; reliability and developer experience became the differentiation.
Talk to customers repeatedly. Public posts show he treats support conversations as research. Use-case answers changed positioning and features. Automating that layer away too early removes the signal.
Share the real numbers if you are comfortable. The $200K ARR post and the four-year $33K MRR update are primary sources. They are not leaderboard estimates. Sharing them has brought attention and, he has noted, also copycats. He continues to post anyway.
Slow compounding is valid. Three-plus years to substantial ARR in a narrow B2B API is not a viral launch story. It is consistent product work, SEO, public updates, and staying in the market long enough for inertia to help.
Finally, the niche has constraints. He has been open that screenshotting is not a category that will produce $5M ARR overnight. Focus and stubbornness matter, and so does knowing when the market itself sets a ceiling.
All revenue figures above are self-reported by Dmytro Krasun on his site, blog, or X. No third-party estimates are presented as fact.