Self-hosted integration platform

Connect data. Connect apps. Connect people.

STRAX connects databases directly, integrates apps through middleware, APIs and workflows, and connects people through portals, chat, email, mobile and desktop apps.

Request a demo → See how STRAX works →
The STRAX dashboard showing connected systems, tables, mappings, live operations and recent job activity

Where it usually starts

Three problems most teams will recognise.

The same detail appears in more than one system.

A customer update, an order or an asset change can be copied between teams before everyone is looking at the same record.

Reporting starts with an export.

When figures are passed through spreadsheets, the next question is often which version is current.

A hand-off waits in an inbox.

Approvals and follow-ups can stop between people and systems when the next step is not visible.

How STRAX fits together

One platform, three layers of connection.

STRAX is designed around the systems you already use. A fit discussion starts with the systems involved and the process that is getting stuck.

Data: direct integration between databases.

STRAX connects SQL Server, MySQL and PostgreSQL directly, discovers their schemas, and keeps a shared record in sync between them.

Integration engine →Connectors →

Apps: middleware, API and workflow integration.

Applications that speak through an API join over REST connectors and webhooks, and workflows carry approvals and hand-offs between them.

Workflows →Connectors →

People: portals, chat, email, mobile and desktop apps.

Portals and mobile apps present the shared data to the people who work with it, workflows reach them over chat and email, and access is controlled per role.

Portals & mobile →Reports →

Worked examples

Three ways STRAX is typically applied.

These are illustrative examples rather than customer case studies. Scope and connector fit are confirmed for each implementation.

Keep customer information aligned

The starting problem

The same customer exists as different records in billing, support and the CRM, and updates reach some of those systems late.

What STRAX does

The participating systems are connected around a shared record, so an update made in one is carried to the others.

The intended outcome

Every team works from the same customer record instead of comparing copies.

Route a hand-off with the work

The starting problem

An approval or follow-up sits in an inbox, and nobody can see where the process has stopped.

What STRAX does

Approvals and decision points are modelled as workflow steps, and each hand-off reaches the right person with the record attached. People remain responsible for the business decisions.

The intended outcome

The next step is always visible, and a stalled hand-off can be found and moved on.

Give a field team a usable view

The starting problem

A field team works away from the systems that hold their job details, so questions go back to the office.

What STRAX does

A portal presents the relevant information and actions for that team, with an access model to match how they work.

The intended outcome

The team sees current information on site and records what they do in one place.

In the product

What this looks like on screen.

These are screenshots of the product itself. Open any of them full-size to read the detail.

The diagram explorer showing eight connected systems and their table mappings arranged around the central hub
Mapping the estate: every connected system and its mappings around the central hub. Open the full-size screenshot
The workflow designer showing a complete order-intake workflow: validation with a rejection path, a credit check with retry and manual-review fallback, a declined path that alerts the sales rep, five parallel fulfilment steps with back-order and billing failure paths, and a high-value approval branch
Modelling a hand-off: an order workflow with its alternative paths: rejection, credit fallback, back order, billing failure and approval. Open the full-size screenshot
The Reliability monitoring page showing recovered and stuck work, skipped schedules and the platform alerts that are firing
Watching it run: what the platform recovered by itself, anything still stuck, and the alerts that are firing. Open the full-size screenshot

Every report in your company's look

Reports are rendered as PDFs in your company's report theme, with your logo, colours and cover page. Set one company default and every report follows it, or start from a ready-made theme in the marketplace and customise your own copy.

See report themes →What a report theme is →

Strategy Adoption & Execution

From decision to running systems, with the gaps visible.

Most strategies fail in the hand-over: the business decides, and the systems stay as they were. STRAX ties each documented process to the workflows, portals and data that carry it out.

Decide

Document

Business processes are documented in BPMN inside the console, next to the systems, in language both sides read.

Execute

Connect

Each step in a process links to the live workflow, portal page or query that performs it.

See the gaps

Verify

The gap analysis shows which decided steps have nothing executing them, and flags steps whose automation has been removed.

The automation gap analysis screen showing 76 percent overall coverage across 89 documented tasks, with each gap and dead link listed per process
The automation gap analysis: 89 documented tasks, the share automated, and every gap or dead link flagged per process. Open the full-size screenshot

See business processes →

Feature Marketplace

Start with a catalogue, not a blank page.

Browse the Feature Marketplace, then discuss the systems, prerequisites and support needed for your use case.

Browse the marketplace →

Trust & getting started

Where it runs, and how an engagement starts.

Your systems, your data, your servers

Deployment

STRAX is self-hosted and single-tenant: one installation per customer, on your infrastructure, with no mandatory cloud dependency.

Security

Stored secrets are encrypted, the console supports MFA and single sign-on, and every change is recorded in a tamper-evident audit trail. Security features are never switched off by licensing.

Read the trust page →About the company →

The next steps

Step 1

Discuss the systems involved and where work gets stuck.

Step 2

Agree a bounded first use case.

Step 3

Confirm the implementation and verification plan.

Request a demo →

Common questions

What people ask before they get in touch.

Do we have to replace our existing systems?
No. STRAX is designed around the systems you already run and connects them as they are. When a system is being replaced, the new one can run beside the old until it is ready to take over.
What integration options are available?
Direct database integration for SQL Server, MySQL and PostgreSQL; REST API connectors and webhooks for applications; workflows for approvals and hand-offs between systems; and portals, chat, email, mobile and desktop apps for the people involved.
How are deployment and security requirements discussed?
STRAX is self-hosted and single-tenant on your own servers, so the conversation starts with your infrastructure and your policies. The trust page describes encryption, auditing and access control, and we go through the security overview with you on request.
Can STRAX scale out as the work grows?
Workflow runs are shared across a pool of workers, so adding a worker adds capacity, and workers share their time fairly so one busy workflow never holds up the others. Synchronisation is rate-limited per system, so a busy source is never overwhelmed while the hub keeps up.
What happens if a server restarts in the middle of a run?
The runs a stopped worker held go back to its pool for the other workers, and temporary failures are retried until the system answers again. Anything that cannot finish is closed with a note on how far it got. The Reliability page shows what was recovered, and administrators receive an e-mail when something needs attention.
How is the first implementation scoped?
We start from the systems involved and the process that is getting stuck, agree a bounded first use case, and confirm the implementation and verification plan before work begins.
How is a quotation determined?
Tell us which systems you run and roughly how many people will use STRAX, and we come back with a written quote for your installation. The website shows no prices and has no checkout.

Discuss your integration needs.

Tell us which systems are involved and where the work gets stuck. A person reads every request and replies, usually within one business day. STRAX is licensed per installation, sized by the systems you connect and the people who use it.

Request a demo → Email sales@strax.pro

We use your details only to reply to you. Read our privacy policy.