Getting Started

What adopting STRAX looks like, from your first sign-in to live data movement and your first portal, typically within a week.

An installation of your own

STRAX is installed for your organisation, so your data stays in your environment from the first day. Exousia sets up the installation with you and hands over a web console ready for use. You sign in with your own account, protected by roles and optional two-factor authentication. Everything that follows happens in that console, in a browser, with no tooling on your desk.

Day one: connect a system

The guided connection wizard walks you through joining your first system to the hub. You choose the type of system, such as SQL Server, MySQL, PostgreSQL or a REST API, and supply its connection details. Credentials are stored encrypted and are never shown again in the console. The wizard then reads the system's structure and shows you every table and field it found.

Demo ISP, our running example, starts with Splynx, the billing platform its finance team lives in. Within an hour the console holds a complete picture of Splynx's customers, invoices and payments.

Day one, continued: map it to the canonical model

Every organisation on STRAX builds one canonical model, a single agreed shape for customers, products, orders and the rest. The AI copilot studies your newly connected system and proposes how its tables and fields line up with that model. You review each suggestion, accept the good ones and adjust the rest. A person approves every change before it takes effect, so the model stays deliberate rather than accidental.

For a first system this mapping session usually takes an afternoon. See How STRAX works for the thinking behind the canonical model.

Same day: watch the data flow

Once the mapping is approved, you ask STRAX to bring the integration to life and load the existing data. From then on the hub tracks changes continuously and keeps the two sides in step. The console shows records moving in and out per system, live, so you can confirm the flow with your own eyes. Most teams see their first data arrive in the hub on the same day they connected the system.

The rest of the week: build on the hub

With one system flowing, the platform's delivery features open up:

• Connect a second system, such as NetBox or HubSpot, and map it to the same model. Two systems mapped to one model stay synchronised with each other automatically.
• Publish a portal that gives field staff or customers a clean view of hub data, with no console access needed.
• Set up a scheduled report that lands in a manager's inbox as a PDF.
• Add a workflow that reacts when a record changes, for example alerting the network team when a service is suspended in billing.

Demo ISP ends its first week with Splynx and NetBox in step, a technician portal live and a daily revenue report running. Browse the marketplace for pre-built profiles covering Shopify, Zendesk, HubSpot and over 150 other systems.

See it with your data

The fastest way to judge STRAX is to watch it connect a system you actually run. Request a demonstration and we will walk your team through a first integration live.