Dealing with servers doesn't have to suck

Build and automate your own servers, deploy your apps on it in a few minutes

Say goodbye to Heroku, Puppet and Jenkins

Tired of expensive PaaS or complex tools like Chef or Jenkins? is like a GithHub for operations; your team can set up your servers, deploy your apps and automate everything in minutes, on any cloud, on your own terms. See how it works.

Cloud providers

Deploy your own machines on your preferred cloud

PaaS can be a great way to get something up and running quickly, but you're effectively locked out of your infrastructure. With, you can use your own account on Amazon EC2, Rackspace, Digital Ocean or Linode to provision new servers.

Node configuration

Stop wasting time configuring your machines

Ever spent half a day trying to configure your stack on a fresh instance? Googling instructions only get you so far, and even then you can't be sure things will hold in production. Just tell us what cloud you want to use and what services you need, we'll take care of the hard, tedious work.


Give your whole team access to your infrastructure

Tired of being asked to give access to a server by a team member? You're probably also taking care of deploying code, ensuring backups are running and managing the cloud provider account. With you can safely invite collaborators and start managing servers together.

Task runs

Automate everything right from the start

How many times did you promise yourself you would automate the most common tasks you run on a daily basis? Problem is, you never seem to find the time to get this done. With, you can get started right away with setting up continuous deployment, scheduled backups and easily script jobs to run on any of your servers.

Forkable repositories

Share and re-use your infrastructure like you do with code

You don't need to start from scratch every time you start a new project. Simply fork an existing repository from GitHub in one click or use one of your existing project. Get up and running with database backups, deployment pipelines and server configuration in a few minutes.

Our plans start at $0

Still not convinced? Come chat with us and ask any question you may have.

How does it work?

With you manage servers like you manage code: with files in Git.

id: web
name: Web server
type: server

  name: digitalocean

  nodejs: *
  nginx: *

      - gulp
      - forever
      - bower
$ git add nodes/web.yml
$ git commit -m 'Installing NGINX and Node.js'
  [master 27ba3cb] Adding NGINX server
  1 file changed, 2 insertions(+), 2 deletions(-)
$ git push
  Counting objects: 7, done.
  Delta compression using up to 2 threads.
  Compressing objects: 100% (3/3), done.
  Writing objects: 100% (4/4), 444 bytes, done.
  Total 4 (delta 1), reused 0 (delta 0)
  remote: [] Git push accepted.
  remote: [] 1 node updated: web (nodes/web.yml)
  remote: [] 
  remote: [] Your nodes are being synced, to see their status:
  remote: []  Go to:
  remote: []  Use the CLI: `devops logs --repo ninjacoder/meanjs --node <node_id>`
  To [email protected]:ninjacoder/meanjs
  078335f..27ba3cb  master -> master
  • Web server updated (2 services added)

    "Installing NGINX and Node.js" by ninjacoder
  • Deploy task removed

    "Removing old deploy pipeline" by coderbuddy
  • Deploy task run failed

    Triggered manually by ninjacoder
  • Deploy task added

    "Adding deploy pipeline" by coderbuddy

Built by a friendly bunch

We're a small team of technologists. We've worked with a wide range of technologies on small to very large scale platforms. We've had enough of fighting with crappy user interfaces, bloated software and inconsistent APIs when dealing with infrastructure: this is why we're building Come say hi to us in the chat.