Skip to content
[B] BARGO
[ 01 / BARGO ]

Audit-defensible software and research for regulated EU domains.

We build the systems and we research the rules. Compliance SaaS, govtech, regulated B2B — with the architecture and audit trail to back both tracks up, line by line.

When your auditor opens the file, every number resolves to a verbatim source.

Start a conversation See the product →
[ 02 / WHAT WE DO ]

Two tracks. One discipline.

We ship code and we ship written work. Both are produced by the same engine, against the same standard: every claim traces to a source, every artifact survives a read-through.

Track A · We build

Software for regulated domains.

  • 01 · Compliance & regulatory SaaS

    Multi-tenant platforms for CSDDD, CSRD, ETS, CBAM, NIS2, DORA, and adjacent EU regimes. SAP and Power BI connectors, Excel ingestion at 100k-row scale, audit-grade deliverables in the formats regulators actually ingest.

  • 02 · Govtech & public-sector integrations

    EU procurement pipelines, municipal data infrastructure, regulated B2G workflows. Three-layer audit defense (code, runtime, database), full provenance from input through approval.

  • 03 · Regulated B2B marketplaces

    Two-sided platforms with isolated microservices per actor, shadow-catalog caching, fully containerised — runs on your infrastructure or ours. Supply, demand, and catalog state consistent under load.

Track B · We research

Briefs your committee can defend.

  • 01 · Regulatory & legislative briefs

    EU and national legal texts ingested, normalized, and extrapolated into briefs ready for government review. Every claim cites the source verbatim; every cross-reference resolves on disk.

  • 02 · Funding-source mapping

    EU programmes, national instruments, regional grants — mapped against your project's eligible surface, scored against the programme criteria, written up as application-ready material.

  • 03 · Cross-jurisdiction extrapolation

    A binding requirement in one jurisdiction traced across adjacent regimes — directive vs national transposition, implementing acts, court interpretations. What compliance looks like in practice, not on paper.

[ 03 / OUR PRODUCT ]

We don't just consult. We ship.

UNBIN

v6.26.0 · design-partner phase

  • 15 products
  • 4 categories
  • multi-tenant SaaS
  • signed PDF · JSON-LD · iXBRL · XML
  • ISAE 3000-aligned

regimes covered
CSRD · ETS1 · ETS2 · CBAM · ESPR · EnergyTag

UNBIN is our own product — a 15-product audit-grade reporting suite for EU sustainability and emissions compliance, currently in design-partner phase. The suite spans four categories: hourly energy attestation (Scope 2, 24/7 CFE matching, Granular GO issuance), corporate inventory (CSRD ESRS E1-5 and E1-6, intensity metrics, iXBRL, Digital Product Passport), market & regulatory filings (EU ETS1 and ETS2 MRV, CBAM, audit bundle), and a verification layer that lets any calculation be replayed years later, byte-for-byte.

A services pitch is only as honest as the work behind it. UNBIN is the work behind ours. It exists because we needed to know — concretely, in code, not in conversation — what it takes to ship regulatory output that a Group-1 reporter, a Big-4 auditor, and an EU regulator can all read off the same artifact. The answer is specific: per-calculation factor snapshots, cryptographic hashes on every output, on-disk archives of every cited regulation, and per-regime schema adherence that takes a quarter to build for any one regulation — and we now have it for the ten that matter most.

● unbin.eu / dashboard / energy
Disclosures published
+ 11 / day
Citations grep-verified
24 h
Factor snapshots locked
cumulative
Compliance coverage
%
ESRS E1
Hourly Scope 2 attestations · last 24h ENTSO-E zone · LV
Last engine run · live tail verified
  1. 09:59:43.571 OK factor snapshot locked · IEA · 2026Q2 · sha 9c1f…3b
  2. 09:59:43.629 RUN claim-grounding-guard · 412 citations · 412 grep-matched
  3. 09:59:43.845 OK cross-methodology differential · GHGP · ISO 14064 · agree
  4. 09:59:44.068 OK disclosure 1247 sealed · ISAE-3000 envelope · published
