iblync · Replication without coding

Data replication without a development team: configured, not coded

iblync replaces per-project scripts with low-code workflows. Your team chooses the source, the target and the tables. Interkey sets it up and runs it with you.

  • Built and supported by Interkey An Interkey product, delivered and supported by Interkey
  • Low-code workflows, not per-project scripts Set up by configuration, with no development team needed on your side
  • Delivered with the team that runs it Interkey sets it up and runs it with you
The iblync dashboard: a replication task between two databases
The iblync dashboard, from the recorded product demo.

Building data replication in-house usually needs developers to write the pipelines and keep them working. iblync, built by Interkey, is set up through low-code workflows instead of scripts, so a database or infrastructure team can run migration and continuous sync without a development team. A system outside the published list gets a connector built as part of the project.

What "no development team" means here

On this page, "no development team" means one specific thing: nobody on your side writes or maintains the code that moves the data. In-house replication usually starts with a developer writing a pipeline for each source, and then turns into a standing job, because every pipeline needs someone to keep it working as the systems around it change.

Read more

With iblync, your team makes the decisions and the Interkey team does the setup. Your side chooses the source system, the target and the tables in scope, grants access to both, and approves the cutover date when a migration is ready to switch. What your side does not do is write pipeline code, keep it running, or rewrite it when a system is upgraded. No development team needed on your side: a database or infrastructure team is enough to own the project.

Configured, not coded

iblync replaces per-project scripts with low-code workflows. A migration or a continuous sync is described by configuration: which system is the source, which is the target, which tables move, and whether the move is a one-time migration, a migration in phases, or a continuous sync that keeps running afterwards. The usual setup needs no code at all. Where a case is unusual, the Interkey team handles it as part of the project, so your team is not left with a script to look after.

Read more

The systems iblync connects today are listed on the connectors page. A system outside that list gets a custom connector, built when needed, as part of the project. Once data is moving, each change is applied as it happens; our real-time replication page explains that part. If your team is weighing a build on an event-streaming platform instead, our page on Apache Kafka or a replication platform sets out that choice.

Build it yourself or configure a platform

Both routes can move data. The difference is who carries the work after the first run, and four questions show it. When you build in-house:

  • Who writes it: your developers, one pipeline per source and target, as code.
  • Who maintains it when a system is upgraded: the same developers, who change and retest the code each time a source or a target moves to a new version.
  • Who is called when it fails: whoever knows that code, at whatever hour it stops.
  • Where the project knowledge goes when a developer leaves: often with them, in scripts few others have read.

Building in-house can still be the right answer for a team that already has developers dedicated to data and wants to own every line. For a team that does not, the questions further down are worth answering first. Pricing for iblync is discussed in a pricing meeting, followed by a written quote.

What iblync covers

Three things the platform does for the project, from the first copy of the data to the sync that follows it.

01

Migration and continuous sync

A one-time migration, a migration in phases, or a continuous real-time sync that keeps the source and the target in step afterwards. Sync in both directions is supported where both systems accept writes.

02

Control over transfer speed

Transfer speed and resource use can be limited, so the production database keeps serving users at its normal pace while the data is copied.

03

A queue when the target stops

If the target is unavailable, for maintenance or a fault, changes wait in a queue and are applied when it returns.

What stays with your team

Removing the code does not remove the decisions. Three of them stay with you, because they belong to the business that owns the data.

01

The scope of the data

Which systems, which tables, and what is left out. Your team knows which data matters and which is old history that nobody reads.

02

Access and credentials

Your team grants access to the source and the target, decides which accounts iblync uses, and decides who holds their credentials.

03

Approval of the cutover

When a migration is ready to switch, the date and the decision to go ahead are yours. Our parallel run and cutover page sets out how that decision is prepared.

Questions to ask before building in-house

Six questions to answer honestly before a developer writes the first pipeline. If most of them have no clear answer, a configured platform is worth evaluating, and our evaluation guide sets out how.

  • Who will maintain the pipelines a year from now, when the developer who wrote them has moved on?
  • Who watches the replication at night and at weekends, and who do they call when it stops?
  • What happens to the code when the source system is upgraded or replaced?
  • How will you prove that every record arrived, and show that proof to the business?
  • How many more systems will need to be connected later?
  • What does it cost the business if the project runs late because the pipelines take longer to build than planned?

Scope

Two points of scope

A custom connector, for a system outside the published list, is built by Interkey as part of the project. And iblync sends weekly and monthly replication reports: a detailed account of each transfer, with evidence that it completed, so your teams can see that the old data and the new data match. More on our migration and replication reports page.

Questions about replication without a development team

Do we need developers to use iblync?

No. iblync is set up through low-code workflows instead of scripts, and the Interkey team runs it with your team. Your side chooses the source, the target and the tables, grants access, and approves the cutover. No development team needed on your side: a database or infrastructure team is enough to own the project from day to day.

Who sets up the first replication?

The Interkey team, working with yours, once the source, the target and the tables in scope are agreed. Your team grants access to both systems and confirms the scope; the Interkey team configures the workflow and starts the first copy. From then on the two teams run it together, and your team can follow each transfer in the weekly and monthly replication reports.

Can our database team run it day to day?

Yes. A database or infrastructure team can run iblync day to day, with support from Interkey in Arabic and English. The routine work is following the sync and reading the reports, not writing or fixing code. A change that needs new configuration, such as adding a table to the scope, is agreed with the Interkey team.

What if our system is not on the connector list?

Interkey builds a custom connector for it, as part of the project. Tell us the system and its version when you contact us, and the connector is scoped with the rest of the work. The systems iblync connects today are listed on our connectors page, so check there first: your system may already be covered.

Is low-code the same as no-code?

No. Low-code means the usual setup needs no code: the source, the target, the tables and the type of move are configured, not programmed. An unusual case may need some code, and the Interkey team handles it. Either way, nobody on your side has to write that code or maintain it afterwards.

How long does setup take?

It depends on how many systems and tables are in scope, and it is estimated in the assessment for your own systems rather than given as a standard figure. One source and one target with a clear list of tables is a smaller job than several systems, one of which needs a custom connector. Ask for the estimate in the meeting.

Next step

Request an iblync quote

Tell us the source and the target, the tables or systems in scope, and who on your side will own the project: a database team, an infrastructure team, or both.

Required field

By sending this form, you agree to our Privacy Notice.

What happens next

  1. We read your request
  2. An engineer contacts you
  3. You get an estimate or a demo
  • Built and supported by Interkey

    An Interkey product, delivered and supported by Interkey

  • Low-code workflows, not per-project scripts

    Set up by configuration, with no development team needed on your side

  • Delivered with the team that runs it

    Interkey sets it up and runs it with you

Or directly

+966-11-2180999 [email protected]

Tawuniya Towers, North Tower, 7th Floor, King Fahad Highway, Olaya, P.O. Box 56835, Riyadh 11564, Saudi Arabia

or See supported connectors

Published by Interkey. Last updated . Interkey is registered in Riyadh, Saudi Arabia under commercial registration 1010156897.