37 Best Open Source Developer Tools for Every Workflow (2026)

The open source dev tools almost every developer ends up using are Git for version control, an open source editor (Code - OSS through VSCodium, or Neovim), a runtime such as Node.js, a container engine (Podman or Docker Engine), PostgreSQL, and a test runner such as Playwright. For the work around your code (background jobs, data pipelines, approvals, cron jobs), the open source workflow engines to know are Temporal, Apache Airflow, Prefect, Kestra and BullMQ. All of the 37 tools below are free, run locally or self-hosted, and have licenses that allow commercial use. For each one you get the license, what it replaces, its GitHub star count (pulled from the GitHub API on November 4, 2026) and the command to install it.

One correction to the version of this list that used to live on this page: GitHub is not open source. It is a proprietary hosting service built around Git, which is open source. If you want the hosting layer open too, use Forgejo, Gitea or GitLab Community Edition.

For a longer, category-by-category catalog (languages, databases, CI, frameworks), see our companion post on community-built open source software tools. This page is the practical list: what to install, what each tool replaces, and where the licensing traps are.

The short list: 10 open source dev tools

This is the open source software for developers that belongs on almost every machine, whatever language you write.

Frameworks like React (MIT) and Angular (MIT) are open source too, but they're a project decision, not a tool you install once. Our post on open source frameworks compares them.

GitHub stars: how popular each core tool is

Stars are a rough signal of mindshare, not quality, but they tell you how big the community is that writes plugins, answers issues and keeps a tool alive. The numbers below come straight from the GitHub REST API (GET /repos/{owner}/{repo}) on November 4, 2026.

Every repo on this list had commits pushed in the week before we checked, so none of them is abandoned. Podman's repository moved to the podman-container-tools organization; old containers/podman links redirect there.

Why each one made the list

Git

Every other tool on this page assumes you use Git. It's GPL-2.0 licensed, which only affects you if you redistribute modified Git itself; using it on proprietary code is fine. Learn git switch, git restore and git rebase -i early; they replace most of the older, confusing checkout uses. The latest release tag on the git/git mirror is v2.56.0 as of November 2026. If you're new to it, our open source version control guide walks through the first week.

VSCodium (or Code - OSS)

This is the part most lists get wrong. The VS Code source code ("Code - OSS") is MIT licensed, but the VS Code you download from Microsoft is a build that adds telemetry, branding and Microsoft-only extensions, and is distributed under a Microsoft product license. VSCodium ships the MIT source as a ready-made binary without Microsoft's telemetry.

The trade-off: VSCodium uses the Open VSX extension registry, not the Visual Studio Marketplace, and some Microsoft extensions (for example Remote - SSH, Pylance and Live Share) are licensed for Microsoft's builds only. If you depend on those, use Microsoft's VS Code and accept that the editor you run is not open source.

Neovim

If you work over SSH or prefer a keyboard-driven editor, Neovim with its built-in LSP client gives you go-to-definition, completion and diagnostics for most languages. Its license file is Apache-2.0, except for parts contributed under the Vim license. It costs you a weekend of configuration; starter configs like LazyVim (Apache-2.0, 27.8k stars) cut that down.

Node.js

Even if you don't write backend JavaScript, most frontend tooling runs on Node. Use an LTS line. As of November 2026, Node.js 26 ("Lithium") is the newest LTS release: it entered LTS on October 28, 2026 and is supported until April 30, 2029. Node.js 24 moved to maintenance on October 20, 2026 and is supported until April 30, 2028, per the official release schedule.

The release model is changing. Up to Node.js 26, odd-numbered releases never became LTS. Starting with Node.js 27, the project ships one major release a year and every major version moves to LTS after its Current phase. Node 27 is in alpha now and is scheduled for LTS in October 2027.

Vite

Vite is the default dev server and build tool behind most new React, Vue, Svelte and Solid projects. npm create vite@latest scaffolds a project in seconds, and hot reload stays fast as the project grows. It has 83.7k stars on GitHub and ships releases every few weeks.

Podman or Docker Engine

