Built in Europe. Runs on your store.
Otto is a catalog-production tool, not a photo-sharing app. It exists because DACH distributors keep asking the same question: how do we photograph 700 products without a photoshoot?
The operator behind Otto
Otto is built by a solo operator based in Croatia, working with distributors across Austria, Germany, and Switzerland. No team, no office, no VC. One person, one pipeline, one supported workflow. When you email the founder, the founder replies.
Why this product exists
Two pilot customers — Markowitsch (Austrian promotional-goods distributor, 700 SKUs) and ZUBA (cast-iron stove distributor, supplier-PDF intake) — hit the same wall in 2025. Their product photography costs scaled linearly with SKU count. Their sales did not. Traditional photo production was a tax on growth.
Otto was built on their real catalogs. Every pipeline stage — parse, vision, generate, review, publish — exists because one of them needed it. No hypothetical features. No stock workflows.
What Otto is not
Otto is not a general AI image tool. It does not generate marketing banners. It does not compose headshots. It does not remove objects from wedding photos. It does one thing — turn catalog inputs into shelf-ready product images with SEO copy, and publish them to your store.
Where Otto runs
Fly.io, Frankfurt region. Product data and images stay in EU infrastructure. Image generation uses Google Gemini in the EU region. Emails sent through SiteGround SMTP. Billing through Stripe Europe. Analytics through Plausible (EU, cookieless). Full processor list on the privacy page.
What comes next
Catalog photography is the opening product. Next: video rendering for TikTok Shop and Instagram catalogs, automated A/B testing of hero frames, retail-shelf mockups. Each feature earns its place by moving a real buyer's numbers.
Start a Pack. Otto handles the rest.
Pay once. Upload your SKUs. Shelf-ready images and SEO copy in your store this week.