DVB · DataVaultBrain Live

A brain that refuses to talk about you.

DVB is the anonymizing intelligence mesh behind the JARBIZ apps. Your apps push price observations in. What comes back out is one rounded market signal — median, min, max and a count — and only once enough independent sources agree that nobody can be picked out of it.

Visit dvb.redis4u.com Join the waitlist
  • Push-only · never queryable by tenant
  • ≥ 2 sources, ≥ 3 samples before release
  • $0.50 rounding
Render of the DVB neural core Observations stream in from REDIS.4U, InvoiceIQ and HUNTER along push-only wires. At the outer membrane each observation sheds its colour, meaning its source identity. Inside, a vault-like neural core pools them. A single rounded aggregate price signal, showing median, min, max and n, leaves on the right. A dashed red return path back to the apps is crossed out: the core cannot be queried by tenant. REDIS.4U DISTRIBUTOR CORE INVOICEIQ INVOICE PHOTOS HUNTER INSIDE REDIS.4U DVB GET /PRICE-SIGNAL ONE AGGREGATE median · min · max · n ROUNDED TO $0.50
Render · colour is identity. It is stripped at the membrane.

How a price signal is born

Five steps. No shortcuts around them.

Every number DVB releases goes through the same sequence. If a product can't clear the gate, nothing is released for it at all — no partial answer, no “close enough.”

  1. Ingest

    POST /ingest

    Apps push batches of up to 500 price observations. The flow is one-way: DVB receives, and it is never queried by tenant.

  2. Canonicalize

    The same product written a dozen ways collapses into one canonical item, so a supplier’s shorthand and a full catalog name count toward the same signal instead of splitting it.

  3. Gate

    No signal until at least 2 independent sources and 3 samples agree, inside a 365-day window. One supplier’s price can’t be read back out, because one supplier’s price is never released.

  4. Round

    Released prices are rounded to the nearest $0.50, so an exact figure can’t be matched back to a single invoice.

    $38.37$38.50

  5. Release

    GET /price-signal

    What comes out is the median, min, max and n. No source, no tenant, no invoice.

Illustrative values and annotations, not live data. The response shape — median, min, max, n — is what the endpoint returns.

The AKA dictionary

Kitchen slang, translated.

Chefs and buyers don’t write catalog names. DVB keeps a shared nickname dictionary that maps the words people actually use to one canonical product.

A nickname only resolves once at least two sources use it — k-anonymity ≥ 2. A word that only one kitchen says stays private, so a nickname can never fingerprint the business that coined it.

POST /akateaches the mesh an alias → canonical name
GET /aka/resolvereturns a canonical match, at k-anonymity ≥ 2
ALIAS → CANONICALILLUSTRATIVE
  • evooExtra virgin olive oilk ≥ 2
  • APAll-purpose flourk ≥ 2
  • rom heartsRomaine heartsk ≥ 2
  • heavyHeavy creamk ≥ 2
  • house goldHeld — only one source uses itk = 1

Sovereignty audit

The endpoints that do not exist

Most APIs tell you what they do. DVB also publishes what it will never do. The five sealed endpoints below were never built, and the status page lists them under “We won’t build.” That list is part of the product.

DVB · API MANIFEST dvb.redis4u.com

Exposed

5
  • POST/ingestaccepts ≤ 500 observations
  • GET/price-signalreturns median · min · max · n
  • POST/akateaches alias → canonical
  • GET/aka/resolvereturns canonical match · k-anon ≥ 2
  • GET/healthreturns ok

Does not exist

5
  • GET/raw-price-historydoes not exist
  • GET/source-tenantdoes not exist
  • GET/decrypt-pricesdoes not exist
  • GET/user-purchase-profiledoes not exist
  • GET/competitor-namesdoes not exist
Push-only · never queryable by tenant Published on purpose

The moat is what it refuses to expose.

DVB sovereignty audit · dvb.redis4u.com

The four classes of data

Two never leave. Two are built to.

Every piece of data in the ecosystem sits in one of four classes. The gate between them is the same one every price signal has to clear.

Sealed

Class A · Tenant private

Your own operational data. Visible to you. Never shared.

Who sees it: you

Class B · Confidential

Raw competitor prices and source identities. Encrypted with AES-256-GCM.

Who sees it: developer + master key only
Released

Class C · Anonymized aggregate

Price signals and trend directions, released only once at least 2 independent sources and 3 samples agree, rounded to $0.50. No source identity attached.

Who sees it: the apps that ask, as an aggregate

Class D · Your output

Derived signals back to you — ranges, alerts, recommendations. Never raw upstream data.

Who sees it: you

What feeds the mesh

Every app pushes in. None can pull out.

The JARBIZ apps share one rule: they push observations to /ingest and read back aggregates from /price-signal. No app can ask DVB about another tenant.

  • REDIS.4UFlagship · pre-launch, onboarding in waves

    The operational core for wholesale distributors — catalog, warehouse, CML price lists, orders, routes and AR in one place. Your price lists stay class A inside your tenant.

  • InvoiceIQLive

    Photo-first invoice organizer for any small business, free at inviq.redis4u.com. Snap an invoice and it’s read and filed; anonymized price signals feed DVB. No ads, no data resale.

  • HUNTERLive

    New-business acquisition inside REDIS.4U: a 5-stage prospect pipeline, competitor invoice scanning, business-card capture and one-tap Close-Won. Territory lead-routing via DVB: Planned

Live now

Ask what the market pays. Never who.

DVB runs as its own service at dvb.redis4u.com. The JARBIZ apps plug into it as they roll out — join the waitlist to get REDIS.4U when your slot opens.

Visit dvb.redis4u.com Join the waitlist

Operator console: neural-core graph · live feed · coverage. See build status