SQL Agent runs on the database server. You would use Agent to call the console app the article describes.
Not sure exactly what you'd have to install on a system to make up an SSIS runtime, at least most of the appropriate version of the dotnet framework, which I suppose it might already have, but watch out for rev mismatches.
I believe there is a way to get Visual Studio to package up an SSIS solution with all runtimes for deployment, but I've never actually looked for it or tried to run it.
Actually, I will need to know this myself at some point, we have similar plans for eventual production deployment - not on the web server, but on a non-database "ETL" server. Though, whether that is actually a good idea or not, is debatable, a matter
of whether you want to run SSIS on the database server where it is close to the data but will steal memory and cycles from SQL Server, or off somewhere on a machine of its own but another network hop (or six) away from the database.
ps - the kill switch will be a challenge as well!