What an outbox means in practice
An outbox (sending box) is a table in the application database. When something happens that should be passed on, for example a card badge-in or the closing of a permit, the application saves it as a row in this table and its work ends there. It does not open a connection to an external system and does not wait for a reply.
Outgoing webhooks can be queued in exactly this way when the plant network blocks outbound traffic from the application server: a poller, a small process on the receiving side, collects the event batch over an inbound channel. The direction of the connection is reversed: the receiver asks, and the application server does not call out.
Why outbound traffic is costly to organise
In production networks and in segments with raised protection, the default firewall rule forbids the server from initiating connections to the outside. Each exception is a request that goes through several hands: the network team, the information security team and the system owner. The cost is measured in labour hours and in waiting time, and the waiting time often delays the integration by weeks.
On top of the one-off cost there is a recurring one. A rule opened once must be reviewed during audits, documented in the change log and assessed again after every change of the recipient address. The more outbound integrations there are, the longer the list of rules to maintain.
Components of the cost of one outbound rule
It is worth splitting the cost into parts, because each one has a different owner and a different duration.
- preparing the request with the address, port, protocol and business justification
- risk assessment by information security and approval by the segment owner
- implementing the rule and testing the connection by the network team
- entry in the change log and in the architecture documentation
- periodic review of the rule during the internal audit
IT hours in the first year: outbound rules versus an outbox
- Outbound rules
- Outbox
How an outbox changes the cost structure
Instead of opening an outbound rule for each integration, the plant approves one pattern: a poller on the receiving side connects to the application server over an inbound channel that is already allowed for the system users. The request concerns one process, not every recipient separately.
Card badge-in events that InnerWeb receives from the access control system via webhook, and links with qualifications, permits, attendance and time recording, can flow back to automation platforms the same way. The platform offers a REST API (versions 1 and 2, JWT) and webhooks, so the receiver can choose the model: pickup by the poller or polling of the API.
What an outbox does not change
The queue does not shorten the audit trail: events still have to be authenticated, and the poller needs its own credentials with minimal permissions. Delivery delay depends on the polling frequency, so for events that need a reaction within seconds the interval has to be agreed with the process owner.
Example calculation of IT labour hours
The calculation below is an example based on explicit assumptions, which the plant should replace with its own figures. It is not a price list and not a promise of savings.
With three outbound integrations, 10 hours per request and two reviews a year at 3 hours per rule, the total cost is 30 hours one-off plus 18 hours a year, 48 hours in the first year. The outbox variant requires one poller configuration estimated at 8 hours and adds no outbound rules to the review. The difference in the first year is 40 hours of IT work.
When an outbox does not pay off
If the plant already has one approved, documented outbound rule to a specific recipient and reviewing that rule is cheap, the saving will be small. The same applies to an integration with a single recipient and no plans for expansion.
An outbox is worth considering when there are several integrations, when the network segment has a strict policy, or when the wait for a firewall decision is longer than the time needed to deploy the application itself. Then the queue shortens the path to a working solution without lowering the level of control.
IT labour hours: outbound rules versus an outbox
| Parameter | Value |
|---|---|
| Number of outbound integrations | 3 pcs |
| Time for one rule request | 10 h |
| Rule reviews per year | 2 times |
| Time for one rule review | 3 h |
| Poller configuration in the outbox variant | 8 h |
Result: Without an outbox: 3 x 10 + 3 x 2 x 3 = 48 h. With an outbox: 8 h. Difference: 40 h in the first year.
Note: Example calculation; the plant substitutes its own times. Does not include waiting time for decisions or licence costs.
Video
Frequently asked questions
Does an outbox require opening an inbound port?
The poller connects to the application server over an inbound channel that usually already exists for users. You need to assess whether this channel is reachable from the recipient's segment and, if necessary, approve one rule instead of several.
How does an outbox differ from a plain webhook?
A webhook is an outbound call made immediately after an event. An outbox saves the event in a table and hands it over later, when the recipient asks for it, so it also works when outbound traffic is blocked.
What about events that must arrive within seconds?
Their delay comes from the poller's polling interval. For time-critical processes a short interval is set, or a separate path is kept under an agreed rule.
Does an outbox replace the API?
No. The platform has a REST API (versions 1 and 2, JWT) and webhooks; the outbox is one of the ways to deliver events when the network limits outbound traffic.
Let us check how many rules you really need to open
Together with your IT team we will describe the path of access control events and show where the outbox shortens the deployment. Contact us for a talk or a short demo.
Let's talk