Open source · Reporting as Code

Reporting as Code. Strictly IBCS®.

Stop building reports by hand. Define them in YAML, query with SQL, and generate pixel-perfect, IBCS-compliant PDFs — version-controlled and reproducible.

Get started 🚀Why bino?

bino-bi/bino-cli5$ brew install bino-bi/tap/bino-cli

Products

One workflow, three tools

Open source at the core — build, try, and share IBCS reports as code.

bino cliOpen source

IBCS reports from YAML + SQL

$ brew install bino-bi/tap/bino-cli

Learn more→GitHub

bino sandbox

Report-as-code runtime in the browser

Learn more→

bino registry

Share report definitions with the community

$ bino registry add @acme/base-layout

Learn more→

From YAML to PDF

Define. Build. Ship.

A data source, a query, a table — and a pixel-perfect, IBCS-compliant result. Both halves below are real: the file is a live sandbox, the render is what it produced. The same pipeline runs on your laptop and in CI.

apiVersion: bino.bi/v1alpha1
kind: DataSource
metadata:
  name: new_cities
spec:
  type: csv
  path: https://sandbox.bino.bi/api/data/new_cities.csv
  delimiter: ";"
---
apiVersion: bino.bi/v1alpha1
kind: DataSet
metadata:
  name: new_cities_ds
spec:
  query: |-
    SELECT *
    FROM new_cities
    WHERE year(date) = 2025
    OR year(date) = 2024
  dependencies:
    - new_cities
---
apiVersion: bino.bi/v1alpha1
kind: Table
metadata:
  name: cities_table
spec:
  dataset: new_cities_ds
  type: sum
  sumTitle: Revenue by city
  scenarios:
   - ac1
   - pp1
  variances: ["dpp1_ac1_pos"]
  barColumns:
   - "dpp1_ac1_pos"
  interval: year
  unitScaling: 20