Underlying topology
UNBIN — 15-product reporting suite Tenant data, regulation archives, and emission-factor databases feed the UNBIN engine, which produces 15 audit-grade reporting products across 4 categories. [ inputs ] tenant data regulation PDFs factor DB / MEF ENTSO-E / AIB [ engine ] UNBIN engine v6.26.0 claim-grounded [ products · 15 total ] Energy 6 products Scope 2 · GO issuance · 24/7 CFE · CZC-proof Corporate 4 products GHG inventory · intensity · iXBRL · DPP Market / Regulatory 4 products ETS1 MRV · ETS2 · CBAM · Audit Pack Verification 1 product Replay [ output formats ] signed PDF · JSON-LD · iXBRL · AIB-Hub XML · ISAE 3000-aligned
UNBIN · 15-product reporting suite · 4 categories · per-regime outputs

UNBIN runs on its own brand and will move to its own site at launch. It is referenced here as evidence of capability, not as a product for sale on bargo.lv. The full catalog — currently 15 products and growing — lives on the UNBIN side of the house, and that conversation has not opened yet.

[ 03b / RESEARCH ]

Briefs we've already written.

6 audit-defensible briefs published by our UNBIN product team — every claim cites its source, every cross-reference resolves to a verbatim passage in EUR-Lex or the relevant methodology standard. Read before the discovery call. No email gate.

CSRD ESRS E1 Timeline 8 min

CSRD timeline 2026 — which wave, which year, what to file

Definitive CSRD reporting timeline by company size. ESRS E1 data point requirements and what auditors expect across Wave 1, Wave 2, Wave 3 cohorts.

For: CFO · Chief Sustainability Officer

ESRS E1 Climate disclosure 12 min

ESRS E1 in plain language

Every climate-disclosure point named, every metric defined, every cross-reference resolved against OJ L 2023/2772.

For: Chief Sustainability Officer · Audit partner

CBAM Importer 6 min

CBAM importer guide

Transitional-to-definitive period change from 2026-01-01, embedded-emissions calculation, declaration format, and what auditors check.

For: Regulated B2B · Procurement

GHG Protocol Methodology 10 min

GHG Protocol explained

Scope 1, 2, 3 boundary rules, the Corporate Standard and the Scope 3 Standard, and what changed in the recent Scope 3 revisions.

For: CSO · IT Director · Audit partner

ESPR DPP Battery 7 min

Digital Product Passport — battery passport guide

ESPR battery-passport substrate — schema, data-provenance pattern, QR carrier, public viewer architecture. Feb 2027 mandate.

For: Product · Engineering · Compliance

Methodology Audit evidence Golden tests 14 min

Calculation methodology · audit evidence pack

Every formula, the cascade lookup engine, golden-test results (24/24 passing), 99.5% factor-match rate cross-checked against DESNZ, ADEME, EPA.

For: Big-4 audit partner · Methodology reviewer

[ READING ROOM · REFERENCE DESK ]

Don't want to read all six? Ask [B]ob, our reading-room desk, about any regime we cover — CSRD, ESRS, CBAM, CSDDD, EU ETS, NIS2, DORA. Every answer quotes the verbatim source. Or it tells you it can't.

Under NIS2, what's the deadline to report a significant incident?
[B]

An early warning is due within 24 hours of becoming aware of the incident.

"…without undue delay and in any event within 24 hours of becoming aware of the significant incident, an early warning…"
Source NIS2 · Article 23 (CELEX 32022L2555)
What's the VAT registration threshold in Latvia?
[B]

I can't answer that from BARGO's published material — we don't hold Latvian national tax law. For that, write to gunars@bargo.lv.

Ask the reference desk

Example exchanges. [B]ob answers only from BARGO's published research and the verbatim EU texts on file.

These briefs follow the same principles as our regulated-domain builds. The methodology is open; the artifacts are signed by BARGO, SIA. Spot something you want a longer answer on? Start a conversation.

[ 03c / PROOF OF WORK ]

A real deliverable. Five days. Our cost.

Once a quarter we take on a proof-of-work sprint. Pick a real slice of your compliance work — we build it in five business days with the same audit-trail discipline that's in every paid engagement. Scope is agreed in a 30-minute call before the sprint starts.

You keep what we build. Whether the relationship continues is your call.

