Cloudomation Cloud Development Environments vs. Local Development Environments

Why switch from Local Development Environments to a Cloud Development Environments (CDEs)?
Find out now.

Standardise Processes

Share the same development environment across the enterprise and deploy it instantly when needed. Compatibility issues or configuration mismatches are a thing of the past.

Reduce Costs

Less time spent on troubleshooting, as maintenance of the development environment is performed centrally. Developers do not need expensive laptops, as computationally intensive activities are performed remotely.

Avoid Security Issues

No source code ends up on the laptop. Effectively protect the company’s intellectual property.

Setting up the local development environment takes time.
Continuous maintenance lead to productivity losses.

Developers waste a lot of time setting up the local development environment and regularly struggle with compatibility issues. Regular troubleshooting is one of the main problems. And not only that: developer tools eat up resources – expensive laptops have to be purchased. The source code is also stored insecurely on the developers’ computers.

With Cloudomation CDEs

  • productivity is increased because the development environment is available instantly.
  • the development environments are standardized.
  • computationally intensive tasks can be taken over by the CDEs.
  • broad automation and integration functionality is available.
  • your source code is secure, because it isn’t stored locally (air-gapped).

Why Cloudomation?

  • Also available as an on-premise solution.
  • Any number of self-service tools can be added.
  • No editor / IDE constraints: developers can continue to work with their personal favorite tools.
  • Broad automation options for integration with other tools.

Cloudomation CDEs vs. Local Development Environments

Task Cloudomation CDE Local Development Environment


Automation of the setup.
Provision of the tools and the
proprietary software
via one simple click.

Manual configuration for each project
(dev tools, dependencies, installation
of the company's own product)


  • Install editor
  • Start the CDE
  • Install Runtimes
  • Install Editor
  • Configure Git
  • Clone sources
  • Install dependencies / libraries
  • Install company software

Bug fix /
Version change

  • Change to the desired CDE
  • Fix bug
  • Switch back to the previous CDE
  • Pull the branch of the old version
  • Set up dependencies
  • Make local build work
  • Fix bug
  • Troubleshoot local build
  • Check bug fix
  • Push bugfix
  • Push current branch
  • Set up dependencies
  • Make local build work

Maintenance of the
Development environment

Centralized management.
Troubleshooting for the whole team.

Complex. Individual problem solving
per developer in case of errors

Securing the source

Secure setup possible (air-gapped).
Source code never locally on the computer.

Risk high because source code
is located on the computer.


Broad and sustainable
automation is possible.

Use of proprietary scripts, which
are difficult to maintain and error-prone.

Work with individually
selected tools

Selection of equipment

It can be developed on any
device. Less costs for the purchase
of equipment.

Purchase of expensive equipment necessary,
to have the power for all the tools.

Compiling, Linting,
Testing, Build

Runs on the remote server.
Performance thus individually scalable.

Locally. This can lead to waiting times if you
have old / less powerful equipment

Working without an
internet connection


Cloudomation DevStack

Start now with Cloud Development Environments