Integration glossary
Self-hosted integration platform
A self-hosted integration platform is software for connecting business systems that you install and run on your own servers, so the data it moves stays on infrastructure you control.
Hosted and self-hosted integration
Many integration tools are offered as a cloud service: the vendor runs the platform and your data passes through its infrastructure on the way from one system to another. That is quick to start and asks nothing of your own IT team.
A self-hosted platform does the same job on servers you choose, in your data centre or your own cloud account. The data moving between your systems never leaves infrastructure you control.
Why companies choose to self-host
-
Data residency and privacy rules, such as POPIA or the GDPR, are easier to meet when personal information stays on your own servers.
-
Databases inside the company network can be connected directly, without opening them to an outside service.
-
Upgrades happen when you schedule them, so a vendor change never surprises a running process.
-
Security reviews deal with one installation you can inspect, instead of a shared service you cannot.
What you take on
Self-hosting also means running the platform: servers, backups, monitoring and upgrades become part of your operations. A good self-hosted platform keeps that work small, with an installer, health monitoring and versioned upgrades you can roll back.
STRAX is self-hosted
STRAX is self-hosted and single-tenant. It runs on Windows Server through its installer, or on Linux for the API and pipeline services, with Microsoft SQL Server for its databases, on your own physical or virtual infrastructure. We install it with you, and your business data never passes through our servers.
How STRAX protects your data → The STRAX integration engine → What iPaaS means →
More terms
Other ideas worth knowing.
iPaaS (integration platform as a service)
Integration delivered as a cloud service, where the vendor hosts the platform that connects your applications.
Read the definition →Data hub
A central store that every connected system feeds and reads, so they share one current version of each record.
Read the definition →Change data capture (CDC)
Passing on only what changed in a database, shortly after it changed, instead of copying whole tables on a schedule.
Read the definition →See it on your own systems.
A demo takes about an hour and shows these ideas working on systems like yours.