LeanVault

Open source / 04 repos

Projects we maintain in public

Four tools we run ourselves: an AI gateway client, a release console, an LLM integration SDK and a codebase understanding workbench. MIT unless stated otherwise.

ID

Every repository below states its own license. Star the organization to follow along.

01

clawchat

MIT

A direct WebSocket client for your OpenClaw gateway. No backend, no message limits, one codebase for every platform.

Dart / Flutter Active View on GitHub
02

deploy-box

MIT

A release control plane for Docker projects: onboarding, image packaging, version publishing and remote deploy tracking in one console.

Python / Docker Active View on GitHub
03

llm-hub

MIT

A lightweight frontend LLM SDK: register providers, pick a model, test access, then reuse it in code. Ships with an embeddable config UI.

TypeScript / SDK Active View on GitHub
04

loci

UNLICENSED

A local-first workbench for reading a codebase: it indexes the repository into a graph, links code to git history and design decisions, then answers from that evidence.

Rust / Tooling Active View on GitHub

License is stated per repository. A repository without one is not open source — treat it as all rights reserved until a LICENSE file lands.

Open the organization on GitHub

Standards

01

Documentation first

Every repository ships with a README that explains what it is not, too.

02

Tests as spec

Behaviour is pinned by tests, so releases are boring by design.

03

Changelog kept

Every release notes what broke and why, including our mistakes.

04

Licenses stated

Each repository names its own license in the register, so you always know what you are allowed to do.