
Sync engine to share data across engineering teams in enterprises
We turn complex API integrations into drop‑in full‑stack libraries
At ReJot, we're building a synchronization engine to greatly reduce the complexity of data sharing between backend services within enterprises. The traditional approach is Event Streaming, where events are published to a platform like Kafka. Kafka not only requires significant effort to operate, it also forces engineers to use events. Events come with inherent complexity—they encode something happening rather than something being (i.e., state). Our approach is based on replication, where state is transferred directly instead of requiring a back-and-forth conversion to events. We provide primitives to enable teams to break data silos, while keeping in mind data ownership and provenance. Teams define what data their backend publishes and requires, and we'll make sure everything is reactively up-to-date. ReJot works on top of existing infrastructure such as Postgres.
ReJot is building Fragno to let API companies go from simply exposing an API to offering drop-in integrations that work out of the box. Fragno is an open‑source framework for packaging backend endpoints, data storage patterns, and frontend utilities into reusable building blocks. API providers ship full integrations, not just low‑level SDKs and docs. Customers configure rather than write code, so integrations are both much faster to launch and far more consistent across customers.
ReJot shifted from building a data synchronization engine for internal enterprise services to an open-source framework enabling API providers to ship drop-in integrations; this is a notable product pivot, moving from backend data sync to turnkey API integration tooling.