We’ve been working on FFmate for a while, and last week we released version 2.0.
FFmate is an automation layer for FFmpeg. It includes a job queue, REST API, watchfolders, presets, webhooks, a Web UI, and support for pre- and post-processing scripts. he idea is to move beyond shell scripts and provide a cleaner, cross-platform tool to run and scale FFmpeg.
The main change in version 2 is clustering. Tasks are split across multiple nodes using a Postgres queue, and the system keeps running even if a node goes down.
We rewrote the Go codebase using Goyave. The rewrite cut about 2,000 lines, simplified the structure, and gave us a solid base for future features. Webhooks now support retries and execution logs, and watch folders use lock files for more reliable handling
If you’ve worked on scaling or automating FFmpeg, we’d like to hear your thoughts.
rbgala•1h ago
FFmate is an automation layer for FFmpeg. It includes a job queue, REST API, watchfolders, presets, webhooks, a Web UI, and support for pre- and post-processing scripts. he idea is to move beyond shell scripts and provide a cleaner, cross-platform tool to run and scale FFmpeg.
The main change in version 2 is clustering. Tasks are split across multiple nodes using a Postgres queue, and the system keeps running even if a node goes down.
We rewrote the Go codebase using Goyave. The rewrite cut about 2,000 lines, simplified the structure, and gave us a solid base for future features. Webhooks now support retries and execution logs, and watch folders use lock files for more reliable handling
If you’ve worked on scaling or automating FFmpeg, we’d like to hear your thoughts.
Repo: https://github.com/welovemedia/ffmate
Docs: https://docs.ffmate.io