Key Concepts

Self-Governed Data

Schema metadata is embedded within the code itself, automatically updated as the code changes. This eliminates the need for separate, potentially outdated, data documentation. Governance becomes a prerequisite for data production.

Shift-Left Data Engineering

Software Engineers take ownership of the data they create, including defining and documenting it accurately from the start (during development) rather than later (after it's produced). When a developer creates a new field, they are responsible for defining what that field means and how it should be used.

Data DevX

The concept of building software with data as a first-class citizen. Data is not an afterthought, but a core consideration throughout the development process. Data DevX practices include using code-synced metadata and Data APIs to ensure data is discoverable, usable, and reliable.

Code-Synced Metadata

Woven automatically keeps schema metadata up-to-date by connecting it directly to your source code. Whenever the code that defines your data changes, the metadata is automatically updated as well. Instead of maintaining a separate data dictionary, Woven uses the code itself as the source of truth for data definitions.

Data API (DAPI)

Similar to how software exposes functionality through APIs, DAPIs treat data as a product with well-defined specifications and usage patterns. This approach encourages collaboration between data producers (software engineers) and data consumers (analysts, data scientists).

Data Access

The intentional sharing of data with specific use cases in mind. Data access can be Public (open to everyone) or Private (controlled access for authorized users). A company might grant public access to anonymized user demographics data while keeping private user contact information.