SceneForge

Inspiration

Testing is a vital yet pain-staking part of the software development cycle, and one of the worst parts of it is generating data to test your app with. Tools exist (notably TestBox), but they suffer from ease-of-use and scalability issues. Hence, the idea for SceneForge was born.

What it does

You describe what you need in plain English. SceneForge's AI generates a fully configured sandbox — realistic synthetic data, role-based users, feature flags, all internally consistent across every table and view. You get a shareable link in under 2 minutes. No config files. No engineers interrupted. To test for edge cases, SceneForge has a chaos button. Click it and the AI injects a realistic edge case into your live sandbox — a failed payment, a permission conflict, a data anomaly — and it shows up everywhere simultaneously. We further simulate edge cases with the endpoint tester, which takes the synthetic sandbox data — including the chaos-injected broken data — and fires all of it at a real endpoint automatically. Then it tells you which requests passed, which failed, and what the failures reveal about your code -- all of which is summarized in a QA report, which we return.

How we built it

The frontend is built on React (Vite) with Framer being used to power the interactive code windows on the landing page. The backend is built with Typescript, primarily. SceneForge uses Moorcheh AI to handle its memory, growing smarter over time.

Challenges we ran into

Interestingly, and rather counterintuitively, building the application itself didn't present too many difficulties. Deploying it, however, absolutely did. We spent an hour trying to decide on a particular web hosting service to use and another hour bashing our heads together over how to use it. Then, after we thought SceneForge was complete -- a small error derailed the entire project, forcing us to redo the whole process. Additionally, we found ourselves quite fatigued and our productivity... staggered, to say the least.

Accomplishments that we're proud of

We're proud of building something deployable (and that actually works!) in the time we did. Unlike many hackathons, the bulk of our productive time was spent fussing over deploying, creating the demo video, etc.

We talked to the people at BorderPass, who identified real problems facing developers in their demos -- and we solved them. We're very proud of that :)

What we learned

We learned how to deploy web apps using Railway! None of our team members had ever deployed a non-static website, so it was a nice learning experience.

We came to the realization that, in 2026, hackathons are no longer about technical experience -- it's about who's the most creative. Ideas are key.

What's next for SceneForge

SceneForge is already deployed! What's next is shipping it as a real, usable product. The next version of SceneForge connects directly to your real schema and the sandbox matches your production data model exactly. On a technical note, we'd like to integrate CI/CD integration so that every pull request gets a fresh sandbox.