-
Notifications
You must be signed in to change notification settings - Fork 1
Marketing brief
devo.ps is a SaaS that helps you build, manage and automate your technical infrastructure, from servers to applications.
We want to be to Ops/DevOps what Github is to development. We allow you to:
- Create, manage and delete servers on any cloud: AWS, Rackspace, Linode, Digital Ocean...
- Manage services and their related configurations on these servers (think NGINX, Varnishd or Ruby).
- Easily build automation for anything managed through devo.ps: backup or deployment strategies, throttling, scaling...
- Soon you'll be able to manage applications too.
We make these things easy, portable, visible and transparent; everything is stored as simple JSON files, not unlike a packages.json file. We're
Keywords:
- Primary: DevOps, Infrastructure, Servers, Deployment, Automation, Scalability, Cloud, PaaS
- Secondary: IaaS, Configuration Management
- Our list of clients speaks for itself: Apple, CNN, the United Nations, the World Bank, Nvidia, Axel Springer, Popcap Games... We can provide references for any of our past clients. Include references
- Our technical chops: we are constantly updating our skills, investigating a very wide range of technologies and encouraging our colleagues to become full stack engineers. We more recently have focused on Javascript (node.js, angular.js, backbone.js...), Python, configuration management (Chef, Ansible), GIS, full text search engines, HTML5... At any given time, we experiment with many other things (Go, Erlang...) but are invariably using, and contributing to, Open Source. Many of us are deeply involved in several OSS projects.
- Our approach & methodology: we have a track record of consistently "shipping". From small to large projects, we use a combination of various methodologies, with a strong dose of "agile".
There are currently two options to solve your DevOps issues:
- The black box: Heroku, DotCloud, AppFog and the likes. You settle for somebody else's DevOps approach and decide to forget about the problem.
- The DIY approach: using various tools (Chef/Puppet, Capistrano, Jenkins...) and investing heavy resources into implementing parts of the DevOps tool chain (automation, orchestration, deployment...).
We want to provide users who outgrew the Heroku stage but don't have a dedicated DevOps team with a platform they can invest in building their strategy, from provisioning to automation. In our experience, this is the vast majority of the market.
Development and Operations are two different beasts. The Heroku stand is an attempt at obfuscating Operations from developers. Chef/Puppets are just better tools for Operations.
This is why we've witnessed teams moving on from Heroku passed a certain scale of operations, and why more Puppets/Chef doesn't mean a better collaboration between the teams (high barriers of entry and poor visibility, leaving development teams in the dark).
The bottom line:
- The larger portion of the market are companies who don't have (yet) a large and/or dedicated DevOps team but are passed the scale for Heroku.
Companies need a better platform they can invest in freely: no lock-in, no technology limitations (or at least none they can't contribute to remove, that's why we propose an Open Source version), access to their infrastructure.
Development and Operations teams need tools with a better shared visibility for them to collaborate.
- Vincent Viallet - Infrastructure: having worked with startups and Fortune 500, Vincent designs infrastructures that scale to millions of users. He leads all discussions related to security, ops and automation.
- Makara Wang - Development: Makara has been a critical player in most of our large projects, bringing his expertise in designing architectures and strategies, leading our engineering teams and spearheading technological innovation.
- Ronan Berder - Founder: Ronan founded Wiredcraft in 2009. As a jack-of-all-trades, he leverages his expertise in development, design and management to craft strategies and help teams ship products.