Frequently Asked Questions

SyncBridge is a secure integration platform that helps you turn local files, SQL data, and internal systems into controlled cloud APIs and automated data flows — without exposing your internal network.

SyncBridge is built for companies that need to connect local systems with cloud applications, customer portals, ERPs, external APIs, or custom integrations while keeping control over security, structure, and deployment.

Many businesses still depend on local machines, industrial equipment, internal SQL databases, legacy exports, CSV, Excel, XML, shared folders, and on-premise applications. In many cases, these systems do not provide a modern API. SyncBridge bridges that gap by capturing data locally, mapping and transforming it into structured JSON, and delivering it securely to cloud platforms, MES systems, ERP systems, external APIs, and other business applications.

Yes. This is one of the strongest use cases for SyncBridge. If a machine, industrial device, legacy application, or internal process can expose data through files, exports, folders, or a local database, SyncBridge can process that data locally and turn it into a structured cloud-ready flow.

Yes. SyncBridge is designed to bridge locally generated machine data into secure cloud workflows, dashboards, APIs, MES platforms, ERP systems, and other external applications.

Yes. SyncBridge can prepare, map, transform, and deliver local data in a structured format so it can be consumed by MES platforms, ERP systems, cloud applications, customer portals, and other external systems.

Yes. SyncBridge is especially useful when a system can only export CSV, XML, XLSX, JSON, or database records but does not provide a modern API.

In real industrial environments, direct cloud integration is often difficult, risky, or simply unsupported. Some machines have no API, some systems only export files, and some databases should remain local. SyncBridge provides a safer and more controlled model by processing data locally through the Desktop Agent and sending only the required structured data to the cloud.

The SyncBridge Desktop Agent is the local Windows component installed inside your environment. It can watch folders, process files, run SQL-based channels, transform data locally, and exchange data securely with the SyncBridge Hub.

No. The standard model is based on secure outbound communication initiated by the Agent, which helps reduce network exposure and avoids opening inbound ports for typical scenarios.

Yes. Multiple Agents can be used for different machines, sites, or responsibilities depending on your deployment model and subscription plan.

A Channel is the main integration unit in SyncBridge. It defines how data is collected, processed, transformed, and transferred. A Channel can be connected to files, folders, or SQL queries depending on the use case.

The current project includes support for XML, CSV, TSV, JSON, XLSX, and SQL-query-based datasets.

Yes. A core pattern in the platform is converting incoming data into structured JSON payloads that can be delivered, stored, or consumed by external systems.

Yes. One of the core benefits of SyncBridge is that it can convert local files, database results, and machine-driven exports into structured API-ready payloads that can be delivered securely to the cloud or consumed by external systems.

Yes. The Desktop Agent includes a mapping designer that lets you define how incoming source fields are translated into the output structure you want to publish or send to another system.

Yes. The project includes inference logic that can build an initial mapping tree from XML, CSV or TSV samples, and SQL query results, which speeds up the first setup considerably.

Transformation is the step where values are cleaned, normalized, converted, or adjusted before they are delivered in the final JSON output. This helps standardize messy source data before it reaches the target system.

The current implementation includes operations such as trim, upper or lower case conversion, whitespace normalization, string or number conversion, integer conversion, rounding, boolean conversion, date conversion, regex extract, regex replace, replace, split and take, prefix, suffix, value mapping, null-if-empty, and default-if-empty.

Yes. The project includes SQL query channels that can run against SQL Server and produce structured JSON output.

Yes. The Agent includes a SQL Query Builder window and related models for selecting tables, fields, joins, aliases, and incremental logic without forcing every query to be written manually.

Yes. The current implementation supports join definitions as well as manual SQL text when you need tighter control over the query.

Yes. SQL channels can use an incremental column together with a stored last-sync value so the next execution can fetch only newer records instead of re-reading the entire dataset.

The platform uses authenticated communication between components and supports channel-level protections such as key validation and optional request signing. The architecture is intentionally designed to reduce local network exposure.

Depending on deployment and configuration, the system can store data in local or cloud storage layers. The platform includes retention policy logic and cleanup services so message data does not live forever unless you want a museum of JSON fossils.

Yes. The Hub includes Stripe-based billing flows for plan subscriptions, upgrades, downgrades, cancellation behavior, and reactivation.