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 deploy list |
List pending deploys |
baucli deploy approve <id> |
Approve a deploy |
baucli deploy 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/.credentialswith 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
synccaptura 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), obau.tomldeve nascer comunwrap_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
Proprietary — BEG Support © 2025-2026 www.begcloud.com
1 maintainer
Release files for baucli 1.0.110
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| baucli-1.0.110.tar.gz | 641.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| baucli-1.0.110-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.3 MB
Release files / baucli-1.0.110.tar.gz
| Download URL | baucli-1.0.110.tar.gz |
|---|---|
| Size | 641.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
910019a5ebbf3181c446a5b467e81d2bd680b9ced24f834c97cd3e96d1cafb4b
|
|
BLAKE2b-256 checksum How to use checksums |
eb70cf1b2463928db1e37d3e9268bd48784c8e54a5acc368ad51fb04fe71d223
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 29, 2026.
Transparency logRelease files / baucli-1.0.110-py3-none-any.whl
| Download URL | baucli-1.0.110-py3-none-any.whl |
|---|---|
| Size | 647.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7a563f82e7ab411c5f7cdded1507c1301e3572732bc0bb2170c7cef51dbafe5e
|
|
BLAKE2b-256 checksum How to use checksums |
f0bdd584e8318e09d2f356755baf446fe8df756cd115fc287a92aa3d44b5d665
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 29, 2026.
Transparency log
