The gateway would sit in front of systems that cannot be exposed casually, so the defaults are conservative, the surface is small, and every commitment below goes into the engagement documents rather than staying on a web page.
Authenticated or anonymous, depending on the rules you set for that class of caller.
The gateway checks what that caller is entitled to see, including which price and which documents.
The read goes to the ERP, PIM or price service where the data already lives, inside your network or through an agreed endpoint.
What was asked, what was returned, what was refused. The log is delivered to you, and nothing is retained to build a second copy of your catalogue.
No copy to our side, no re-hosted product data, no shadow database that drifts from the source of truth.
The first month allows reads and no writes. An agent may look; permission to order is granted by you, after you have read the log.
Access control and per-buyer pricing stay yours. Anonymous callers see what you allow, contract customers see their own terms and nothing else.
Caller, query, response code, fields returned, refusal reason. That log is the artefact you take to your own board.
Inside your VPC or in ours, SSO on the control plane, role separation between operator and viewer, retention set by your policy rather than ours.
Signed records and published keys verify offline. If our service disappears, the records you issued still prove what they proved.
Records are signed with Ed25519, evidence is bound by its sha256 fingerprint, and the document follows the W3C Verifiable Credentials data model, so verification does not depend on our code being installed anywhere. Status is published as a list, so a withdrawn record reads as withdrawn rather than disappearing silently.
Each claim carries its basis separately: measured by inspection, self-declared by the manufacturer, or asserted by a named third party. A buyer comparing two suppliers can see which statements rest on evidence and which rest on a declaration, and can verify the fingerprints without an account.
The record format is deliberately host-agnostic. The same documents verify whether they are served from a container, a CDN or a public canister on a decentralised host such as the Internet Computer, which is one of the options we offer when a record has to remain verifiable even if we are gone. Customer catalogues are never hosted there and never leave the customer's own systems.
| Item | Status |
|---|---|
| NDA and data processing agreement | Signed before any catalogue access; standard documents available on request |
| Data residency | European Union by default, with a United States region for a US-only deployment |
| Identity | SSO against your provider; no shared passwords and no standing access for our staff |
| Kill switch | You can revoke the gateway, or a single tool, without a change window and without informing us first |
| SOC 2 or ISO 27001 | Not held. We will not imply a certificate we do not have. A pilot runs under contract, inside your controls, which is the arrangement that makes an uncertified supplier reviewable |
| Penetration test | Available on request for an enterprise engagement, at our cost in the first year |
Only a scoped read credential, issued by you, revocable by you, rotated on your schedule. Preferable is an endpoint you expose inside your own network, so no credential leaves your perimeter at all.
It reads. The blast radius is disclosure of what you allowed that class of caller to see, which is why the first month is read-only and the rules start restrictive. We notify you within 24 hours of confirming an incident, in writing, with the log.
Yes. The gateway can be deployed into your VPC and operated by your team, with us providing the licence and the integration work. Some enterprises require that, and it changes nothing in the commercial terms.
No. Your catalogue is not used to train anything, ours or anyone else's, and no buyer data is shared between customers.
Send your questionnaire and we will answer it in writing before any commercial conversation, including the parts where the honest answer is that we are small.
hq@arliwork.com · Shenzhen Capernaum Technology Co., Ltd · PIAKHOUSKI DZMITRY