Approvals and hand-offs sit in inboxes.

Hand-offs and approvals that run on their own.

The hand-offs that used to wait in someone's inbox, such as approvals, follow-ups and updates across systems, run on their own. A workflow is drawn as a diagram, from a two-system relay to a nine-step process across five systems, and there is no middleware to write or maintain.

Request a demo → All features →
A workflow that grows from a two-system relay to a nine-step process A new order triggers a support ticket; the canvas grows to check stock, branch, retry an invoice step and approve by rule; then it provisions the service, notifies the field team and updates the CRM and billing, with the outcomes appearing in each system. Nothing waited in an inbox. Two systems joined by one relay, with no middleware. Decisions, branches and retries, drawn as a diagram. Nine steps across five systems, one click to deploy. yesno New orderdata change · trigger Create ticketsupport desk Ran in 0.8 s Check stockwarehouse ?In stock? Reserve & invoicebilling Back-order & emailcustomer · not taken retry 2 of 3 · back-off Approveunder limit Approved · by rule Provision serviceprovisioning Notify field teamfield app Update CRM & billingCRM · billing Billing · invoice INV-7741via STRAX Warehouse · pick list issuedvia STRAX Customer · confirmation sentvia STRAX Run 4 182 · 9 steps · 6.8 s · done v7 · deployed with one click From a relay to a nine-step process, and nothing waited in an inbox.

Two systems joined by a drawn line

Connecting two systems used to mean a piece of middleware somebody had to write, host and remember. In STRAX it is a drawn line: a change in one system triggers a step in another, and the relay runs on its own from that moment. There is no code, no server, and nothing to hand over when the developer leaves.

  • Triggered by a data change, a schedule, an HTTP call or a click.
  • Runs within seconds and leaves a record of every run.
  • Changed by dragging a step, with no code to redeploy.
Live Two systems, one drawn line No code · no server · nothing to hand over
A drawn line replaces the middleware A middleware box is struck out; a line is drawn between the field app and billing, and changes then relay across it on their own, each run recorded. On data change Update billing Field app job #1042 marked complete The change simply happens here Billing invoice drafted run ✓ · 2.1 s · recorded Custom middleware code + a server + the person who left The old way: middleware to write, host and remember. Now a drawn line does the job.
A change in one system triggers a step in another, along a line that runs from the moment it is drawn.

Decisions drawn as branches

Real work has conditions: in stock or not, under the limit or over it, first attempt or third. Those decisions are drawn as branches and rules on the diagram, so the process approves what it can by itself and brings a person in only where judgement is needed. When a system is slow or down, a step retries with back-off instead of failing the whole run.

  • Branches, checks and approvals by rule, all visible on the diagram.
  • Retries with back-off and error branches, so a slow system does not become an outage.
  • People are asked only where a decision needs one.
Live Branches and rules on the diagram Auto-approve · retry · ask only for judgement
Decisions drawn as branches An order passes a rule diamond: the yes branch auto-approves and completes; a slow step retries with back-off instead of failing; a second order needs judgement, so one person is asked, approves, and it completes. rule: under R5 000, no one needed judgement needed Order received Under limit? Auto-approve Update ERP retry 2 · back-off Nadia: approval requested Done The rule approves what it can on its own. When a system is slow, the step retries. People are asked only where judgement is needed.
Branches, checks and approvals by rule, visible on the diagram, with people asked only where judgement is needed.

A nine-step process, watched live

When a process spans five systems (the CRM, billing, provisioning, the support desk and the field app) it is still one diagram, deployed with one click, with every run streaming step by step. You see where it is, what it did and what it is waiting for, and a version moves from staging to production the same way a report does.

  • One diagram for a nine-step, five-system process.
  • Versioned deployments, promoted from staging to production with one click.
  • Every run visible live and every failure explained.
Live Nine steps, five systems, one diagram Streamed live · promoted with one click
A five-system process, watched live Nine steps across CRM, billing, provisioning, support and the field app light up in sequence while the run log streams; the run completes and one click promotes the version to production. Order-to-activation CRM · Billing · Provisioning · Support · Field app 1. New order CRM 2. Credit check Billing 3. Reserve stock CRM 4. Provision line Provisioning 5. Configure CPE Provisioning 6. Create ticket Support 7. Schedule visit Field app 8. Confirm install Field app 9. Activate & bill Billing Run #88, live 09:14:02 step 1/9 · CRM · new order ✓ 09:14:05 step 2/9 · billing · credit ok ✓ 09:14:11 step 4/9 · line provisioned ✓ 09:14:19 step 6/9 · ticket created ✓ 09:14:31 step 8/9 · install confirmed ✓ Run #88 complete in 41 s, every step recorded Promote v14 → production production ✓ Nine steps and five systems on one diagram. Every run streams step by step. Staging to production in one click.
A nine-step, five-system process on one diagram, every run streamed live and versions promoted with one click.

Keep exploring

More in Build

A working portal for customers, partners and field teams.

Customers, technicians and partners get a working portal over current company data, secured per site and published to web and mobile in one step.

Sites — portals →

Reports read the same data the business runs on.

Reports and queries read the same hub the systems write to, so every figure is current, and AI writes the insight paragraphs from the report's own numbers.

Reports & queries →

Every process as it really runs, gaps included.

STRAX assembles each business process from what the systems record and what the people say, checks one against the other, and shows every gap on the diagram.

Business processes →

See it on your own systems.

A demo takes about an hour. Bring a process, a portal or a report you would like to see built on your own data.

Request a demo → Request a quote