Building an AI Zombie Couple Video Generator with Next.js

A developer built AI Zombie Couple Video, a Next.js web app that turns two portrait photos into a personalized 15-second zombie love story using Seedance 2.0 or 2.5 at 480p, 720p, or 1080p, sold through one-time credit packs. After deployment, the developer traced failing login sessions and admin pages to a database connection pool hitting its client limit and fixed it by switching production to a transaction pooler with per-instance client reuse. The developer notes that matching motion direction across the scene cut and verifying database connection settings post-deploy were the key lessons.

I’ve been building AI Zombie Couple Video https://www.aizombiecouplevideo.org/ , a small web app that turns two portrait photos into a personalized, 15-second zombie love story. The idea came from the zombie couple video trend: a tense encounter between two lovers cuts suddenly to a happy memory of them together. I wanted to make that scene accessible to people who don’t want to write detailed prompts or edit a video timeline. The product is now deployed. Here’s what it does and a few practical lessons from getting it online. The user uploads two portraits and assigns the roles: They then choose Seedance 2.0 or 2.5 and an output resolution: 480p, 720p, or 1080p. The interface shows the credit cost before they confirm generation. The homepage includes an actual generated sample alongside its two input photos. This was an important design choice: visitors can compare the inputs and result before deciding whether to purchase credits. Generation uses one-time credit packs, with no subscription. A short video still needs clear visual storytelling. During development, we worked through details such as the distance between the characters, the direction of the zombie’s approach, and the transition into the memory scene. One particularly important detail was matching the movement across the cut. The zombie approaches from one direction, and the embrace in the memory continues that direction. The setting changes abruptly, but the motion should still make sense. Character identity, expressions, and clothing continuity also needed attention. These remain useful things to inspect when evaluating generated results; a finished clip can vary from the intended scene. The site uses: I started from a SaaS template and adapted the account, payment, and credit features to this specific product. One issue after deployment affected both login sessions and the admin dashboard. The database logs showed that the session connection pool had reached its client limit. The application was online, but database-dependent pages could fail. We switched the production connection to the transaction pooler and enabled database client reuse within each running application instance, keeping the connection limit small. After redeployment, we checked existing sessions, admin pages, credit balances, and several concurrent page reads. The useful lesson for me was that a successful build doesn’t prove the deployed application’s database connection settings are appropriate. For a paid generation tool, users need clear answers before pressing the button: Those questions influenced the confirmation step, balance display, credit records, and generation history. They also made it important to check payment settlement and credit handling separately from the visual interface. You can see the sample and explore the site here: I’d appreciate feedback on whether the sample clearly communicates the result and whether the model, resolution, and credit choices are easy to understand. If you’ve built a paid AI generation tool, what part of the user experience required the most iteration? Disclosure: This article was drafted with AI using development notes from the project.