Example slices

  • ESRS E1 disclosure-readiness review Pick one data point in your draft narrative; we cite it back to OJ L 2023/2772 line by line and flag what your Big-4 reviewer will challenge.
  • CBAM importer-flow audit One product line, transitional-to-definitive (from 2026-01-01). Embedded-emissions calc, declaration format, where the audit trail sits.
  • Cross-jurisdiction trace One binding requirement (CSDDD / NIS2 / DORA / ESPR), traced across the EU directive plus 2-3 national transpositions, with divergence flagged.
Tell us your slice One sprint per quarter
[ 04 / EVIDENCE ]

Selected engagements in production.

One government research engagement under NDA, and two builds in production. We can walk through architecture, deliverables, and trade-offs in conversation.

Case · 01 · Research · Confidential

Government-facing regulatory research engagement

A government engagement requiring rapid synthesis of a multi-domain regulatory framework — directives, implementing acts, applicable case interpretations — into briefing material the client can defend in front of a committee. Multiple deliverables produced under NDA over the past quarter. Every cited paragraph grep-verified against on-disk source texts; every interpretation anchored to a paragraph number; every cross-reference resolves before the document leaves the engine.

Citations verified
Source PDFs indexed
Cross-refs resolved
Drift errors caught
good

Confidential engagement — domain abstracted by mutual agreement.

Case · 02 · Build

EU procurement-intelligence pipeline

EU public-procurement runs on the TED data feed — every contract notice from every Member State in one firehose. Pure-LLM filtering is expensive and fuzzy at scale; pure-rules-based filtering misses everything outside the keyword catalog. We built a two-stage filter on a Node/Postgres pipeline: stage one is a deterministic capability-manifest that rejects obviously-irrelevant tenders for zero LLM cost; stage two is an LLM pass over the survivors — the only data worth the spend. A React operator console keeps a human in the loop on every promotion. Three independent audit layers — code, runtime, database — record every rejection, every promotion, every operator decision. Nothing leaves the system without a provenance trace.

Tender-parser architecture EU-27 procurement feed ingests into Postgres, passes a deterministic capability-manifest filter chained with an LLM second pass, then an operator console gates the published bid draft. [ source ] TED feed manifest filter LLM pass operator UI [ audit ] code-layer checks runtime guards DB triggers

Internal system — no business figures shared.

Case · 03 · Build

B2B parts marketplace

A two-sided marketplace matching specialist buyers with parts suppliers, built for an established community brand. Three isolated microservices (customer, supplier, admin) behind a single edge, React 19 on the front, Postgres and Redis behind, fully containerised and deployed to production. A three-layer shadow-catalog cache keeps response times flat without hammering the upstream OEM source.

Classic marketplace architecture Nginx routes to three isolated microservices (customer, supplier, admin). They share Postgres and Redis behind. Deployed via Docker to production. [ edge ] nginx · TLS [ services ] customer api supplier api admin api [ data ] postgres 16 redis 7

Build partner — staged and operational.

[ 05 / HOW WE WORK ]

Experience, decisions — augmented by AI agents.

The interesting question in 2026 is no longer "can a single senior engineer build a regulated system end-to-end." It is "can they do it without cutting the corners that get caught in an audit." Our answer is: yes, with in-house tooling that does the parts a junior team would do — drafting, cross-checking, source-grounding, regression — and a single principal architect doing the parts a senior would never delegate. Architecture, regulatory mapping, schema decisions, the calls that determine whether the thing is correct.

Every claim in a deliverable traces back to a source. Every calculation is reproducible. Every schema change is versioned in three places, not one. Every regulated artifact — a disclosure, a bid, a report, an integration contract — has a provenance trail you can read top to bottom. This is the part we don't compromise on, regardless of project size.

We don't sell speed in isolation. We don't sell head-count. We don't sell "AI" as a noun. We sell software that does what it says, in a domain where the cost of being wrong is paid by the customer's board, the customer's regulator, or the customer's lawyer — not by the vendor.

[ 06 / CONTACT ]

Let's discuss your project.

We take only a few engagements a year so each one receives principal-architect attention from the first call through deployment. If your problem lives in compliance, govtech, or regulated B2B — anywhere "must be correct" is a tighter constraint than "must ship next quarter" — we'd like to hear about it. Most engagements run alongside your existing Big-4 advisor or in-house compliance team — we don't require a replacement decision.

Start a conversation gunars@bargo.lv Available for Q4 2026 engagements