Sync and Syncore

Date: November 21, 2025

On December 11th we will present Sync at the Propymes Summit, an important event organized by Techint Group. After years of working on machine connectivity, we finally reached a product that is solid, different, and with long-term potential. We expect to keep developing it for the next decade.

Syncore

Syncore is designed to become an operating system for monitoring and controlling industrial machines. It provides a generic foundation that connects the physical world with digital systems such as: databases, message brokers, web applications. It solves the fundamental problem of communicating machines with modern software. It works as a networking and messaging layer.

To achieve this, Syncore borrows many lessons from the rise of social networks and applies them to industrial communication. It relies on distributed messaging and microservices as its core architectural principles. These principles define how Syncore and Sync operate at scale:

Event-Based: The system reacts to events emitted by machines and applications, ensuring data flows in real time and logic is triggered instantly.
Microservice-Based: Functionality is broken into small, independent services that can scale, update, and recover individually, reducing downtime and complexity.
Distributed Messaging: Data is exchanged through message brokers, allowing components to communicate reliably even in unstable industrial environments.
Stream Processing: Machine data is processed as continuous streams, enabling real-time analytics, transformations, and decisions.
Open Architecture for Multiple Connectors: New protocols, databases, and external tools can be integrated easily, ensuring the platform remains extensible and future-proof.
Custom User-Defined Functions: Developers can embed their own logic into the data flow, adapting Sync to unique machine behaviors and application needs.
Bidirectional by Design: The same system handles data flowing from machines to applications and from applications back to machines, closing the loop between sensing and action.

Sync

Sync, built on top of Syncore, is the layer that makes syncore usable. Is a set of tools that simplify how digital twins are modeled inside Syncore.

User definition

Along our way, we deployed and maintained real-time data projects in production environments, which turns out to be very hard. And the industrial environment makes everything even harder. Managing all the resources needed to achieve a project, and ultimately meet the client’s goals, requires expertise across many fields. These are the foundational ones, listed from the bottom to the top of the stack, lets call it the knowledge base list:

Mechanics
Automation, including PLCs and basic automation elements
Process understanding
Industrial electrical technician knowledge
Electronics
LAN and WAN installation and management
Server setup and maintenance
Industrial communication protocols
——————————————- Sync —————————————
Protocol drivers
Container orchestration
Real-time operating systems
Cloud computing
Message brokers and queues
ETLs and ETL frameworks
APIs
Databases, including time series, NoSQL, and SQL
Data modeling, labeling
Database schema
——————————————————————————————-
Visualization tools
Web apps
User interfaces
SQL
Python (Pandas, Pytorch, Numpy, TensorFlow, MatPlotLib)
Colab and Jupyter
ML models
Git

Sync was created to integrate the tools between the dashed lines into just one ecosystem.

If you replace the elements between the dashed lines with sync, the knowledge base is reduced significantly, but still has a lot of content in it.

To make it simpler to analyze, I divide the stack into four developers: OT (Operational Technology), IT (Information Technology), Web Development, and Machine Learning Development. In this model, a developer can specialize in at least one of these four areas and in Sync itself. This naturally leads to a team structure.

——————————————- OT Developer ——————————————-
Mechanics
Automation, including PLCs
Process understanding
Industrial technician knowledge
Electronics
Sync
——————————————- IT Developer ——————————————-
LAN and WAN installation and management
Server setup and maintenance
Sync
——————————————- Web Developer ——————————————-
Visualization tools
User interfaces
SQL
Git
Sync
——————————————- Data Scientist ——————————————-
Python (Pandas, Pytorch, Numpy, TensorFlow, MatPlotLib)
Colab and Jupyter
SQL
ML models
Git
Sync

Every team member must know how to use Sync, but they do not need to understand all the tools or technologies that Sync is built on. This significantly reduces the required expertise. The learning curve becomes focused on our documentation and on understanding the data model.

Great! we have defined our users. Now Sync must provide tools and interfaces tailored to these four roles, which is a challenging task. Let’s go through them one by one.

OT Developer

Role: Connecting the industrial process to an MQTT broker through the technologies available on the shop floor: Modbus, TCP/IP, Profinet, EtherCAT, AutentioNode, DACs, PLCs, industrial PCs, and more.

Sync can provide the following:

Easy-to-install protocol drivers (we call them adapters)
LoRaWAN network management, until our own WAN is developed
An MQTT broker with authentication

IT Developer

Role: Handling local compute, networking, and infrastructure.
These team members install our applications on company servers. They might not be required if everything is processed in the cloud; however, industrial internet connections are usually unstable, so local edge compute is critical.

Sync provides:

Docker images for local data processing
Local brokers and databases to prevent data loss during internet outages
Lightweight Windows binaries (very challenging, but we will deliver them)
Syncore running on the edge to minimize cloud dependency

