Run your Jenkinsfile
without Jenkins.

Plumber supports the full Declarative Pipeline syntax for the constructs most teams actually use: stage(), parallel {}, sh/bat/powershell, echo/sleep/error, build job:, @Library(), load, and environment {}. checkout scm runs a real git fetch and clean. withCredentials and archiveArtifacts are logged but not fully executed. post {} is parsed but not yet executed — that's on the roadmap. The Syntax Coverage table on the homepage shows the current status.

No — Plumber runs pipelines entirely locally without any Jenkins server. Optionally, you can connect to a remote Jenkins server via the Jenkins panel to trigger builds, stream live console output, push pipeline scripts directly from the editor, and browse recent build history. The connection is opt-in: if you don't configure it, Plumber never makes any Jenkins API calls.

Pipeline steps run in a clean environment — Plumber only passes through a safe subset of your host environment variables (PATH, HOME, toolchain vars, SSH agent socket). Your personal tokens, API keys, and other secrets are not injected unless you explicitly declare them in the pipeline's environment {} block. withCredentials wrappers are logged but the credential binding itself is a no-op in the current version.

Mostly yes. Once Plumber is installed and your plugins are downloaded, running pipelines works completely offline. The plugin marketplace fetches live data from plugins.jenkins.io when you open it, but it falls back to a local catalogue if the network is unavailable. Tool downloads (via Settings → Environment) require internet access the first time but are cached locally after that.

The marketplace calls the Jenkins Plugin Index API (plugins.jenkins.io/api/plugins) to fetch the top 1,000 plugins sorted by install count, with a 30-minute local cache. Clicking Install downloads the .hpi directly from updates.jenkins.io and imports it into Plumber's plugin registry. Installed plugins expose their declared step names for use in subsequent pipeline runs.

Plumber auto-selects the strongest available sandbox: Linux user namespaces (unshare, for process + PID isolation), macOS Seatbelt (sandbox-exec, filesystem write restrictions), Windows WSL (full Linux namespace stack with an automatic one-time fix for Debian/Ubuntu's stripped Python ensurepip), Windows Job Object (process group tracking and termination), or Clean Environment (minimal env passthrough, available everywhere). You can inspect and override the detected mode in Settings → Sandbox.

Yes. When you open a workspace, Plumber discovers all Jenkinsfiles recursively. The global map view shows every discovered pipeline and the build job: edges between them. You can run any individual pipeline from the sidebar or run the root Jenkinsfile and let downstream pipelines trigger automatically.

Plumber is free to download and use for individual developers. A Pro tier is in development, targeting teams and power users — think cloud sync for settings and pipelines, team workspaces, priority support, and advanced features we haven't announced yet. The core local pipeline execution will remain free.