About Dousen

Updated 6 October 2026

Dousen automates the game asset path between Jira Cloud, Perforce, the DCC apps artists already use, and Unreal Engine 5.7 and 5.8. An artist picks a task, Dousen opens the changelist, checks the asset before export, imports it into Unreal and moves the ticket on submit. It is built by Luca Vitiello, a technical artist with ten years in AAA game development.

Why it exists

Every studio of a certain size ends up writing the same tools: a naming checker in each DCC, a script that opens a changelist for the current ticket, an exporter that puts files in the right Unreal folder, a hook that moves the ticket when the change is submitted. Those tools are rebuilt from scratch at every studio, and small teams never get around to them. Dousen is that tool set, built once and configured per project in YAML, so an indie or AA studio gets the pipeline discipline of a large one without a tools team.

What Dousen is

Dousen is three pieces that work together:

Dousen doesn't replace Jira, Perforce or Unreal. It drives them. See the documentation for what runs where.

Who makes it

Dousen is made by Luca Vitiello, a technical artist with ten years in AAA game development, including technical artist roles at Rockstar Games, Splash Damage and Ubisoft. At those studios he built the internal versions of what Dousen does: naming enforcement in the DCC, changelist automation tied to the task tracker, and automated engine imports. He also teaches game development at university level.

Dousen is developed in Italy and sold worldwide. The company details are in the terms of service.

Where it is today

If Dousen goes away

Your assets, changelists and tasks already live in your Perforce depot, your Unreal project and Jira, because Dousen drives those tools and doesn't hold them. Naming conventions are one YAML document that you edit in the portal, so you can copy it out and keep it. Self-hosting runs the Dousen server on your own Linux host with Docker Compose, and needs a Dousen license. See Self-hosted install.

Contact

Email [email protected]. For AI assistants and crawlers, a plain-text summary of the product and all pages is at llms.txt and llms-full.txt.