We just tagged v1.0.1-alpha-15. The headline is the boundary CLI and a completely overhauled bootstrap experience: one curl command installs everything, and boundary new replaces the old boundary-starter workflow.
New: boundary CLI
boundary-cli is a new Babashka library published via bbin that provides a standalone project generator and module installer. It does not require the monorepo — generated projects are fully self-contained.
Install
curl -fsSL https://get.boundary-app.org | bash
The installer handles all prerequisites (JVM, Clojure CLI, Babashka, bbin) and installs the boundary command. macOS, Debian/Ubuntu, Arch Linux, and WSL2 are all supported.
If get.boundary-app.org is unavailable:
curl -fsSL https://raw.githubusercontent.com/thijs-creemers/boundary/main/scripts/install.sh | bash
Bootstrap a new project
boundary new my-app
cd my-app
This scaffolds a complete project with four core modules wired: core, observability, platform, and user. The generated project is immediately runnable.
Add optional modules
boundary add payments # PSP abstraction (Stripe / Mollie / Mock)
boundary add cache # Redis / in-memory caching
boundary list modules # See all available modules
Non-interactive by default
All boundary commands are non-interactive, making them safe for AI agents and CI pipelines. Pass --force to overwrite an existing project directory.
Overhauled installer
The install.sh script received a full overhaul:
-
WSL2 support — Windows users get explicit guidance and a supported install path via WSL2
-
bbin version check — installer upgrades bbin if the installed version does not support
--git/root -
Automatic tag resolution — fetches the latest GitHub release tag via the API; no hardcoded version in the script
-
AI agent tooling — installs
clj-nrepl-evalandclj-paren-repairfromclojure-mcp-lightfor REPL-over-MCP workflows
Documentation
Quickstart and getting-started pages updated to reflect the new boundary new workflow. All boundary-starter references removed from user-facing documentation.
What’s next
The CLI catalogue currently covers 18 optional modules. We will expand this to the full library suite, add a boundary upgrade command, and continue toward beta. Feedback and issues welcome on GitHub.