The Docker engine (the Moby project) is Apache-2.0. Docker Desktop is not open source. Per Docker's pricing FAQ, free use is limited to non-commercial open source projects and to companies with fewer than 250 employees and less than US $10 million in annual revenue; government entities always need a subscription. Podman is a daemonless, rootless-by-default alternative that accepts the same commands (podman run, podman build) and reads the same Dockerfiles. On macOS and Windows it runs containers in a small VM through podman machine.

PostgreSQL

The safe default database for almost any new app. The PostgreSQL License is a permissive BSD/MIT-style license, and the project has been independent of any single company for decades, so there's no license-change risk. PostgreSQL 18 is the current major version (18.6 as of November 2026) and is supported until November 2030. PostgreSQL 14 reaches end of life on November 12, 2026, so plan an upgrade if you still run it. Our open source database comparison covers when MySQL or SQLite fits better.

Playwright

Playwright drives Chromium, Firefox and WebKit from one API, waits for elements automatically, and includes a test runner, trace viewer and code generator (npx playwright codegen). It's maintained by Microsoft and Apache-2.0 licensed, with 99.3k stars on GitHub. Version 1.64 was the latest release as of November 2026.

Bruno

Bruno is an offline-first API client. Collections are plain-text .bru files in your repo, so API requests get reviewed in pull requests like code. Hoppscotch (MIT, 80.7k stars) is the browser-based alternative. More options are on our free Postman alternatives page.

OpenTofu

When HashiCorp moved Terraform to the Business Source License in August 2023, the community forked the last open version as OpenTofu, which runs "under the Linux Foundation's stewardship" according to opentofu.org. It reads the same .tf files, and for most projects switching is a matter of replacing the terraform binary with tofu. The current release line is 1.13.

12 more open source developer tools worth adding

The core 10 open source development tools get a project running. These are the tools that make the daily workflow faster: searching code, staging commits, managing Python environments, hosting your own Git, and running AI models without sending code to a third party.

Editors and terminal tools: Zed, lazygit, ripgrep, fzf

Zed is a Rust editor built by Zed Industries; its README says the source is "licensed primarily under GPL-3.0-or-later, with Apache-2.0 components where marked." It starts fast and has built-in collaboration and AI features. If you want something lighter than VSCodium with a GUI, try it.

The terminal trio pays off within a day: rg "TODO" src/ searches a large repo in a fraction of the time grep -r takes and respects your .gitignore; fzf adds fuzzy search to Ctrl+R shell history and file pickers; lazygit lets you stage individual lines, reorder commits and resolve conflicts from one screen.

Python projects: uv

uv replaces pip, virtualenv and pyenv with one binary. uv init, uv add requests and uv run app.py create a project, lock dependencies and run code in an isolated environment without activating anything. It's dual-licensed Apache-2.0 and MIT.

Self-hosted Git: Gitea and Forgejo

Both are lightweight Git forges with pull requests, issues, packages and CI (Gitea Actions and Forgejo Actions use a GitHub Actions-compatible syntax). Gitea is MIT licensed. Forgejo is a GPL-3.0 licensed community fork and powers Codeberg, a free community host. Either runs on a small VPS.

AI tools you can run yourself: Ollama and OpenCode

Ollama downloads and serves open-weight models on your own machine with ollama run <model> and exposes a local HTTP API, so editor plugins and scripts can call a model without sending code to a third party. OpenCode is an MIT-licensed terminal coding agent that works with many model providers, including local ones. It installs with brew install opencode or npm i -g @opencode/cli@latest, per its README.

Backend building blocks: Supabase, Valkey, Infisical

Supabase wraps PostgreSQL with auth, storage, auto-generated REST and realtime APIs, and runs fully local with npx supabase init and npx supabase start (it needs a container engine). Valkey is a BSD-licensed key/value store "backed by the Linux Foundation," per valkey.io, and is the drop-in choice if you want the pre-2024 Redis license. Infisical keeps .env secrets out of your repo and syncs them to CI and servers; its license file puts everything outside ee/ directories under MIT.

