How it works, and what it is built on

A gate is a small service placed between a sender and a receiver. It never changes either system. It checks, passes on what fits, refuses the rest with a reason, and writes everything down.

One call, start to finish

caller (A)                    gate                         receiver (B)
    |                           |                               |
    |  POST message  ---------> |                               |
    |                           |  read CSV or JSON             |
    |                           |  check against the contract   |
    |                           |                               |
    |                           |  fits?  ------ message -----> |
    |                           |  <------------ reply -------- |
    |  <--- 200 + B's reply --- |                               |
    |                           |                               |
    |                           |  does not fit? B is not called|
    |  <--- 422 + reasons ----- |                               |
    |                           |  journal: what came in,       |
    |                           |  what went out, why           |

When a gate between two systems is worth it

The sender can call a URL but cannot be taught the receiver’s rules.
The receiver expects a format, a size or a set of values of its own.
Neither side can be modified: they are vendor products, or the people who wrote them are gone.
The sender needs the answer in the same call, not in a nightly report.
Someone must be able to prove what happened.

Built on Qu4zr

This site is not a server someone maintains. It is a canvas of blocks on Qu4zr: one HTTP endpoint for the gate, a handful of short JavaScript blocks, a built-in database for the journal, and one daily job that deletes what has expired. The pages you are reading are files on the same canvas.

The same building blocks make a gate for your own systems:

Forward to a real receiver. Replace the simulated receiver with a call to your API. Credentials stay in a vault and never appear in code or logs.
Reach a system inside your network. A runner installed on one of your machines lets the gate query an on-premise ERP or database without opening a port.
Transform, not only check. Rename fields, convert dates, turn JSON into the XML or the fixed-width file the receiver wants.
Verify the caller. Check a webhook signature or an API key before anything else runs.

The endpoint is live as soon as it is described, and every change is versioned. See Qu4zr.

What stays honest about this public site

The public gates do not forward anywhere, by design: an open relay to any address is an abuse tool. They are for testing a contract, a webhook or a file, and for seeing the idea work. Limits and retention are on the privacy page.