Install something
5 of Hilbras’s products are published to npm, all under the MIT licence, and each is usable on its own. Every version below was read from the npm registry on 2026-09-30.
Published packages
No account, no bundle and no other Hilbras package is required to use any of these. Each one is a standalone product with its own release history.
- Hilbras KeystoneStableAn API-first identity and authentication platform.
@hilbras/keystonev3.5.3 · MITnpm install -g @hilbras/keystone - OmniHilbrasBetaRouting and provider management for model traffic.
@hilbras/omnihilbrasv1.30.0 · MITnpm i @hilbras/omnihilbras - Hilbras RememberaStableDurable memory for AI assistants, outside the context window.
@hilbras/remembrav5.6.0 · MITnpm install -g @hilbras/remembra - Hilbras SDKStableA provider-agnostic LLM client SDK for TypeScript.
@hilbras/sdkv3.2.0 · MITnpm install @hilbras/sdk - Hilbras CodeAlphaA coding agent for web, desktop, CLI, and editor.
hilbras-codev0.1.0 · MITnpm install -g hilbras-code
What is not on a registry
The other 6 products have no published package. They are listed here so the absence is stated rather than left to be discovered — a developer looking for something to install should not have to guess whether a page simply forgot to mention it.
- HilPressAn extensible application and content runtime.
- Hilbras StudioA goal-driven runtime that plans, schedules, and publishes.
- Hilbras GatewayA single edge in front of every model provider.
- Hilbras OSA desktop operating system with its own shell and services.
- HilGitCode collaboration and community around a project.
- Hilbras SpectraA modular security testing and analysis platform.
Running from source instead? Every product links its repository on its own page, and each carries its own licence and build instructions in its README.
None of these depend on each other
That is not a slogan, it is an audit. Every manifest in the Hilbras organisation was read, and the only cross-reference between them is an internal package inside a single repository. Installing one of these pulls in zero Hilbras dependencies, and the versions above are genuinely independent of one another.
OmniHilbras is the exception that proves the rule: its gateway is a multi-surface runtime that speaks to providers, not a wrapper around the other packages here.