iblync · FAQ
iblync: the questions buyers ask before they decide
Short answers on what iblync does, what it connects, how it is priced, who runs it, and what it does not do.
Published 5 min read
- Built and supported by Interkey An Interkey product, delivered and supported by Interkey
- One platform for migration and continuous sync The move and the replication that follows it
- Written quote after one meeting The price is discussed in a meeting about your systems
iblync is a data migration and synchronisation platform built by Interkey, a Saudi technology company in Riyadh. It moves data between different systems once, in phases, or continuously, in one direction or both. Its price is discussed in a meeting for each project, and it is delivered with the team that operates it.
Questions buyers ask about iblync
The product
What is iblync?
iblync is a data migration and synchronisation platform built by Interkey, a Saudi technology company in Riyadh. It moves data between different systems once, in phases, or continuously, in one direction or both. Its price is discussed in a meeting for each project, and it is delivered with the team that operates it.
Who built iblync?
Interkey built iblync. Interkey is a Saudi technology company based in Riyadh, working since 1999, and iblync is one of its own products, alongside SquintPRO, Interkey Digital Connect and Interkey Intelligent DPI. The same company delivers the platform, operates it with your team and supports it in Arabic and English.
What is the difference between migration and synchronisation in iblync?
Migration moves data from one system to another, once or in phases, and ends at cutover. Synchronisation keeps the systems in step after that: a change in one reaches the other in real time. iblync does both on one platform, so the old and the new system can run side by side until you decide to switch.
Is iblync an ETL tool?
No. iblync moves and synchronises data between operational systems; it is not built to reshape data for analytics, which is the job of an ETL tool. If your project is loading a data warehouse for reporting, our page on ETL and change data capture explains which approach fits which job.
RelatedETL and change data capture
What it connects
Which systems does iblync connect?
iblync connects, as a source or a target, Oracle, SQL Server, MySQL, PostgreSQL, IBM Db2 (on LUW, z/OS and IBM i), MongoDB, Couchbase, Cassandra, Redis, Elasticsearch, Neo4j, Apache Spark and Amazon S3. Apache Kafka works as the bridge between systems, not as a source or a target. The direction is confirmed for each pair of systems before the project is designed. The iblync connectors page lists them in one table.
Relatediblync connectors page
What if our system is not on the list?
A custom connector is built for it, as part of the project. A system missing from the list is a connector to build, not a reason the project cannot go ahead. Tell us the system and its version in the form at the end of this page, and the connector is planned with the rest of the work.
Can iblync sync in both directions?
Yes. iblync supports two-way synchronisation, where both systems accept writes and each side's changes reach the other. It is used most when an old system and its replacement run in parallel during a transition. The rule for a record changed on both sides is agreed before sync starts; our page on bidirectional database sync explains those rules.
Relatedbidirectional database sync
Running it
Who operates iblync?
iblync is delivered with the Interkey team that operates it, working alongside your team. You do not buy a tool and run it alone: the same team sets up the workflows, follows the transfer and supports the platform, in Arabic and English, for the length of the project.
Do we need a development team to run iblync?
No development team is needed on your side. iblync is set up by configuring low-code workflows, not by writing code or transfer scripts for each project, and Interkey runs it with you. What your team brings is knowledge of its own systems and data: which records matter, and how the business uses them.
Where does iblync run?
Where iblync runs is decided for each project, before the design starts. The decision covers the environment the platform works in and whether any data leaves it, and it is taken with your security and data owners before the first record moves.
Will iblync slow down our production database?
It does not have to. Transfer speed and resource use can be limited, so replication does not compete with production for capacity. The limits are agreed with your database team before the first transfer, and they can be changed while the project runs if the load on the source calls for it.
What does iblync do with changes if the target system stops?
It keeps them in a queue. When the target is unavailable, changes queue instead of failing, and the queue is processed when the target returns. Plan with the Interkey team how long a target may be away, because the queue grows for as long as it is down.
Does iblync send regular reports?
Yes. iblync provides weekly and monthly replication reports. Each one details the transfer and shows that it completed, so your teams can see that the old and the new system match and that the move was complete.
Buying it
How is iblync priced?
The price of iblync is discussed in a meeting and followed by a written quote: book that meeting with the form on this page, or read how the iblync pricing meeting works.
What do you need from us to prepare a quote and start a project?
Three details are enough to start: the source and target systems with their versions, a rough data volume, and the downtime window the business can grant. The project starts with one meeting in which we understand your systems; the written quote follows it, and the work is planned from there.
What iblync does not do
What does iblync not do?
iblync moves and synchronises data. It does not rewrite stored procedures, triggers or application code for a new engine: that conversion is separate work in a migration project. It is not a database monitoring tool either; for monitoring, see Redgate Monitor. And it does not replace your backups, which you keep as before.
Next
Related pages
Next step
Request an iblync quote
Tell us the source and target systems, a rough data volume, and any question this page did not answer. The price is discussed in a meeting, followed by a written quote.
What happens next
- We read your request
- An engineer contacts you
- You get an estimate or a demo
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