Oracle
LogMiner or XStream. Single instance, RAC and ASM; non-CDB and multitenant with mining in CDB$ROOT and the catalog read in the PDB.
Home / Platform
Capture, initial load, apply, verification, high availability and operations — one agent, one repository, and the same guarantees for every engine.
No triggers, no polling queries. Each engine has a native reader that follows its change log from a durable position.
LogMiner or XStream. Single instance, RAC and ASM; non-CDB and multitenant with mining in CDB$ROOT and the catalog read in the PDB.
Native redo reader, including per-thread capture on TAC clusters and archive catch-up that never skips to the current log.
Logical replication slots, PG 10 and later, with DDL captured through an event-trigger queue.
Row-based binlog with GTID resume, for MySQL 5.7 and 8 and MariaDB 10 and 11.
SQL Server native CDC tables; Db2 LUW recovery logs and Db2 for i journal receivers.
Altibase Log Analyzer, Kafka consumer groups with JSON, Debezium or Avro payloads, and watched folders of CSV or JSONL.
Choose the read strategy per pipeline. Every mode checkpoints by primary key, so an interrupted load continues instead of starting again.
| Mode | How it reads | Best for |
|---|---|---|
| Consistent | One read as of a single SCN, so every table reflects the same point in time. | Most pipelines; exact cut-over point |
| Flashback-free chunks | Short primary-key ranges of current data; the change stream restores consistency. | Very large tables where long reads would exhaust undo |
| Parallel partitions | Contiguous PK ranges copied concurrently, each with its own resume pointer. | Big single-table copies with numeric keys |
| Capture-early | Capture starts first; apply for each table waits until its snapshot completes. | Zero-gap migrations on busy systems |
| On-demand reload | Reload one table from the console, with or without truncating the target. | Repairs and newly added tables |
One agent can fan out to several targets of different types. Each target tracks its own progress, so a slow sink never holds back the others.
Oracle, Tibero, PostgreSQL, MySQL, MariaDB and Altibase, with identifier case and quoting handled per engine.
Keyed by primary key, JSON or Avro with Schema Registry, and transactional exactly-once delivery.
Upserts and deletes by key through bulk APIs, carrying changes only so documents are never overwritten with partial images.
Changes are staged per table, fsynced, and rolled into JSONL, Avro Object Container Files or Apache Parquet. Each rolled file can be uploaded to HDFS or S3-compatible storage, merged into Snowflake or another warehouse over JDBC, and registered as a Hive or Impala partition — the Cloudera data-lake pattern. Failed uploads stay marked and are retried, so a NameNode restart or an expired Kerberos ticket never strands a file.
target.type: FILE · format: JSONL | AVRO_OCF | PARQUETTwo independent services compare what the source holds with what the target received.
Agents coordinate through a lease in the repository. Only the lease holder may write, and every write carries the lease epoch.
Web console for agents, lag, initial-load status, reloads, transactions, sinks and the audit trail.
viriyaneuron_adm for status, recovery, reloads and transaction repair from any shell.
Metrics endpoint plus concise operator log lines designed to be alerted on — progress, gaps and verdicts.
Mix any supported source with one or more targets. Filter by role.
Databases
Streaming & NoSQL
Big data & data lake
Files
Product names and logos are trademarks of their respective owners and indicate compatibility only. Logo artwork from Simple Icons (CC0).
We install the agent on your servers, load and replicate a schema you choose, and hand over the verification results.