SignalWeaver

Connect your business through events

Keep partners informed.
Let each business act.

Create your SignalWeaver accountSee how it works

An order is ready. A document is approved. A delivery is complete. The right applications and partners need to know.

SignalWeaver connects those business events to registered subscribers. Your application announces what happened; each receiving business controls its own response.

The connection should support the business

Every new partner brings another connection to manage.

Custom notifications can leave the publishing application managing who to contact, where to send the update, and what each partner expects.

Manage who receives each event through SignalWeaver subscriptions, without choosing each destination in the publishing code. Your application announces what happened; each partner controls its own response.

01 The core interaction

See the event travel.
See the response stay independent.

The publisher owns the information. SignalWeaver delivers the event. The subscriber uses the correlation ID to get the matching details directly from the publisher.

Why SignalWeaver exists28 seconds AI narration: Dan Dan
Read the video sequence
  1. The publishing application raises an event carrying correlation ID ABC-123.
  2. SignalWeaver delivers that event to the subscribed receiving application.
  3. Immediately after receiving it, the subscriber sends an inquiry directly to the publisher using ABC-123.
  4. The publisher returns the matching details directly to the subscriber. The inquiry and response bypass SignalWeaver.
Read the narration

Three independent systems. One connected exchange. Your application publishes an event and a correlation ID. SignalWeaver notifies the subscriber. The subscriber uses that ID to ask the publishing application directly for details. The publisher returns the information. Each application stays in control. Share the event. Keep control of your application. That's why SignalWeaver exists.

  1. 01 / Publish

    Share what happened.

    The publisher raises a lightweight event with a reference to the information behind it.

  2. 02 / Notify

    Reach the subscribers.

    SignalWeaver delivers the event so each receiving application can run its own response.

  3. 03 / Inquire

    Get context at the source.

    The subscriber uses the correlation ID in a direct inquiry. The publisher returns the matching details.

An illustrative business scenario

An order is ready. Two partners have work to do.

  1. Your business

    Announce that the order is ready.

    Your fulfilment application publishes the event.

  2. Delivery partner

    Prepare the collection.

    Its application receives the notification and asks for the authorised collection details.

  3. Billing partner

    Prepare the invoice.

    Its application receives the same event and retrieves the information it needs for its own process.

One shared event. Separate applications, access permissions, and business decisions.

02 Across organisations

One event.
Two external business partners.

Now extend the same pattern. Two partners subscribe to the event. Each runs its own application, inside its own organisation, and independently retrieves information from the publisher.

One event. Two business partners.28 seconds AI narration: Dan Dan
Read the video sequence
  1. The publishing application raises one event carrying correlation ID ABC-123.
  2. The animation shows SignalWeaver notifying both external partner applications in parallel.
  3. Each subscriber immediately sends its own direct inquiry to the publisher using ABC-123.
  4. The publisher returns the matching details directly to each partner.
  5. Solid boundaries identify three separate organisations. SignalWeaver sits outside those boundaries; neither partner's inquiry or response passes through the other partner.
Read the narration

One publisher. Two external business partners. The publishing application raises one business event. SignalWeaver notifies both subscribers. Each partner uses the same correlation ID to request details directly from the publisher. Each receives the information it is authorised to access, within its own organisation. One shared event. Independent businesses, each in control of what happens next.

The boundary stays with the business.

The publisher and the two subscribers belong to three distinct organisations. Each partner owns its application and decides what to do when the event arrives.

Each inquiry goes back to the source.

Both partners use the same correlation ID in separate exchanges with the publisher. Each retrieves the information it is authorised to access through an agreed interface.

The animations illustrate the communication pattern. Actual delivery and response timings can vary.

Before you connect

Clear responsibilities from the start.

What is SignalWeaver, and what does it manage?

SignalWeaver is a business event notification service that connects publishing applications with subscribers, including external business partners. It brings publishers, subscribers, and registered event contracts together, using subscription relationships for publication and delivery. Each participating business remains responsible for its own information and downstream work.

Do our applications still need an integration?

Yes. A receiving application needs a supported way to receive the event, such as the SignalWeaver SDK, and agreed access to any details it requests. The publisher raises the event without choosing each destination in its publishing code.

What happens after I create an account?

Your account is the starting point for configuring publishers, event contracts, and subscriptions. Publishing and receiving events also requires the participating applications to be integrated.

Start with one business event

Connect the partners
who need to know.

Create your account and begin setting up your first publishing application.

Create your SignalWeaver account

Want help planning your first connection?
Book a conversation