Marketing brief

devo.ps makes it easy to manage your cloud infrastructure. We're SaaS that makes creating, managing and automating your servers not suck.

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, notifications, code builds...
• And soon manage your applications.

Our core idea is organized around representing all of the components of your infrastructure as simple JSON files (not unlike packages.json), making it a compact, portable, visible and transparent blueprint of your strategy.

Keywords:

• Primary: Cloud, DevOps, Infrastructure, Servers, Automation, Deployment, Scalability
• Secondary: PaaS, IaaS, Configuration Management

What are people doing right now?

The following describes the existing competition and provides pointers at its perceived shortcomings. For a more exhaustive list, refer to the Space & Competitors page.

There are currently two options to solve your DevOps/infrastructure issues:

• PaaS aka The expensive black box: Heroku, DotCloud, AppFog and the likes. You settle for somebody else's strategy and decide to forget about the problem.
• The DIY approach: using various tools (Chef/Puppet, Capistrano, Jenkins...) you investing heavily into implementing parts of the DevOps tool chain (automation, orchestration, deployment...).

These do not answer the fundamental challenges:

• The Heroku-likes are mainly solving the deployment and (horizontal) scaling problems, while obfuscating the infrastructure layer, effectively locking you out of your own infrastructure. There are many (hard) problems beyond these issues, and if you're going to invest in solving them, you'd better own the solutions. More importantly, it gets very expensive very quickly.
• Building things on your own is not only expensive, but time consuming and risky. DevOps profiles are a rare breed and hard to evaluate. Moreover, this approach lacks portability and visibility; most of what you'll build will be spread across many technologies and tools.

Why choosing devo.ps?

Development and Operations are two different beasts. The Heroku stand is an attempt at obfuscating Operations from developers. Chef, Puppet, Rightscale and the likes are just better tooling.

This is why we've witnessed teams moving on from Heroku passed a certain scale of operations, and why more tooling (Chef, Puppet, etc) 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 a tool they can collectively build upon their infrastructure strategy, something reachable, visible and portable.

We make this bridge possible at a fraction of the cost of implementing it on your own, mostly by forcing our description of the elements of this strategy as compact and portable JSON files.

Audience & Customers

We intend to serve first small to medium sized technical teams, in or out of large organizations. A few examples:

• Startups: these teams usually move fast and have high level of expertise in development, but lack the resources (staff and time) to invest in getting their
• Dev shops:
• Technical teams within larger companies (candidates for Enterprise):

Our customers actually intersect heavily with Github's, which explains why we've taken a of inspiration from their licensing and pricing model. However, we avoid the complexity of individual and organization accounts for the online version since we believe

• Developer
• Ops
• Project manager

Based on these Our audience is obviously technical.

Founding team

• 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 ops, automation and security.
• Makara Wang - Development: Makara has been working on small to complex software architectures for the largest organizations in the world: CNN, the UN, the World Bank, governments... He spearhead the development team and the design of our software architecture.
• Ronan Berder - Product and Business: having previously built and scaled a consultancy working with the humanitarian world and Fortune 500, Ronan leverages his diverse background in software development, design, management and marketing to lead the business development, product management and marketing initiatives at devo.ps