30-year film editor building a relational visual database.
Hi Product Hunt. I’m Chris. I spent three decades in film editing suites [IMDb here].
I built PictaBase because I got tired of managing production photos in "dumb" folders. Finding specific assets across thousands of files—like a prop from a specific scene—is a major bottleneck in our industry.
I am a solo developer. I used an adversarial AI development loop to build a platform with real engineering rigor:
Pixel-blind server: Image bytes go directly from your browser to S3 via presigned POST.
Sidecar metadata: All tags, notes, and AI labels are written to .meta.json files in your own bucket.
Technical baseline: 287 PHP files (38,500 lines) with 100% strict_types and PHPStan Level 8.
We are launching today. I am offering a Lifetime Deal, but there is also a fully functional Free Tier (250 MB) if you want to test-drive the architecture first.
I want people to push the code. Audit the API routes. If you find a way to bypass the 4-code hard cap in LtdCheckoutIntentController.php or break the metadata engine, let me know.
I’m here to talk tech specs, S3 presigning, or sustainability.
@PictaBase

Replies