Open source workflow automation tools and orchestration engines

The two posts merged into this page were about open source tools to streamline your workflow, and most developers asking that mean one of three jobs: running background jobs and cron jobs reliably, running data pipelines, or wiring services and approvals together. Each job has its own class of open source workflow engine. Picking the wrong class (Airflow for user-facing app logic, or a low-code tool for a pipeline with 400 tasks) is the most common mistake.

Durable execution for app workflows: Temporal, Hatchet, Trigger.dev, Conductor

A durable execution engine records every step of a workflow, so if a worker crashes halfway through, the workflow resumes from the last completed step instead of starting over or silently failing. That's what you want for checkouts, onboarding sequences, provisioning, or anything that waits for hours or days.

Temporal is the most established option. You write workflows as ordinary code and the server persists their state. A TypeScript workflow that charges a card, waits a day and sends a receipt looks like this:

// workflows.ts
import { proxyActivities, sleep } from '@temporalio/workflow';
import type * as activities from './activities';

const { chargeCard, sendReceipt } = proxyActivities<typeof activities>({
  startToCloseTimeout: '1 minute',
  retry: { maximumAttempts: 5 },
});

export async function checkout(orderId: string): Promise<void> {
  await chargeCard(orderId);
  await sleep('1 day'); // survives restarts and deploys
  await sendReceipt(orderId);
}

For local development, the Temporal CLI starts a full server in one command: brew install temporal then temporal server start-dev (Web UI on port 8233). Hatchet and Trigger.dev cover similar ground with less infrastructure: Hatchet uses PostgreSQL as its durability layer, and Trigger.dev focuses on TypeScript jobs that outlive serverless function timeouts.

Python workflow orchestration: Airflow, Prefect, Dagster

If your workflows are data pipelines that run on a schedule, use a Python orchestrator. Apache Airflow is the long-time standard (47.4k stars, Apache Software Foundation project); pip install apache-airflow and airflow standalone give you a local scheduler and UI. Prefect is the lighter choice: decorate existing functions and they become a flow you can run locally with no server at all.

from prefect import flow, task

@task(retries=3, retry_delay_seconds=10)
def fetch(url: str) -> str:
    import httpx
    return httpx.get(url, timeout=10).text

@flow(log_prints=True)
def pipeline():
    html = fetch("https://example.com")
    print(f"fetched {len(html)} bytes")

if __name__ == "__main__":
    pipeline()  # runs locally; add a schedule when you deploy

Dagster models pipelines as data assets rather than tasks, which suits dbt-heavy teams that care about lineage. All three are Apache-2.0.

Declarative orchestration: Kestra and Argo Workflows

Kestra defines workflows in YAML and runs tasks in any language, which makes it a good fit when data engineers, backend developers and ops share one orchestrator. Argo Workflows does the same on Kubernetes: each step is a container, defined as a Kubernetes custom resource. If you already run a cluster, see our guide to container orchestration tools.

Low-code workflow automation: Activepieces, Node-RED, Windmill (and n8n)

These are the open source workflow automation tools worth considering when the job is "when X happens in app A, do Y in app B" and you'd rather not write a service for it.

• Activepieces is the closest open source Zapier replacement: its license file puts everything outside the enterprise directories under MIT.
• Node-RED (Apache-2.0) is flow-based programming in the browser, strongest for IoT and device automation.
• Windmill turns Python, TypeScript, Go or Bash scripts into scheduled jobs, flows and small internal UIs. Its source is AGPLv3 with proprietary enterprise code behind a compile flag, and the official Community Edition binaries include some non-public code, per its license file. Build from source without the enterprise flag if you need a purely open source binary.

Comparing open source BPMN workflow engines

BPMN engines run business processes drawn as diagrams (approvals, claims, order handling) and are usually embedded in Java applications. When you compare them, look at three things: performance under your process volume, extensibility (Java delegates, scripting, external task workers), and community support (release cadence and who maintains it).

