Following the news of a switch to a pay-as-you-go model, we asked Codenvy CEO Tyler Jewell what the new approach means for users.
As of Codenvy’s latest 3.9 release, users will only pay only for what they’re using. With a gigabyte per hour measurement, cost control functions and a 10 free gigabyte hours a month, the microservice and Eclipse-based technology is hoping to appeal both to the frugal occasional user and the frequent enterprise users via a brand new pay-as-you-go model.
The latest update to Codenvy also brings a number of interesting changes, including an On-Prem installation manager for migrating from one installation to another. Founder and CEO Tyler Jewell tells us the need for simplicity is what inspired them to change their pricing model.
JAXenter: What motivated the decision to change to a pay-as-you-go pricing model?
Tyler Jewell: Simplicity for buyers. We previously had a model where we created packages of resources and features. It was difficult to scale and customers struggled to know which package was right for them. We had 10 different packages of RAM sizes and each of those had 4 different feature combinations. 40 SKUs will make anyone’s head hurt.
With meter-based pricing, there is a single metric, Gigabyte hours, that is easy to understand, measure, and track. This metric measures consumption and usage of the system, allowing us to unlock all of the features of Codenvy for new users. It removes any of the decision work that an evaluator goes through in asking whether certain features are right for them, since they can use all of them from the beginning.
We still provide pre-paid subscriptions with bulk amounts of Gigabyte hours and customers can prevent runaway bills by setting workspace caps that limit consumption. Architecturally, we measure consumption in byte microseconds and are able to continuously calculate the Gigabyte hour consumption for each user, workspace, and account.
What kind of new users has Codenvy added recently? And how are they using it?
Our new user growth has been increasing about 30% month over month, and we will do around 6,000 this month. New users span the range of students, consultants, software development companies, open source project members, and devops professionals evaluating Codenvy for deployment within their own organization.
We have four types of buyers for Codenvy.
OEM / Strategic:
- Uses Eclipse Che and Codenvy to build new hosted, embedded or desktop IDEs for their products.
- Vendors like WSO2, SAP, YouthDigital, and Gazibit are actively doing development.
- Eclipse Che community now has 40 committers and 77 active contributors.
- Uses Codenvy On-Prem to make internal development more productive. In these scenarios integrating with the existing tool chain, letting developers continue using their preferred desktop editors, and connecting to restricted behind-the-firewall resources are part of the automation that drives them.
- We now have 100s of trials of On-Prem occurring, mostly in large brand name organisations that are adopting agile, continuous integration, continuous delivery, and hosted git.
- Uses Codenvy SaaS for collaborative development and shared workspaces.
- Nearly 60% of these projects are Java projects.
- Now over 400,000 projects built with Codenvy.
Individuals – students, hobbyists, and consultants working on the world of projects that are cool, educational, and eating the world.
Can you also tell us a bit about the Eclipse Che project?
Eclipse Che is both a cloud IDE and an SDK for creating a custom cloud IDE by packaging extensions you author into an assembly. Che can be used as a desktop IDE, embedded IDE, or a hosted IDE. It is supported as part of Eclipse Cloud Development initiative with backing from Codenvy, IBM, SAP and Pivotal.
Codenvy runs Che as its kernel, and it is also possible to take extensions authored in Che and package them into Codenvy On-Prem to create a new distributed tooling system.
What other kinds of improvements can Covenvy users look forward to?
We have a rich pipeline of activities. We are releasing a couple times per week now, and ship a little less frequently.
Things that are coming include a centralized installation manager for codenvy on-prem intances that allows for REST-management of Codenvy clouds; a new machine architecture with bi-directional syncing of machines, separation of command execution from machines, and machine snapshots; persistent machine URLs with pretty formatting; advanced content assist for Java with 20 different forms; gradle plug-in; a new user dashboard with responsive design; and launching an analytics system that lets users track their performance relative to their peers.