Self-hosted data integration platform

Everyone works from the same facts

When a customer’s address changes in billing, the CRM, the provisioning system and the support desk see the change within seconds. There is no re-keying, no spreadsheet export to reconcile, and no argument about which system is right. The hub is the one place every system feeds and reads, so every screen shows the same answer.

Changes flow both ways: a correction made in any connected system reaches the others, so your teams keep the tools they already use.
Conflicts are settled field by field. If billing edits a phone number while the CRM edits an address on the same record, both survive, and every value shows where it came from.
Deletes are set per table. By default the hub keeps a record that a source removes, or it can mark the record deleted and pass the delete on to the other systems, never back to the one it came from.
Years of existing records are brought in when a system is first connected, so reports and portals are complete from day one.
Synchronisation is rate-limited per system, so a busy source is never overwhelmed by the hub keeping up with it.

Live Integration estate: 9 systems · 8 mappings · 746 tables into the hub back to the source

Systems, owners and mappings as the metadata describes them, and the data moving between them, generated from the configuration itself.

A new system joins in days

Point STRAX at a database or an API and it works out the tables, fields, types and keys for you. The assistant proposes how they line up with what you already have, you approve the mappings, and the synchronisation is generated. There is no integration code to write and no contractor to wait for. When the vendor changes the schema next year, you regenerate.

Discovery reads the system’s own structure, so there is no data dictionary to write, and it can be re-run whenever the structure changes.
The assistant proposes the mappings with its reasoning, and you decide.
The configuration is the integration, so the diagram and the running system cannot drift apart.
A schema change means a regenerate, with no hand-written code to rewrite and retest.

Live A new system joins Discover · propose · approve · generate

Point STRAX at a database or API: discovery, proposed mappings, one approval, and the synchronisation is generated.

What changes for the business

Month-end reconciliation becomes a routine check. Customer-facing teams answer from one record instead of three screens. Reports, portals and workflows are built once, on data that is already correct, and when a system is eventually replaced the hub keeps the history while the new system runs beside the old one until it takes over.

Live One record, every screen One record on every screen, nothing to reconcile

Customer-facing teams answer from one record, and month-end reconciliation becomes a quick check.

Common questions

What people ask about integration engine.

Does STRAX replace the databases our systems already use?

No. Each system keeps its own database and its own screens. STRAX adds a hub, a SQL Server database on your own servers, which every connected system feeds and reads, so they all agree on the same customer, order and asset.

How quickly does a change reach the other systems?

A change made in one system reaches the other systems that need it within seconds, in both directions, without anyone re-keying it. Synchronisation is rate-limited per system, so a busy source is never overwhelmed.

What happens when two systems change the same record?

Conflicts are settled field by field. If billing edits a phone number while the CRM edits an address on the same record, both changes survive, and every value shows which system it came from.

What happens when a record is deleted?

You decide per table. By default the hub keeps a record after a source system removes it. You can instead have the hub mark the record deleted, keeping the row and the date, and pass the delete on to the other systems, which either remove their row or set a column that means deleted. A delete is never sent back to the system it came from.

Keep exploring