BAUCLI

Business-logic context for your databases — kept true to production.

BAUCLI runs on the developer's machine. It connects to Oracle, PostgreSQL, MySQL and SQL Server, extracts the real structure and PL/SQL logic, and turns it into documentation that is reviewed by people and consumed by AI — then writes it back where it belongs: COMMENT ON in the database and context files in your repository.

Because the context is extracted from the live database on every sync, it does not drift away from what is actually deployed. That is the difference between documentation you trust and documentation you stopped reading.

It is the local component of the BAU platform (BEG Application Utilities), which stores the catalog, runs the AI drafting and holds the approval workflow.

Quick Start

# Install
pip install baucli

# or with all database drivers
pip install baucli[all]

# Activate license
baucli init --license BAU-XXXX-XXXX-XXXX-XXXX

# Add a database
baucli connect --name dev_oracle --engine oracle \
  --host localhost --port 1521 --service XEPDB1 --user DEMO_HR \
  --schemas DEMO_HR

# Sync objects to BAU Server
baucli sync

# Download AI context for your IDE
baucli context

Commands

Command	Description
`baucli init --license <key>`	Activate license, receive API key
`baucli connect --name <alias> ...`	Add and test a database connection
`baucli sync [--db name \| --all]`	Sync objects to BAU Server
`baucli context [--db name]`	Download AI context (CLAUDE.md)
`baucli status`	Show config, quota, pending deploys
`baucli documentation list`	List pending deploys
`baucli documentation approve <id>`	Approve a deploy
`baucli documentation apply <id>`	Download and apply deploy script
`baucli db list`	List configured databases
`baucli db remove <name>`	Remove a database
`baucli db default <name>`	Set default database

Multi-Database Support

Configure multiple databases in ~/.baucli/config.json:

# Add Oracle dev
baucli connect --name dev_oracle --engine oracle --host localhost --port 1521 --service XEPDB1 --user HR

# Add PostgreSQL staging
baucli connect --name staging_pg --engine postgresql --host pg-staging --port 5432 --database erp --user app_user

# Add SQL Server production
baucli connect --name prod_mssql --engine mssql --host sql-prod --port 1433 --database erp --user bau_reader

# Sync specific database
baucli sync --db staging_pg

# Sync all
baucli sync --all

# Set default
baucli db default dev_oracle

Supported Databases

Engine	Driver	Install
Oracle 19c+	oracledb (thin mode)	`pip install baucli` (included)
PostgreSQL 14+	psycopg	`pip install baucli` (included)
SQL Server 2019+	python-tds	`pip install baucli` (included)
MySQL 8.0+	mysql-connector	`pip install baucli` (included)

Configuration

Config file: ~/.baucli/config.json

{
  "license_key": "BAU-XXXX-XXXX-XXXX-XXXX",
  "api_url": "https://begbrokerdev.begcloud.com/ords/bauctx/api/v1",
  "api_key": "bau_cli_xxxx",
  "tenant_code": "ACME_CORP",
  "default_db": "dev_oracle",
  "databases": {
    "dev_oracle": {
      "engine": "oracle",
      "host": "localhost",
      "port": 1521,
      "service": "XEPDB1",
      "user": "DEMO_HR",
      "schemas": ["DEMO_HR"]
    },
    "staging_pg": {
      "engine": "postgresql",
      "host": "pg-staging.internal",
      "port": 5432,
      "database": "erp_hml",
      "user": "app_user",
      "schemas": ["public", "hr"]
    }
  },
  "sync_interval_min": 30,
  "context_output": "CLAUDE.md"
}

Passwords are stored separately in ~/.baucli/.credentials (restricted permissions).

Override config dir with BAUCLI_HOME=~/.baucli-tenant2 to keep multiple isolated profiles on the same machine.

Security

Database credentials never leave the developer's machine
Only extracted metadata and source code are sent to BAU Server via HTTPS
API key uses SHA256 hash — plain token shown once at baucli init
Passwords stored in ~/.baucli/.credentials with mode 600 (or OS keychain when available)
BAU Server never executes DDL on your database

Requirements

Python 3.9+
Network access to BAU Server (HTTPS)
Database access (read-only on DBA_SOURCE, DBA_TABLES, etc.)

Unwrap de PL/SQL (opt-in)

O sync/extract sabe reverter o wrap do Oracle (10g/11g/12c) para documentar objetos ofuscados — é o que permitiu documentar os ~90% de units wrapped em catálogos legados. Vem DESLIGADO por padrão: distribuir um deobfuscator tem implicação de propriedade intelectual (o wrap é do fornecedor do cliente), então cada projeto liga explicitamente, declarando ter direito sobre o código-fonte.

