I can't seem to figure out if this is ruby-centric (like Rake) or ruby-only.
Then, you can run the processes in the foreground with `foreman start` (eg. on your dev machine), or export the processes to config files for the init system of your choice (eg. on your server). Once the processes have config files in the init system, Foreman is out of the picture: your processes are run and managed by the init system.
Of course, this all works very well in a Rails app (hence my blog post), but that's only one of many uses. Hope that helps!