Architectural deep dive

Universal Connectivity

Connect to the interfaces your systems already expose instead of waiting for a branded connector to be designed, released, and maintained.

HTTP / APIs Databases Files & object storage Messaging ODBC

The difference

Connect through protocols, not just catalogs

Traditional integration platforms often present connectivity as a list of named applications. DataZen starts one level lower: with the API, database, file, storage, messaging, or driver interface that actually carries the data. This makes custom, internal, and rapidly changing systems first-class integration sources and targets.

Use open interfaces directly

Work with HTTP/S endpoints, relational databases, files, cloud object stores, messaging systems, and ODBC-accessible technologies from the same pipeline model.

Describe APIs from existing assets

OpenAPI, Swagger, and Postman definitions can accelerate configuration while still leaving the underlying request, response, and authentication behavior visible.

Keep sources and targets independent

A source does not dictate its destination. Read through one interface, transform the result, and deliver through another without replacing the pipeline engine.

Adapt when systems evolve

Inspect and reshape incoming structures in the pipeline so API and schema changes can be handled in logic instead of waiting for a connector vendor's release cycle.

Execution model

One pipeline from acquisition to delivery

Connect. Configure the endpoint and its authentication once as a reusable connection.
Acquire. Read records through the source's native interface, including parameters, pagination, and source-side filters.
Shape. Normalize, validate, enrich, or reduce the data in memory while it moves.
Deliver. Route the prepared result to one or more supported destinations without coupling them to the source.

Universal does not mean uncontrolled

Connections centralize endpoint and credential configuration. Pipelines reference those named connections, keeping secrets out of pipeline logic and making access easier to govern, rotate, and audit.

Where it fits

Useful when the connector catalog becomes the constraint

Internal applications: integrate proprietary APIs and databases that will never appear in a public catalog.
Fast-moving SaaS APIs: update requests and mappings as the provider evolves its endpoints.
Hybrid estates: bridge cloud, on-premises, and private-network systems with a consistent pipeline language.
Modernization: preserve working source integrations while changing downstream lakes, warehouses, or applications.

DataZen makes the interface the integration boundary, so new systems do not have to wait for a new platform connector.

Back to DataZen