Ligar por projeto no bau.toml:

unwrap_enabled = true

Ou por sessão via env: BAUCLI_UNWRAP=1. Quando ligado, db/oracle.py::extract_objects desempacota via baucli/unwrap.py (is_wrapped → unwrap_source) antes do CREATE OR REPLACE; unit em formato 9i/corrompido é mantido wrapped (não fatal). Não cobre o formato 9i.

⚠️ Num schema com objetos wrapped, o flag PRECISA estar ligado antes do sync. Com o gate OFF, o sync captura o texto wrapped e o grava por cima da documentação — corrompendo o catálogo em silêncio. Por isso, num projeto cujo alvo tem PL/SQL wrapped (ex.: Exatron/ODIN), o bau.toml deve nascer com unwrap_enabled = true, e o smoke test antes do primeiro sync real é: BAUCLI_UNWRAP=1 baucli sync --dry-run --object <objeto_wrapped> → deve voltar UNCHANGED. (Se rodar o dry-run SEM o flag, o UNCHANGED é falso — ele nem tentou desempacotar.)

License

Metadata

Release files for baucli 1.0.148

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for baucli 1.0.148
File	Size	Uploaded	Provenance
baucli-1.0.148.tar.gz	887.4 kB	Oct 21, 2026	With provenance	Details

Built distribution (wheel)

Table of built distributions (wheels) for baucli 1.0.148
File	Interpreter	ABI	Platform	Reset
baucli-1.0.148-py3-none-any.whl 802.4 kB Oct 21, 2026 With provenance	Python 3	none	any	Details

Total release size: 1.7 MB

Release files / baucli-1.0.148.tar.gz

Download URL	baucli-1.0.148.tar.gz
Size	887.4 kB
Tags	Source
SHA-256 checksum How to use checksums	`d3f311bb3d4b1dad01552722a4d27a09b77815c44fbc0c41831965e3898897d9`
BLAKE2b-256 checksum How to use checksums	`778cc73a0af8aeb585ee3078e0f481f29cf3693287ea4c55cdae8a9305564892`
Upload date	Oct 21, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/7.0.0 CPython/3.13.16`

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/begsupport/baucli
Publishing commit: github.com/begsupport/baucli/tree/12f096576bbe11b90d65e84ca250edda1a7c3967

Workflow

Publishing configuration: github.com/begsupport/baucli/blob/12f096576bbe11b90d65e84ca250edda1a7c3967/.github/workflows/ci.yml
Publishing logs: github.com/begsupport/baucli/actions/runs/39526692621/attempts/1

Artifact

Subject: baucli-1.0.148.tar.gz
SHA-256 checksum: d3f311bb3d4b1dad01552722a4d27a09b77815c44fbc0c41831965e3898897d9 Verifying attestations

Release files / baucli-1.0.148-py3-none-any.whl

Download URL	baucli-1.0.148-py3-none-any.whl
Size	802.4 kB
Tags	Python 3
SHA-256 checksum How to use checksums	`d240c1a32ebd69fedf8da2a988ac29970064ab51d95972e61db4802ca58ec589`
BLAKE2b-256 checksum How to use checksums	`c25c495aac91260f74ed27da6cd8f6df5d5057200d123267ffde1f35e830231a`
Upload date	Oct 21, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/7.0.0 CPython/3.13.16`

Provenance

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/begsupport/baucli
Publishing commit: github.com/begsupport/baucli/tree/12f096576bbe11b90d65e84ca250edda1a7c3967

Workflow

Publishing configuration: github.com/begsupport/baucli/blob/12f096576bbe11b90d65e84ca250edda1a7c3967/.github/workflows/ci.yml
Publishing logs: github.com/begsupport/baucli/actions/runs/39526692621/attempts/1

Artifact

Subject: baucli-1.0.148-py3-none-any.whl
SHA-256 checksum: d240c1a32ebd69fedf8da2a988ac29970064ab51d95972e61db4802ca58ec589 Verifying attestations

Security for baucli 1.0.148

Report project as malware

Provenance

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Attestation for baucli-1.0.148.tar.gz

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/begsupport/baucli
Publishing commit: github.com/begsupport/baucli/tree/12f096576bbe11b90d65e84ca250edda1a7c3967

Workflow

Publishing configuration: github.com/begsupport/baucli/blob/12f096576bbe11b90d65e84ca250edda1a7c3967/.github/workflows/ci.yml
Publishing logs: github.com/begsupport/baucli/actions/runs/39526692621/attempts/1

Artifact

Subject: baucli-1.0.148.tar.gz
SHA-256 checksum: d3f311bb3d4b1dad01552722a4d27a09b77815c44fbc0c41831965e3898897d9 Verifying attestations

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.