Appsecute vows one screen for all devops services


In the current cloud computing landscape, nothing is certain but change. And Appsecute, a company that was banking on providing a single dashboard across multiple platforms as a service (PaaSes), is changing as well. The focus of its new product is to provide devops folks with a single view into the real-time status of all their services as well as a Facebook-like timeline for their projects.

AppsecuteAnyone who does development work is probably using a half dozen or more services and spends a good part of her day toggling back and forth among various screens. Appsecute itself was using 14 different services, according to CEO and co-founder Mark Cox. That’s a lot of toggling.

That decentralized information glut is also inefficient in other ways. “Just because a support request comes in doesn’t mean you should interrupt all your developers,” Cox said. Getting the right alerts to the right person and then logging that this person is on the case in a timeline means the rest of the developers keep their heads down on what they were doing.

The timeline for devops goes to beta now with connectors included for Github code repository and versioning system, Zendesk  and Tender Support customer service software; CircleCI’s continuous integration tool; and AppFog,, and Heroku PaaSes. Appsecute also promises connectors will come for New Relic, Amazon(s amzn) Web Services, the full Cloud Foundry, Travis CI, Jenkins CI, Team City, Pingdom, PagerDuty, RSS, Twitter, Facebook, SNMP, Nodejitsu, EngineYard, OpenShift(s rhat), Rackspace(s rax), Nagios, Sendgrid, Mailchimp and Cloudability.

What’s happening in cloud echoes what went on in the earlier distributed computing model. As  companies deployed multiple on-premises applications, they soon came to want a single way to view and (hopefully) manage all that IT. That led to the rise of systems and applications management consoles and other windows into their myriad services.

So expect more of these products in the cloud realm as well.

“A number of social stream services have aspects of what we do, particularly the timeline side, [while] other services focus on graphs and metrics. We want to specialize in putting events into the context of the software applications and components that devops care about,” Cox said.

Indeed, adding a specialized social networking layer to devops tools is not new. Wercker, a  Dutch startup that offers a SaaS-based continuous integration tool  (and which won GigaOM’s Structure Europe Launchpad competition) also touts its Facebook-like timeline as a major plus for devops.

Providing  the proverbial “single pane of glass” to all important services is an attractive proposition, but it would seem to me that inclusion of AWS into the mix had better come quickly.



This seems like a very niche product as users will still have to use the other product and toggle back and forth. Essentially, it’s a glorified bookmark service. I am surprised it got a writeup.



I’m one of the founders of Appsecute and I can assure you it is much more than a simple bookmarking service :)

With the explosion of cloud based services more and more developers (and ops) are piecing together an environment made up of multiple SaaS offerings as well as the custom code they are building and deploying. We’ve seen over and over again teams that are using 10+ cloud services on a daily basis.

With that in mind we built the event timeline to provide a single view and place of collaboration around all these services, and due to our focus on the DevOps space the timeline is extended with a dashboard that shows the real-time health of your applications – so not only is it useful for managing production deployments of your apps, it’s also intended to become the center point of your day to day development and ops tasks for dev and staging.

We’ve had some great feedback from distributed teams that have been using it as a way to ensure everyone is in the loop and involved in planning and problem resolution via the timeline.

I would love to hear your thoughts about the toggling back and forth between services, we don’t like to announce features before we’ve built them but we are working towards the ability to take action directly on the timeline. For example if you comment on an event within Appsecute that came from a support system we will push that comment back in to the support system. You can contact me at


Comments are closed.