Given that it ultimately pokes around with Amazon's route53 infrastructure I'm not too sure that there'd be a gain if the site/processor were available in-house.
Even if the manipulation were local, the Amazon API would be remote, and not within a company's control.
Interesting idea though. Most of the backend is portable perl and easy to pull out..
Lots of companies already trust AWS and host various services there. Many of those companies might not trust your git servers to be up and running 24/7 with Amazon-like SLAs.
Thanks for the interesting perspective. I guess when I strip it down I've written a tiny layer of magic to convert a (bastardized)TinyDNS zone-file, or Bind zonefile, into Amazon Route53 update commands.
Selling that as a one-off utility would be hard, but it does currently work well as a hosted service via the webhook integration-layer, and a small amount of git-magic.
I will have a think to see if people would prefer it self-hosted, though nobody has expressed any interest in that previously.
Even if the manipulation were local, the Amazon API would be remote, and not within a company's control.
Interesting idea though. Most of the backend is portable perl and easy to pull out..