About — openbis.tech

A platform where the architecture is the product.

openbis.tech is built on the bip-app-framework — a monorepo where every architectural rule is encoded in a manifest and enforced by machine, so the platform stays coherent as it grows.

The bip-app-framework manifest

Rules that enforce themselves

Most platforms drift. A convention holds until someone forgets it, and the codebase slowly loses the shape it started with.

openbis.tech encodes its rules — layering, bounded contexts, tenant isolation, feature shape — in a single manifest, and enforces them with lints and generators on every change. The architecture cannot rot, because the machine will not let it.

Explore the framework →
  1. The rules

    Encoded, not documented

    Layering, module isolation, and feature shape live in a manifest — the single source of architectural truth. Documentation is generated from it, never the other way around.

  2. The enforcement

    Lints and generators

    Every rule is checked mechanically. A change that breaks an invariant fails before it merges — no reviewer has to catch it by hand.

  3. The operators

    Agents and people, together

    AI agents work the repository and the product alongside people, through the same governed surfaces. The platform is built to be operated by both.

Built in the open, for tenants

openbis.tech is a multi-tenant platform first. Every design decision — from row-level security to per-tenant agent credentials — starts from the premise that many customers share one system and none of them should ever see each other.

Analytics, isolation, and agents — on one platform.

See what a platform looks like when the architecture enforces itself.