What makes Edilitics’ replication different from traditional ETL and pipeline tools?

Edilitics eliminates the code, config, and endless maintenance found in legacy ETL. Replication jobs are 100% no-code, schema-aware, and run in isolated, ephemeral environments. Everything - from flow setup to scheduling, monitoring, and drift handling - happens visually and securely, with no manual scripts or engineering support required.

Which data sources and destinations are supported for replication?

Edilitics supports SQL and NoSQL databases, data warehouses, cloud object storage, and leading SaaS applications. Replicate data seamlessly across hybrid, on-prem, and multi-cloud environments without vendor lock-in or custom integrations.

How does Edilitics handle schema changes and drift during replication?

Before every replication run, Edilitics checks source schemas for changes. If drift or a breaking change is detected, the job is paused instantly and you receive an immediate alert - no silent failures, no accidental data loss. Built-in auto-schema mapping and reporting keep your destinations accurate and trusted.

What replication methods does Edilitics support?

You can configure Full Load, Incremental Load, and Change Data Capture (CDC) for every flow. Edilitics auto-detects what your source supports - enabling both one-time migrations and near real-time sync with minimal system load.

Does Edilitics store or stage my data during replication?

No. Edilitics never stores, stages, or retains your replicated data. All replication happens in real time and within secure, short-lived VMs. Once a run completes, the environment is destroyed. Your data stays in your systems - ensuring security, compliance, and minimal surface area.

How can I control exactly what data gets replicated?

Edilitics lets you define precisely which tables and columns are included in each replication flow. Drop unnecessary columns, rename fields or tables, and map data types to suit your destination - all with a few clicks. No full-dataset lock-in or wasteful data movement.

Can non-technical users manage replication flows?

Yes. Every replication pipeline is created, scheduled, and monitored with a no-code, point-and-click interface. There’s no YAML, CLI, or “expert mode” - it’s accessible and fully governed for every authorized user.

How does Edilitics meter compute usage for replication, and what happens if I run out?

Edilitics meters compute usage for replication precisely - down to the second - based on the resources consumed by each job. Every replication flow runs in its own isolated, ephemeral VM, which is provisioned on demand and destroyed after execution. If you reach your plan’s compute limit, replication jobs are automatically paused. You’ll receive detailed notifications (in-app and via email or Slack, if configured), including usage breakdowns and clear next steps. You can purchase additional compute minutes as an add-on directly from the platform - no forced plan upgrade, no hidden throttling, and no ambiguous limits. You stay in full control of your usage, costs, and operational continuity.

What happens if a replication run fails or a source becomes unavailable?

If a run fails - due to expired credentials, network issues, or source errors - Edilitics fails fast, pauses the flow, and sends instant alerts (via email and Slack if configured). No silent data corruption or undetected pipeline failures. Run logs and error histories help you diagnose and resolve issues quickly.

Can I automate, schedule, and monitor replication workflows?

Absolutely. Replication can be triggered on-demand, by fixed schedules, or via custom Cron jobs. Every run is logged, auditable, and visible in real time - so you can monitor, pause, resume, or modify flows as business needs evolve.

Replication · Next launch

COMING SOON • SYNC • GOVERN

Replication is in private beta until Q1 ’26.

Need to align your rollout? Talk to product so we can plan your activation date once guardrails lock.

Private beta
Finishing compliance + connector hardening with current enterprise tenants.
CDC + incremental ready
Full, partial, and log-based syncs are validating in closed deployments.
Launch window
General availability lands in Q1 ’26.

Talk to product See replication approach

Active runs4 in progress

MySQL → Snowflake
CDC • Running
ETA 02:12
Postgres → BigQuery
Incremental • Complete
ETA 00:00

Alerts & automation

Schema drift
orders.amount renamed → paused
Auto handled
Credential expiry
MySQL service account rotation scheduled
Auto handled

Active runs4 in progress

MySQL → Snowflake
CDC • Running
ETA 02:12
Postgres → BigQuery
Incremental • Complete
ETA 00:00

Alerts & automation

Schema drift
orders.amount renamed → paused
Auto handled
Credential expiry
MySQL service account rotation scheduled
Auto handled

What’s happening now

Drift, retry, and governance systems are hardening in beta.

We’re finalizing replication with the same care we took for Integrate and AskEdi. Beta partners are hammering CDC, partial reloads, and live compute reporting so launch day feels inevitable - not experimental.

Beta access
Invite-only
We’re working with existing tenants. No public waitlist - reach out to align your launch.
Telemetry
100% traceable
Every beta job feeds drift detection, compute metering, and SLA dashboards.
Launch signal
Q1 ’26
We’ll light up this page with the full experience when the switch flips.

Get in early

Early conversations cover architecture, connector roadmap, and governance asks so your rollout is ready the moment we open the gates.

Talk to product See replication approach