Building across AI infrastructure, developer infrastructure, platforms, social technology, computing, and security.
Independent productsBring your own infrastructureOpen where it matters
hilbras / ecosystem
six technology areas · eleven products
Every product stands on its own. The connections are an option, not a requirement.
See how it connectsHilbras is an independent company building software products and infrastructure across several areas of modern computing. Some of them are infrastructure you install. Some of them are applications you use. They share a company, not a runtime.
Each project is designed to be worth installing on its own, with a clear job and a maintainable surface.
Shared identity, shared routing, shared memory. Integration is a bonus you can take, not a dependency you inherit.
The ecosystem is organised by what the technology does, not by when it shipped. A product can sit in more than one area — that is usually the interesting part.
The layer between an application and a model. Execution engines, unified gateways, routing policy, and durable memory for assistants that have to keep working after a context window ends.
The parts every product needs and no product should reinvent. Authentication and authorization, focused coding environments, and the places where code gets written and reviewed together.
Extensible platforms for building and operating real products. A content and application runtime, and a runtime that plans and carries out work across the accounts a team already owns.
Where Hilbras software meets other people. Distribution, collaboration, and community infrastructure built for the people shipping the technology rather than for engagement metrics.
The environment everything else runs in. A desktop operating system, its shell and system services, and the native applications that make it a place to work rather than a launcher for a browser.
Software that finds out what is wrong with software. Target management, discovery, scanning, verification, and reporting — for authorised testing and internal review.
Four products lead the ecosystem today. The rest are earlier, and four of those seven already have a public repository — so you can follow the shape of the company as it grows.
AI Infrastructure
A provider-agnostic LLM client SDK for TypeScript. Streaming, tool calling, structured output, circuit breaker, retry, and cost enforcement across OpenAI, Anthropic, Gemini, Azure, Groq, and Ollama — with zero runtime dependencies.
AI Infrastructure
External memory for AI assistants. Facts, decisions, roles, and history live outside the context window, and only the authorised, relevant subset comes back. Speaks MCP, HTTP, and TypeScript.
Developer Infrastructure
An API-first identity and authentication platform. OIDC and OAuth 2.0, a JWT token authority, RBAC and ABAC, WebAuthn passkeys, a federation broker, and an immutable audit log.
AI Infrastructure
Routing and provider management. Health checks, retries, and fallbacks decide which model serves a request, the local gateway keeps your keys on your own machine, and every decision stays readable afterwards.
Platforms
An extensible application and content runtime. Users, roles, content, revisions, taxonomy, media, and a plugin system with manifests, lifecycle hooks, and permissions.
Platforms
A goal-driven AI runtime. Give it a goal; it plans the work, schedules it, and publishes across X, Instagram, Facebook, Threads, and Telegram — pausing where a person has to approve.
AI Infrastructure
A single edge in front of every model provider. One endpoint, one key, and one place to decide where a request is allowed to run.
Computing
A desktop operating system with its own shell, dock, workspaces, and system services — an environment for Hilbras software rather than a rebrand of the base system.
Developer Infrastructure
A coding agent with one core and four surfaces — web, desktop, CLI, and editor. A streaming agent loop, filesystem and shell tools, and a permission layer that fails closed.
Social Technology
Code collaboration and a working community around it. Review, discussion, and the shared record of what a project is and why it looks the way it does.
Security
A modular, extensible security testing and analysis platform — a 21-crate Rust workspace covering target management, discovery, fingerprinting, scanning, verification, and reporting.
Read this as an ordering of the work, not a set of dependencies. Every box is useful on its own. Connecting two of them is where the extra value appears.
01Foundation
Identity, access, and the audit trail everything else assumes.
02Intelligence
Reaching models, controlling the route, and keeping what matters.
03Application
Runtimes, automation, authoring, and collaboration.
04Environment
The computing surface, and the tooling that inspects it.
A connected product is still a standalone product.
If you only ever install one thing from this list, the diagram still holds. It is a map of where value can be added, not a list of things you are required to install.
Six areas, described in terms of the work rather than the product name. Most projects in the ecosystem live in more than one of them.
Model access, routing, memory, and runtime control.
Identity, authoring environments, and code collaboration.
Application runtimes, content systems, and automation.
Publishing, communities, and developer-first networks.
Operating systems, desktop environments, native apps.
Analysis, testing, and inspection tooling.
You should be able to find the part of Hilbras that matters to you without reading the other two.
Build on modular infrastructure instead of assembling it yourself.
Every Hilbras product is usable on its own. Take the SDK, or the gateway, or identity, and keep the rest of the surface out of your way until you want it.
Technology designed around integration, extensibility, and automation.
Hilbras systems are meant to sit inside existing operations. They expose stable interfaces, keep your data where it belongs, and can be automated without a bespoke integration layer.
Create, publish, automate, and manage digital content.
Platforms and runtimes for the people who need to publish consistently. Connect the accounts you already have, describe what you want, and keep control of what goes out.
Not slogans. These are the rules we use to decide whether a Hilbras project is finished.
Every Hilbras product has to be worth installing on its own. If a project only makes sense next to another one, it is not finished yet.
Integration should add value, not obligation. Products interoperate because the interfaces are good, not because they are bundled.
The person reading the logs should be able to understand the system. Control, visibility, and escape hatches come before convenience.
Foundations outlast features. We would rather ship a smaller surface that stays correct than a large one that quietly rots.
Where a Hilbras project can be transparent, interoperable, and community-welcoming, it is — starting with the parts developers have to depend on.
Hilbras is not one application. The long-term work is a technology ecosystem, built in the order the layers actually depend on each other.
Identity
Knowing who is asking, and what they are allowed to do.
AI
Reaching models through infrastructure you control.
Memory
Keeping what matters past the end of a session.
Applications
Runtimes that turn infrastructure into products.
Automation
Work that runs on a schedule, with humans in the loop.
Development
Tools for building the next piece of the ecosystem.
Collaboration
Shared work, review, and community.
Computing
The environment all of it runs in.
Explore the Hilbras ecosystem and find the technologies we are building for developers, businesses, and creators.
Actively developedYour infrastructure, your keysNo bundling required