Frequently Asked Questions
Plain answers on what STRAX is, which systems it connects, where it runs, data safety, the AI copilot and how to evaluate it.
What is STRAX in one sentence?
STRAX is an integration hub that connects your systems to one canonical data model, keeps them synchronised, and lets you build portals, workflows and reports on top. Read What is STRAX for the longer version.
Which systems can it connect?
STRAX connects directly to SQL Server, MySQL and PostgreSQL databases, and to any reasonable REST API. The marketplace adds more than 150 pre-built connector profiles for platforms such as Splynx, NetBox, HubSpot, Shopify and Zendesk. A profile gives you a tested starting point instead of a blank configuration. Systems without a profile can still be connected through the guided wizard, as described in Connecting systems.
Does STRAX replace my existing systems?
No. Your billing platform keeps doing billing and your CRM keeps doing sales, each remaining the system of record for its own work. STRAX sits alongside them and keeps them in step, so a customer updated in one place is correct everywhere. Teams carry on in the tools they already know.
Where does STRAX run?
STRAX is installed for your organisation, in your own environment, whether that is your data centre or your cloud tenancy. Your data stays where you put it and moves between your systems and your hub. There is no shared multi-tenant service holding your records.
Is my data safe?
Access is controlled through roles, with two-factor authentication and single sign-on available per installation. Connection credentials are stored encrypted and every significant action is recorded in an audit trail. Because the installation is yours, your data never leaves your environment to reach us. The trust page covers our security posture in more detail.
Can business users use it?
Yes, through portals. A portal is a clean web application over hub data, built for a specific audience such as field technicians or customers. Using one requires no technical knowledge at all. Building integrations and portals is a job for your technical team, and the AI copilot assists them throughout.
What does the AI copilot do?
The copilot reads your connected systems and proposes mappings, table designs, portal pages and explanations of what it sees. It turns hours of manual matching into a review session, which is where most first-week time savings come from. It can also answer questions about your integration landscape in plain language.
Can the AI change things without approval?
No. Every change the copilot proposes is presented for review, and a person accepts or rejects it before anything takes effect. The copilot never alters your model, your mappings or your data on its own authority. Approvals are recorded in the audit trail like any other change.
How long until we see value?
Most organisations connect their first system and see data flowing in the hub on day one. A first portal or scheduled report typically follows within the same week. The getting started page walks through a typical first week in detail.
How do I evaluate STRAX?
The best evaluation is a live demonstration against a system you actually run. Request a demonstration and we will connect a source, map it with the copilot and show data moving, live. You judge the result on your own data rather than on a slide deck.
Do you publish prices?
No. Pricing depends on your organisation's size, the systems involved and the capabilities you need, so a published list would mislead more than it informs. Request a quote and we will price your situation specifically.