WalisA CI/CD server that fits on one machine

No repo required, no containers required, no runtime to install. It even updates itself.

No prerequisites

Jenkins needs a JVM and a plugin ecosystem. Woodpecker needs a Git forge and containers. Walis needs a machine and a shell script.

Every step keeps its own status, log, exit code and duration. Output streams live while the build runs, locally and on remote agents alike.

Builds run in a macOS sandbox that cannot read the Walis data directory — no database, no password hashes, no cloud keys.

A plugin produces a shell snippet, not behaviour. You can read exactly what it will run before you install it.

The API speaks MCP, so Claude Code or Codex can trigger a build, wait for it and read the log — with a scoped API key.

A built-in job pulls, builds a new release, swaps a symlink and asks a separate daemon to restart the service.