Metadata-driven catalog discovery
Discovers source tables from catalog metadata instead of hard-coding a Java table list.
This page brings together product capabilities across security, data movement, privacy, validation, backup, performance, observability and topology.
Resumable, metadata-driven and safe data movement.
14 capabilitiesDiscovers source tables from catalog metadata instead of hard-coding a Java table list.
Initial-loads a new target with full source read + idempotent UPSERT without truncating it.
Moves only the changed data window using watermarks and checkpoints.
Reads tables without a reliable watermark through PK-based pagination.
Keeps cursor internals opaque and protects scope/integrity with HMAC.
Uses a stable sync_until boundary during a cycle for a consistent moving-source window.
Determines has_more without a separate count query.
Couples target writes with cursor/checkpoint progression transactionally.
Continues from the last safe cursor/checkpoint after interruption.
Does not pile up jobs; the next cycle starts after the previous one completes plus the configured delay.
Runs multiple source/client flows in parallel with isolated workers and target connections.
Uses process locking and source leases to prevent duplicate concurrent flows.
Makes page retries safe without creating duplicate target rows.
Enables or disables integrations through configuration rather than code changes.
Combines identity, environment, data classification and endpoint controls.
13 capabilitiesSeparates business intent such as backup, PROD→TEST, TEST→TEST, DR and replication from execution mode.
Evaluates PROD, PREPROD, TEST, DEV, BACKUP and DR direction rules explicitly.
Uses the API key only for login and short-lived Bearer/refresh tokens for runtime calls.
Binds tokens to source instance, profile, platform, action and consumer context.
Moves source data over HTTPS/TLS.
Applies action-based DB-backed throttling to limit abuse and bursts.
Exports only allowlisted metadata columns instead of SELECT *.
Validates dynamic table and column identifiers against metadata.
Avoids exposing internal paths, secrets, payloads and stack traces in API errors.
Masks keys, tokens, cursors and secret values in log/audit paths.
Allows sensitive backup columns only through explicit metadata plus local configuration approval.
Separates the public sync endpoint from internal PHP API files.
Records auth, rate-limit, cursor and access events with a controlled event taxonomy.
Protects sensitive data when production data is delivered to non-production environments.
9 capabilitiesRefreshes non-prod environments under explicit purpose and environment policy.
Transforms sensitive values before they leave the source process boundary.
Produces repeatable fictitious identities for the same business identity.
Supports DROP, NULL, CONSTANT, HMAC_HASH, EMAIL_FAKE, PHONE_FAKE, ID_FAKE and DATE_SHIFT.
Keeps related parent/child and business-key identities consistent after masking.
Checks generated values for collisions on unique columns.
Treats password, token, secret, API-key and salt fields as deny/drop by default.
Replicates data between test environments to build a common integration baseline.
Bootstraps a newly created test database from an approved source or backup.
Checks source-target consistency in addition to transfer completion.
9 capabilitiesCompares source and target row counts within the transfer window.
Splits large tables into PK ranges for count + digest validation.
Binds validation to the same snapshot/watermark boundary.
Localizes mismatches to the affected bucket/range instead of the entire table.
Reports extra target rows rather than automatically hard-deleting them.
Plans controlled UPSERT repair only for mismatched buckets/ranges.
Recalculates count/digest values after repair.
Reuses the validation model after a backup restore.
Persists validation runs and bucket evidence as operational records.
Validates source/target shape before data writes and narrows the dynamic SQL surface.
9 capabilitiesFails closed instead of silently falling back when keyset pagination has no PK.
Preserves ordered multi-column primary/sync keys from metadata.
Checks type, nullability, length, precision/scale and signed/unsigned compatibility.
Detects required target columns that are absent from the source payload before transfer.
Designed for controlled, non-destructive schema widening where explicitly allowed.
Verifies configured target schema against the active JDBC catalog before writes.
Lets multiple customer/instance profiles reuse the same runtime with different metadata.
Allows child-table delta windows to be defined through parent metadata.
Surfaces platform and production naming/case differences during preflight.
Protects the operation chain from backup creation to recovery readiness.
10 capabilitiesMoves PROD or PREPROD data to a controlled backup target.
Passes DB credentials through an option file rather than the process command line.
Validates the executable and backup directory before starting.
Verifies that compressed backup artifacts are readable.
Tracks backup artifact integrity with a checksum sidecar.
Supports daily, weekly and monthly retention cycles.
Requires explicit enablement, confirmation and a successful backup before destructive rebuild.
Prevents backup and full-rebuild operations from overlapping.
Tracks the last successful backup point for operations.
Supports production-to-recovery/DR transfers without masking.
Controls network, memory, database and concurrency pressure at scale.
11 capabilitiesCompresses HTTP payloads for network efficiency.
Bounds both wire and decoded response sizes.
Writes rows in bounded transactional batches.
Uses one configured HTTP client instead of creating a new one per request.
Uses isolated Hikari target pools per client.
Retries transient HTTP/transport failures with bounded backoff.
Stops further source calls after repeated exhausted transport failures.
Architecture for splitting very large tables into independently tracked PK ranges.
Architecture for adjusting batch size to DB commit, connection and memory pressure.
Slows source read/write flow when the target database becomes the bottleneck.
Keeps memory proportional to page/batch size rather than total dataset size.
Correlates run, request, table and page layers in one operational model.
12 capabilitiesLinks Java worker cycles and source logs through a common run identity.
Traces the same data-page request across source LOG_SYNC and target transfer metrics.
Carries typed terminal run outcomes together with operational counters.
Records rows, duration and terminal result per table.
Tracks rows, compressed/uncompressed bytes, DB write, HTTP and retry data per page.
Measures rows/sec and bytes/sec.
Checks config, connectivity, auth, metadata, target, schema, backup and runtime safety.
Checks config/policy/schema/readiness without moving data.
Searches source logs by instance, platform, run and request identity.
Renders dynamic log content as safe text rather than executable HTML.
Applies bounded retention to operational and validation records.
Keeps credentials, tokens, raw payloads and stack traces out of operations views.
Supports multiple environments and target models rather than assuming a single source.
8 capabilitiesManages multiple PROD/TEST sources against one backup target with client/source-instance isolation.
Routes sources to separate TEST, DR, standby or backup targets.
Scopes flow identity by source instance, client, run and profile.
Runs the runtime and target DB in your own server, data center or cloud account.
Allows the backup target and operations to be managed in Aereo infrastructure under the service scope.
Supports source and target systems across different network/cloud boundaries over HTTPS.
Handles customer/instance differences through profiles and configuration rather than runtime forks.
Schedules backup jobs independently from the fixed-delay data-sync worker.
Roadmap items describe the product expansion direction and targeted connector ecosystem.
New connectors should plug into the existing policy, checkpoint, validation, masking and observability contracts through a common connector framework, avoiding a rewrite of the security core for each database or language.