• Flowable (Apache-2.0, 9.6k stars) supports BPMN, CMMN (case management) and DMN (decision tables) in one engine and is actively released.
• Operaton (Apache-2.0) is a community fork of Camunda 7. The original Camunda 7 Community Edition repository is now archived on GitHub, so Operaton is the open path for existing Camunda 7 code.
• Camunda 8 is no longer free in production when self-managed. Camunda announced in April 2024 that from version 8.6 (October 2024) self-managed deployments need a production license; most of the current repo is under the Camunda License 1.0, not an OSI license.

Orchestrating complex workflows and cron jobs in a Node.js app

For a Node.js app, you rarely need a separate workflow server on day one. If you already run Redis or Valkey, BullMQ gives you queues, retries, rate limits and cron-style schedules. Job Schedulers replace the old repeatable jobs API and are available from BullMQ v5.16.0, per the BullMQ docs.

import { Queue, Worker } from 'bullmq';

const connection = { host: 'localhost', port: 6379 };
const reports = new Queue('reports', { connection });

// Every day at 03:00: an upsert, so redeploys don't create duplicates
await reports.upsertJobScheduler(
  'nightly-report',
  { pattern: '0 3 * * *' },
  { name: 'build-report', data: { range: 'yesterday' } },
);

new Worker('reports', async job => {
  console.log('building', job.data.range);
}, { connection, concurrency: 5 });

Need a cron pattern? Build and check it with our free cron expression generator. Move up to Temporal, Hatchet or Trigger.dev when a job has several steps that must each succeed exactly once, waits for external events, or runs longer than your workers should hold a lock.

Which open source tool should you pick?

Install the whole set

macOS (Homebrew)

brew install git node postgresql@18 podman neovim opentofu
brew install --cask vscodium bruno

# Daily-workflow extras
brew install ripgrep fzf lazygit uv ollama temporal

# Podman on macOS needs a VM once
podman machine init
podman machine start

Windows (winget)

winget install --id Git.Git -e
winget install --id OpenJS.NodeJS.LTS -e
winget install --id VSCodium.VSCodium -e
winget install --id RedHat.Podman -e
winget install --id Bruno.Bruno -e

Ubuntu / Debian

sudo apt update
sudo apt install git podman postgresql neovim ripgrep fzf
# Node.js: the distro package is often old; use the official installers
# or a version manager such as fnm or nvm instead

Per project (no global install needed)

npm create vite@latest my-app      # scaffold a frontend app
npm init playwright@latest         # add Playwright tests to a project
npm install bullmq                 # queues and cron jobs in a Node.js app
uv add prefect                     # Python workflow orchestration

Check that everything works:

git --version && node --version && podman --version && psql --version

How to judge an open source dev tool before you adopt it

Licenses change. Terraform, Redis, Elasticsearch and others moved from open source to source-available licenses in recent years, which is why forks like OpenTofu and Valkey exist. Before you build on a tool, check:

1. The license file in the repo, not the marketing page. "Open source" on a website sometimes means "source visible". GitHub's API reports NOASSERTION for repos with custom or mixed license files (n8n, Windmill and Infisical all show it), which is your cue to read the file.
2. Who controls it. A foundation (Linux Foundation, CNCF, OpenJS, Apache) is a safer bet than a single startup.
3. Recent activity. Commits and releases in the last few months, and whether issues get answered.
4. The paid edge. Many "open core" tools keep SSO, audit logs or team features in a paid tier. Fine, as long as you know it before you depend on them.

License changes that shaped this list

1. Aug 10, 2023HashiCorp moves Terraform and its other products from MPL-2.0 to the Business Source License (announcement). OpenTofu forks the last MPL version.
2. Mar 2024Redis moves to source-available licensing (SSPL). Valkey, BSD-licensed and backed by the Linux Foundation, becomes the open option.
3. Apr 9, 2024Camunda announces that Camunda 8 self-managed needs a production license from 8.6 (post).
4. Oct 8, 2024Camunda 8.6 ships under the new license; 8.5 and earlier stay usable in production.
5. May 1, 2025Redis adds the OSI-approved AGPLv3 as a license option starting with Redis 8 (announcement).