Web Developer

Role: Building web applications.
To him, Sync can help in removing business logic from the backend. This opens the door to AI-generated apps, where developers focus on user interaction rather than making data “fit” into the application, with SQL queries, internal data modeling, etc.

In this vision, web developers only need to write:

User interface
Authentication
Simple SQL queries (often just a few lines)
Basic backend for user actions
Sync SDK integration

Tools like Replit or Lovable could generate entire applications with minimal human intervention. Since Sync handles the logic and the data management, it simplifies the developer workflow.

Sync provides:

HTTP API and SDKs, allowing users to read and send data easily.
Message brokers integration, enabling Sync to publish and receive data.
Native Brokers.
Native Relational database.
Native No-SQL database for states queries.
Event-Based database for logging events.
Database record writes, so Sync can write directly to an external database.
Grafana templates

Data Scientist

Role: Setting up Sync and developing machine-learning models.

This person is responsible for building the application inside Sync. They configure the data model for each machine and create the functions that transform the raw data provided by the OT and IT teams into meaningful, structured information that other applications will consume. Some of these responsibilities can be shared with the OT engineer or the web developer, depending on their skills and commitment.

In most cases, this will be the user who knows Sync the best. They understand not only how to interact with Sync, but also the logic and long-term vision behind the product. Sync solves a large portion of his challenges related to data normalization and preparation.

This user also develops ML models and interacts with AI agents through MCP servers to integrate AI into the project. Sync prepares datasets in real time, allowing him to avoid overusing Pandas or NumPy for data modeling and letting him focus on model selection and tuning.

Sync also works as a rapid-iteration tool. By using the rewind functionality, they can replay data many times, iterating on the database schema and transformation pipeline until the datasets match the needs of the AI model.

Sync provides:

Sync Visual Interface for setup
Python SDK for data managment
CLI for sync setup
Tables/streams to Dataframe object convertion
Logs
Real time data Vectorization

They are our most valuable user, because they adapt Sync to the real use case and shape how data flows through the entire system. We need to support him well. Clear documentation is essential, and Sync must integrate naturally into his existing tools so the transition is not disruptive. We must always remember that Sync will define and guide their data-normalization workflow.

Mission

Sync’s development will be customer-centric, just as our previous projects have been. The customer must remain at the center of the entire iteration process. This means conducting interviews, listening carefully, and understanding their needs, wishes, and frustrations. We cannot allow this practice to fade, because abandoning customer-centric development would ultimately damage the product. In fact, this will be one of our strongest competitive advantages, precisely because being truly customer-centric is one of the hardest ways to build software. In future posts, I will how we are going to do so. From this customer-centric point of view, I define Sync’s missions:

Sync’s technological mission is to use the most advanced technologies in data processing and industrial communication, and make them accessible to its four user types.
Sync’s developer experience mission is to make Sync the easiest industrial toolkit to build on, supported by excellent documentation, practical examples, robust APIs, intuitive SDKs, and ready-to-use templates.
Sync’s community mission is to create a strong developer ecosystem where users create plugins, adapters, templates, and new tools together. The goal is to empower our community so that using Sync gives professionals a clear competitive advantage in their careers and projects.
Sync’s commercial mission is to continually reduce its cost, making the tools increasingly affordable.
Sync’s usage mission is to steadily grow the number of users, increase adoption rates, and continuously lower the learning curve.
Sync’s security mission is to provide industrial-grade security by default, ensuring safe remote control.
Sync’s interoperability mission is to support an ever-growing list of industrial protocols, databases, cloud providers, and AI agents
Sync’s economic mission is to become the foundation upon which countless products and applications can be built. By enabling new solutions and empowering developers, Sync will generate jobs, create economic value, and accelerate technological progress across the industrial sector.
Sync’s physical AI and final mission: Enable safe and scalable deployment of AI agents that can observe, decide, and act on real machines.

Conclusion

As you can see, building all the tools and features described is extremely challenging. Sync has four types of users: OT Developers, IT Developers, Web Developers, and Data Scientists. Each role interacts with Sync in a different way, but all of them depend on it to simplify their work and reduce complexity.

Sync also has an almost unlimited range of possible applications. The real challenge is building software that consistently delivers value across as many of those applications as possible. It must empower people to create meaningful solutions for their organizations and for themselves. Our goal is to provide all the tools necessary to ignite creativity inside industrial environments—an area where creativity has traditionally been limited. By freeing users from repetitive and tedious tasks such as network setup and pipeline building, we can spark new projects by accelerating idea iteration, taking less time to deliver powerful apps.

“We will try to create conditions where persons could come together in a spirit of teamwork, and exercise to their heart’s desire their technological capacity”
― Akio Morita