As I was getting ready to roll out Executify, I like many of you read Scott Gu’s announcement of Azure Mobile Services providing scheduled jobs, and I was very excited by this announcement.  Because it was validation of the service I have been working on since May, and we didn’t seem to step on each others toes.  Because we differ in one major way.

• Azure Mobile Service Jobs are Node.js based
• Executify Jobs are .NET 4.5 based.

So with Executify you don’t have to worry about rewriting all your .NET code to get it running in the cloud.  The only thing you need to do is follow the instructions on creating your first app, sit back, and let us do all the scheduling work so that you can focus on what matters to you.

I have a common problem that many developers have. I have small programs or processes that I want executed on a semi-regular basis, but having a whole server set aside for just running these processes seems like overkill. Back in May of this year I was thinking about this problem, because I had a small program that I needed run every day in the morning, but paying the exorbitant prices of a worker role from Azure or AppHarbor seemed like overkill for what I needed.

I knew there were others like me so I set out to build a service that provided an on-demand worker role, that allow developers like my self to only be charged for the small amount of time that their program was actually running.  I decided to call it Executify.

More is to come in the future, but if you would like to be an early adopter or test out the service you can sign up for an account on http://executify.com