The lesson: prefer tools whose license is a standard OSI license (MIT, Apache-2.0, BSD, MPL, GPL) and whose governance isn't a single company that could relicense the next version. Where you do use an open core tool, keep its data in open formats (Postgres, plain files, YAML) so moving off it stays cheap.

Our post on open source vs proprietary developer tools goes deeper on these trade-offs. To find newer projects, browse the open source category and the DevOps category on DevHunt, where developers launch and vote on tools every week.

FAQ

What are open source dev tools?

Development tools whose source code is published under a license approved by the Open Source Initiative, such as MIT, Apache-2.0 or GPL. You can use, study, modify and redistribute them, including for commercial work. Git, Node.js, PostgreSQL and Playwright are common examples.

What are the best open source developer tools in 2026?

For most developers: Git, VSCodium or Neovim, Node.js, Vite, Podman, PostgreSQL, Playwright, Bruno and OpenTofu, plus ripgrep, fzf, lazygit and uv for daily work. By GitHub stars on November 4, 2026, the most popular tools on this page are OpenCode (224.5k), the VS Code source (194.6k), Ollama (185.9k) and Node.js (123.2k).

Is VS Code open source?

The source code is: the microsoft/vscode repository is MIT licensed. The VS Code binary Microsoft distributes is not; it's released under a Microsoft product license and includes telemetry and proprietary components. VSCodium is the open source build of the same code.

Is GitHub open source?

No. GitHub is a proprietary service owned by Microsoft. Git, the version control system it hosts, is open source. Open source alternatives for self-hosting are Forgejo, Gitea and GitLab Community Edition.

Are open source dev tools free for commercial use?

Almost always, yes. Permissive licenses (MIT, Apache-2.0, BSD, PostgreSQL) let you use them in commercial work without conditions beyond keeping the license notice. Copyleft licenses like the GPL only add obligations if you distribute a modified version of the tool itself; the AGPL also covers offering a modified version over a network. Source-available licenses (BSL, SSPL, Sustainable Use License) are not open source and can restrict commercial use, so read them.

What are the best open source workflow automation tools?

For integrations between apps, Activepieces (MIT core) and Node-RED (Apache-2.0). For durable workflows in application code, Temporal (MIT). For scheduled data pipelines, Apache Airflow, Prefect or Dagster (all Apache-2.0). For YAML-defined orchestration, Kestra. n8n is popular but uses a fair-code license, not an open source one.

What is the best open source workflow engine for Python and TypeScript?

Temporal has official SDKs for both, plus Go, Java, .NET, Ruby, PHP and Rust, so one server can run workflows written by a Python data team and a TypeScript product team. Hatchet also supports Python and TypeScript. If the Python side is mostly data pipelines, pair a Python orchestrator such as Prefect with BullMQ or Trigger.dev on the TypeScript side.

What open source tools can orchestrate complex workflows and cron jobs in a Node.js app?

Start with BullMQ: it runs on Redis or Valkey and its Job Schedulers handle cron patterns, retries and concurrency. When workflows have multiple steps that must survive crashes or wait for days, use Temporal's TypeScript SDK, Trigger.dev or Hatchet. Kestra works too if you'd rather define the schedule in YAML outside the app.

Is there open source workflow management software for Java?

Yes. Flowable (Apache-2.0) embeds BPMN, CMMN and DMN in Java and Spring Boot apps, Operaton (Apache-2.0) continues Camunda 7, and Temporal has a Java SDK for code-first workflows. Conductor OSS (Apache-2.0) is a JVM-based workflow engine for orchestrating microservices.

Is n8n open source?

Not by the OSI definition. Its code is public on GitHub, but the Sustainable Use License limits use to internal business, non-commercial or personal purposes and restricts offering it to others. Self-hosting it for your own team is allowed; reselling or embedding it is not without a commercial license.

Where can I find open source dev tools on GitHub?

Search GitHub topics such as developer-tools or cli, filter by license, and sort by recent activity rather than stars alone. Curated "awesome" lists help too, and the DevHunt open source category shows new tools as they launch.