Two bits here - debuild.me --------- I've started working on a site to host my build stuff, and i've called it debuild.me  None of it's active, and I'm going to be slowly using it more as it becomes more, well, implemented. atlantic, etc ------------- I've been working (mostly quietly) on a cut down buildd, to test packages I intend to sponsor over a couple of different conditions. I'm going to run deep source checks, build the package a few different ways, check the basics (lintian, piuparts, etc) and lots of other stuff I might think is a good idea while doing it. At it's core, it doens't use buildd nodes like the archive, rather, it uses aws. When I dput a package, it spins up at least one AWS instance, based on an AMI I set up (and update frequently), and builds on that. This means -- yes! -- No queues! :) It also means I need careful oversight of the nodes, and pay attention to not running up a big bill. It should also be noted, this is not for uploading a built package to the archive, this is for testing packages before uploading them to the archive. Ideas / patches welcome