How to Start Your First Cloud Dev Environment in Gitpod

October 30, 2026

Gitpod is a cloud development environment that boots a full Linux workspace from your repository in about 30-60 seconds, with your dependencies already installed. You open a branch in the browser or VS Code, and the code runs on Gitpod‘s servers instead of your laptop.

That pitch matters if your machine already runs two Node versions, four Docker images and a Python venv you are afraid to delete. It matters less if you mostly edit static HTML.

What is Gitpod, exactly?

Gitpod is a hosted platform that builds an ephemeral container per workspace. Each workspace is tied to a Git branch, so a feature/login workspace never touches your main state.

The container is described by a .gitpod.yml file you commit to the repo root. That file lists the Docker image, the tasks to run on boot, and which ports to expose. No .gitpod.yml means Gitpod guesses from your stack — usually Node.js or a generic Ubuntu image.

A workspace stops automatically after 30 minutes of inactivity by default. That is configurable in project settings, but keep it in mind before you walk away from a running dev server.

How do you launch a first workspace?

  1. Open gitpod.io and sign in with GitHub.
  2. Pick a repository. Gitpod installs its GitHub App and asks for repo access — grant it only to the repos you actually want.
  3. Choose a branch, then click the New Workspace button.
  4. Wait for the pull, the init tasks and the VS Code editor to load in your browser.

Your browser tab is now a full VS Code (open-source build, so some Microsoft marketplace extensions are missing). You can also connect your desktop VS Code through the Gitpod extension or SSH if you prefer your local keybindings.

Why does .gitpod.yml decide everything?

Because the file is the contract between your repo and the cloud. Gitpod reads it on every workspace start, and the tasks block is where most people live.

tasks:
  - init: npm install && npm run build
    command: npm run dev

init runs once per prebuild. command runs on every workspace start. Getting that split wrong is the single most common Gitpod mistake: put npm run dev under init and your dev server dies the moment the prebuild finishes.

Ports need declaring too. A Vite app on 5173 is invisible until you add port: 5173 with onOpen: open-preview. Gitpod will otherwise detect the port late and you will spend two minutes wondering why the preview is blank.

What are prebuilds and do they save time?

The answer is yes, and a lot. A prebuild runs your init task whenever you push, then snapshots the container. The next workspace from that commit skips npm install entirely.

On a mid-size React repo, a cold install runs 70-100 seconds. With a warm prebuild it drops to roughly 15 seconds to editor-ready. That is the difference between a tool you use for quick fixes and one you tolerate.

Cost note: prebuilds consume credits even when you never open a workspace. Gitpod’s free tier gives you 500 credits per month (50 hours on a standard workspace), and prebuilds are drawn from the same pool.

Is Gitpod free for personal projects?

Yes, up to 500 credits a month on the free plan, which is about 50 hours of standard 2-core-4GB workspace time. Running out mid-month is common on heavy Docker projects, because Docker-in-Docker workspaces burn credits faster.

Gitpod’s paid plans start at $9 per user per month for more parallel workspaces, and there is a Custom tier for SSO and self-hosted installs. Prices change; check the billing page before budgeting.

When Gitpod is the wrong call

Be honest about this. If your work is a single-file script, a browser IDE is overkill and your laptop is faster. Same if you need a GPU — Gitpod’s standard machines have none.

And there is a lag. Even with prebuilds, typing feels native but command execution has network latency. Heavy npm run test loops on a large suite get old fast. For that, local development or a beefy remote SSH box still wins.

Gitpod is at its best for onboarding a new teammate, reviewing a pull request, or fixing a bug from a borrowed laptop. Which is most of the reason people buy it.

Tuning it so you do not burn credits

  • Set workspaceClass to standard unless you need the memory; the large classes cost double.
  • Turn on prebuilds only for main and long-lived branches, not every PR.
  • Use the gp CLI to stop from the terminal: gp stop.
  • Check Settings → Usage weekly for the first month. You will learn your real burn rate faster than any doc explains it.

Key Takeaways

  • A Gitpod workspace is a container built from .gitpod.yml, tied to one Git branch.
  • Use init for install steps and command for the dev server — mixing them breaks boot.
  • Declare ports explicitly or your preview stays blank.
  • Free tier: 500 credits/month, roughly 50 hours; prebuilds draw from the same pool.
  • Gitpod suits PR review, onboarding and quick fixes; skip it for GPU work or single-file scripts.
Tags: