UDB Skills

Universal Data Broker

UDB :: Universal Data Broker
_{gRPC data plane | native control plane | tenant/project scope guard
crate v0.3.2 | protocol v1.0.0}

UDB is a public, schema-driven knowledge graph and data broker for applications that need one typed API in front of many data systems.

You describe your domain in normal .proto files, add UDB annotations for storage and security behavior, then run one broker in front of relational databases, object stores, caches, vector stores, document stores, graph stores, analytics systems, and native identity services. Application code calls UDB through gRPC or an SDK; UDB handles routing, metadata, authorization, migrations, CDC, and backend-specific execution.

What UDB Gives You

• One DataBroker API for relational records, objects, vectors, cache entries, documents, graphs, analytics, catalog operations, migrations, transactions, CDC, and admin health.
• A native control plane for authentication, authorization, API keys, identity providers, tenants, notifications, analytics, storage, assets, WebRTC, and versioned policy distribution.
• A descriptor-driven contract: protos define services, tables, field security, endpoint security, SDK surfaces, event contracts, and generated docs.
• Multi-tenant request context on every call: tenant, project, user, purpose, service identity, scopes, correlation id, and client catalog version.
• SDKs for Go, Python, TypeScript/Node, Java, C#, and PHP/Laravel.
• A single CLI named udb for proto export, formatting, SDK generation, native service setup, app integration, local dev, broker serving, and diagnostics.

Current Surface

Area	Surface
Data plane	76 DataBroker RPCs
Native control plane	15 services, 186 RPCs
Contract manifest	733 messages, 49 table-backed models, 192 event contracts
Backends	18 backend kinds across SQL, cache, vector, object, document, graph, and column stores
SDKs	Go, Python, TypeScript/Node, Java, C#, PHP/Laravel
Release	crate/SDK version 0.3.2, wire protocol 1.0.0

The native-service table is generated from the embedded descriptor: docs/generated/native-services.md.

How It Feels

Your project owns the model:

syntax = "proto3";
package acme.billing.v1;

import "udb/core/common/v1/db.proto";

message Invoice {
  option (udb.core.common.v1.pg_table) = {
    schema: "billing"
    table: "invoices"
  };

  string invoice_id = 1 [(udb.core.common.v1.pg_column) = {
    primary_key: true
    sql_type: "text"
  }];

  string tenant_id = 2;
  string customer_id = 3;
  int64 total_cents = 4;
}

Application code calls the broker through an SDK:

from udb_client import Metadata, UdbClient, decode_records

meta = Metadata(
    tenant_id="acme",
    user_id="user-1",
    purpose="billing.api",
    scopes=("udb:read", "udb:write"),
    service_identity="billing-service",
    project_id="billing",
)

with UdbClient("127.0.0.1:50051", meta) as udb:
    rows = udb.select(message_type="acme.billing.v1.Invoice", limit=50)
    print(decode_records(rows))

Quick Start

Install the CLI from a release binary, through an SDK launcher, or from source:

cargo install --path .

Export UDB's shared protos into an application project:

udb proto export --fmt

Write app-owned protos that import UDB annotations:

import "udb/core/common/v1/db.proto";

Inspect the catalog and generated SQL:

udb catalog proto
udb sql proto
udb lint proto --human

Start a local broker:

udb serve proto "" 0.0.0.0:50051

Check runtime readiness:

udb doctor --human
udb compat-matrix

CLI

All public commands use the short binary name udb.