Data Ecosystem

Operational data, ready for analytics and AI

Tessell Data Ecosystem streams live changes from your operational databases into Microsoft OneLake and other lakes and warehouses managed from the same console as your databases, with no separate pipeline infrastructure to operate.

Talk to an expertView documentation →
The problem

Operational data and analytical data are managed in separate systems. The pipeline between them introduces latency by design.

Most teams have the analytical systems they need. What they don't have is operational data current enough to make those systems useful. The gap between the production database and the data warehouse is where business decisions go stale.
Pipelines are brittle and expensive

Pipelines are brittle and expensive

Operational pipelines are assembled from multiple components, each with its own complications, and every link adds surface to maintain. For Oracle, change capture needs database-layer configuration before any pipeline can run.
Operational and analytical data live in silos

Operational and analytical data live in silos

Analytical systems are built for query performance on transformed data, not real-time operational state, so the gap is by design. Decisions get made, and AI models trained, on data already stale.
Data integration sits outside database governance

Data integration sits outside database governance

When integration runs separately from the database layer, the database's own access controls and encryption don't extend to the pipeline or target, and the stack's cost is unsustainable as AI accelerates.
How it works

From production database to analytical system, in near real time

Tessell's Change Data Capture engine reads transaction logs directly, processes changes through managed stream handling, and lands the data in your analytical system, without you managing any of the infrastructure and tooling in-between.

01 Capture every change at source
Tessell CDC reads the transaction logs of your Tessell-managed databases - Oracle, SQL Server, PostgreSQL, MySQL. Every insert, update, and delete captured at source. Minimal performance impact, no full-table scans.
02 Deliver changes reliably, without data loss
Captured changes flow through Tessell's managed stream processing layer. Only modified data propagates, incremental, not batch. Schema evolution handled automatically. No Kafka cluster to operate.
03 Move data without exposing it
All data encrypted in transit and at rest. Transmitted over private links so operational data never traverses the public internet. RBAC, audit logging, and data masking apply throughout the pipeline.
04 Land data where analytics runs
Changes land in Microsoft OneLake via open mirroring, stored in open table formats including Apache Iceberg. Sync mode configurable per pipeline - near real-time, asynchronous, or scheduled.
What it does

From the moment a change happens in production, the pipeline carries it to where analytics needs it.

Change Data Capture at source

Continuous capture from transaction logs of Tessell-managed databases. No queries against the source, no performance impact, no specialist tooling.

  • Multi-engine source support - Oracle, SQL Server, PostgreSQL, MySQL captured from native transaction logs.
  • Log-based capture - no full-table scans, no performance impact on the source database.
  • Automatic schema evolution - pipeline adapts as the source schema changes, without manual intervention.
  • Granular capture scope - entire database, specific schemas, or table-level. Configure per pipeline.
Data Management

Four layers of data management, architected into one platform

Tessell connects protection, access, governance, and activation into a single platform. Managed from one control plane, with no gaps between them.

Protect

Availability Machine

Continuously captures snapshots, transaction logs, and native backups across every database and every engine. The foundation everything else depends on.

How AM works
Access

Dataflix

Turns the AM's output into a self-service catalog. Any team, DBA, developer, QA, can clone, restore, or download from any point in time without filing a ticket.

How Dataflix works
Govern

Data access policies

Governs what data flows where and who can access it, same region, cross-region, or cross-subscription. Masked or as-is. Enforced by architecture, not policy documents.

How DAPs work
Activate

Data ecosystem

Streams live changes from operational databases into data lakes or warehouses for analytics and AI, without separate CDC tooling, or ETL overhead

You are here
Ready to see how your operational data could reach analytics systems in real time?

Talk to a Tessell engineer, not a sales rep. Bring your database environment, your analytical targets, and your data freshness requirements. Walk away with a clear picture of what Data Ecosystem would change for your team.

Talk to an expert
Frequently Asked
Questions
Tessell Data Ecosystem is a Change Data Capture-powered pipeline capability that streams live changes from Tessell-managed databases into analytical systems - starting with Microsoft OneLake via open mirroring. It eliminates the need for separate CDC tooling, Kafka cluster management, and ETL infrastructure. Managed from the same Tessell console as the databases themselves.
Tessell CDC captures changes from Oracle, SQL Server, PostgreSQL, and MySQL - reading directly from native transaction logs. Oracle to Microsoft OneLake is the lead GA integration. Other engine and target combinations are available - check with your Tessell representative for the current support matrix.
Tessell is a listed partner in Microsoft's Open Mirroring Partner Ecosystem. The integration uses Fabric's open mirroring capability to stream changes from Tessell-managed databases directly into Microsoft OneLake, stored in open table formats including Apache Iceberg. No batch jobs, no transformation layer between source and target.
Traditional ETL pipelines are well-suited for transformation-heavy workflows where data needs to be restructured or enriched before landing in the target. Data Ecosystem is designed for a different job: streaming operational changes continuously from the database layer to analytical systems, with governance that extends from the source. Both approaches have their place - Data Ecosystem addresses the latency and governance gap that exists when operational and analytical infrastructure are managed separately.
Yes. All data is encrypted in transit and at rest. Transmission happens over private links - operational data never traverses the public internet. RBAC, audit logging, and data masking apply throughout the pipeline, consistent with the database access model.
Yes. CDC setup, monitoring, and lifecycle control sit inside the Tessell portal alongside the databases themselves. Pipeline health appears next to database health. Pause, resume, or delete pipelines from the same place you manage the rest of your estate.
Three modes: near real-time, asynchronous, and scheduled. Configurable per pipeline based on your business need. You can also choose the granularity of capture - entire database, specific schemas, or table-level.
The Availability Machine produces the protected data. Dataflix makes it self-service. Data Access Policies govern where it goes. Data Ecosystem activates it - streaming live operational changes to analytical systems. The four capabilities form one continuous data management platform, managed from one control plane.
Usage-based pricing. Specific pricing depends on data volume, sync frequency, and target system. Talk to your Tessell representative for a quote tailored to your environment.