Join a publisher's house

Available now A publisher's house is its sandbox on SOM Managed Bus, where its

vendors' systems exchange SOM messages. When a publisher invites your organisation, you join from your own vendor workspace, on the portal's Houses you're in page.

Accept an invitation

A publisher invites you in one of two ways:

• By email, to one person. If your organisation is new to SOM Managed Bus, the email's link opens the access request form with the invitation attached: send it from the invited address and your organisation is approved at once, with a vendor workspace on the minimal tier. Then sign in, accept the invitation to your workspace, and open Houses you're in.
• From the vendor directory, if you listed your organisation (below). The invitation shows to your workspace's owners and admins.

The portal shows open invitations at the top of the page. An owner or admin of your vendor workspace presses Read the terms and join, reads the house terms, and accepts them for the organisation. The invitation works once, and expires after 14 days.

The house terms (version house-2026-09):

• The house is a shared bus: messages your connected apps publish, and their payloads, reach every connection the house grants them to.
• The publisher sees counts of your accepted, refused and duplicate messages per connection, and when each was last seen. It never sees your rule ids, paths or other verdict detail, unless you share a results statement with it.
• Other vendors in the house see payloads, never your verdicts.
• The publisher's consent to RND support access covers your traffic in its house.
• Your traffic in the house counts against your own allowance, never the house's.
• The publisher grants what each of your connections may publish or receive, and either side can disconnect at any time.
• The sandbox takes synthetic test data only.

Support access Available now: an owner of the house can let RND read the house for up to 7 days, read-only. RND then sees what the house sees of your traffic there: the payloads in its story timeline, and your connections as counts, never your refused messages or credentials. Nothing of your own workspace is included: only its own owners can grant RND access to it. Without a grant, RND never sees payloads, yours or the publisher's. See Let RND look.

Connect your apps

Press Connect an app on the house, pick one of your organisation's apps, and ask for what it needs:

App	You ask for
Producer	The system_ids it publishes as, and the message types it publishes
Consumer or skill	The message types it receives, and optionally a topic prefix

The house grants what you asked for, or less, or rejects it with a reason. Nothing reaches the bus until it is granted. Your system_ids are yours across the bus, as in your own workspace.

Get the connection's client secret

Once granted, a developer presses Get client secret. It is shown once: copy it then. It works in this house only, and it is yours: the publisher never sees it and can't rotate it. Rotate it from the same page, with an overlap for the old secret, as for your own connections (Credentials).

Then use the house's routes, exactly as in your own workspace but with the house's workspace id:

• a producer gets a token and publishes to …/v1/tenants/<house>/messages (Authenticate);
• a consumer reads its queue over the HTTPS pull API at …/v1/tenants/<house>/consumers/<connection>/messages.

The secret panel shows every URL.

Replay and redrive in the house

A developer, admin or owner of your vendor workspace can Replay a time range from the house's archive into one of your consumer connections there, or Redrive DLQ its dead-letter queue back to its queue, from the connection on Houses you're in. The same limits apply as in your own workspace: one of each at a time, 3 replays and 10 redrives per connection per day. The publisher sees that it happened, when, the range or count and how it ended, recorded as your organisation; it never sees more of your messages than it already could. See Dead-letter queues and replay.

Your results in the house

Press Your activity here on a house: your connections' decisions in that house for the last 7 days, in full, with the rule behind every refusal. The publisher sees only their counts. See Who sees what in a house.

Rehearsals

A publisher can rehearse a newsroom workflow through its house. The rehearsal's synthetic messages reach your consumer connections in that house whose filters match, like any message there. You can tell them apart by their producer: sombus-rehearsal, or sombus-standin-<role> for an RND stand-in. The publisher may cast one of your connections in a role (its newsroom system, say): the rehearsal then cues that step and counts what your connection published in the next 30 seconds. It sees counts only, never your verdict detail.

You're told: each rehearsal, and each reset of the house, is recorded in your organisation's audit log, and shown for a day on Houses you're in. A reset clears the messages waiting in your consumer connections' queues and dead-letter queues in that house; your connections and grants stay.

Emails about your connections in a house

Your vendor workspace gets notification emails about your connections in every house you joined, as for its own: a rotated secret's overlap ending, a producer connection near its daily allowance, a consumer connection's growing dead-letter queue or lag (by your own lag threshold), and Refusals in houses when 25% or more of a connection's messages in an hour were refused, with the rules that refused the most. They go to whoever your workspace chose under Notifications, and link to Houses you're in. They carry only your own connections: nothing about other vendors or the house's own connections. The house gets its own emails, with counts only.

Disconnect, or leave

A developer can disconnect one connection (or withdraw a request); an owner or admin can leave the house, which disconnects all of your connections. Before you confirm, the page shows what is kept: messages already accepted stay in the house's timeline until they expire (7 days), decisions stay in the decision log for 30 days, a consumer's queue is deleted with its messages, and both audit logs keep a record for a year.

The publisher can disconnect your connections or remove your organisation from its house in the same way.

Be found in the vendor directory

Publishers can find vendors that choose to be listed, and invite them by name. Listing is off unless an owner or admin of your vendor workspace turns it on, with an optional line about what you build. Only your organisation's name, website and that line are shown. Take it off at any time.

Share results with a house

On Results statements, Share with a publisher lists the publishers of the houses you're in: pick one instead of typing its organisation id. See Results statements.