Gitpod vs local development

Why should you move your dev environment to the cloud? Here is the answer.

Developer experience

Developer experience

Developer productivity increases and results in greater organization morale.

Remote work

Remote work

Work from anywhere on any device. All you need is a browser.

Faster onboarding

Faster onboarding

Ready-to-code within seconds. No need to set up dev environments.

Open-source contributions

Open-source contributions

Increase in open-source contributions thanks to an easy onboarding.

Meet Bob and Alice

Let’s have a closer look on how desktop and cloud development differentiate.

Bob

Bob

works locally

Needs to manually configure each project. This includes:

  • installing development tools
  • cloning Git repos
  • installing dependencies
  • upgrade tools & dependencies
  • etc.
Alice

Alice

works in the cloud

Automates the configuration setup by using Gitpod Logo .

How does the setup affect their work?

Bob

Bob

alice

Alice

Ready within seconds when working in the cloud

As Alice automates the configuration setup by using Gitpod she is ready-to-code within seconds, while it can take up to days for Bob.

As Alice automates the configuration setup by using Gitpod she is ready-to-code within seconds, while it can take up to days for Bob.

Feel the difference

Spin up fresh cloud development environments for each task, in the cloud, in seconds.

Full blog post

Read a first-hand developer perspective on switching to remote development.

Join developers, everywhere.

Dev environments pre-configured with all the dependencies required to code in seconds.