Daniel Gulla

I build tools that turn messy public web data into something you can actually use — clean, structured, and reliable enough to put in a production pipeline.

What I care about

• Actors that don't fail quietly. Every run tells you what it got and what it couldn't. A video that fails shows up with a reason, not as a missing row you discover three weeks later.
• You pay for results, not attempts. My actors are priced so that failed items cost you nothing.
• Own infrastructure. I run my own servers and GPUs, which means some of my actors can do work that would be too expensive to buy per-request from an API. That saving goes into the price.

What I build

Data extraction and automation for video, media, and content pipelines — transcripts, structured metadata, and the boring plumbing that makes the rest of it work.

Before Apify I spent years building and maintaining production business systems — accounting, point-of-sale, and reporting software that real companies depend on daily. That work taught me the thing that matters most here: software people rely on has to be dependable long after launch day, and someone has to actually answer when it breaks.

Found a problem?

Open an issue on the actor's Issues tab. Include the input you used and I'll take a look. Bug reports and "can it also return X?" requests are both welcome — a lot of my best features started as someone else's request.