DigitalPermits

TeamCity is our main continuous integration server. It starts creating builds and running tests based on commits that we make in our hosted bitbucket repositories. From there, we have a set of configuraitons that can deploy the built and tested artifacts (web app, batches, db, etc...) to a stage or production server. We still release manually, but we release often, and TeamCity has nice features to help us roll back when things don't work out as planned. TeamCity

We log things of importance to loggly. It's a nice one-stop place to search into errors, exceptions, and expectations. Loggly

We use a combination of Scrum and Kanban for our tasks. We focus more on the integration with Bitbucket to keep track of tasks and have bi-directional accountability. JIRA

All of our (Engineering) knowledge is in Confluence. We document our thinking, our architecture, support recipes, trip notes, anything and everything. It's very important in a remote setting, to be have this type of knowledge store. Confluence

We just started looking into Datadog, but from what we see, it's like New Relic meets Loggly. It's really easy to plugin different services (like the one on this list) and get detailed analysis of what is happening on your servers and services. It makes tracking down sparse and difficult to understand problems possible. Datadog

Everyone in our company uses HipChat. From our help center to our engineering department, we do most of our internal conversations in hipchat rooms. Also as a remote engineering team, it is super useful to have a service like this so that conversations are logged and in the open. HipChat