A managed front door for every integration into your business — so partners get one key to us, never to your ERP or storefronts.
For a wholesaler running storefronts over an ERP, every partner wants credentials — to read orders, push stock, send a campaign. Handed out raw, those keys end up in inboxes and contractor laptops. Our Gateway sits in front of every integration; each partner gets one key to us, scoped to what they’re meant to touch. They never see your Shopify or Cin7 credentials, and you can see exactly what they’re doing with the access you gave them.
Kong is the engine underneath — battle-tested for routing, auth, rate-limiting and logging. We didn’t fork it or rebadge it. What we built is the layer on top — the control plane operators use day to day, and the parts of a gateway that make it something a business can run, not just an engineering team. Kong handles a request in milliseconds; we own the rest.
What we owned
- Per-connection analytics in a single control plane — total requests, error rate, average response time, top endpoints, and traffic split by connection type (Cin7, Shopify, Klaviyo).
- One shared key per app, scoped per connection — a partner’s key can’t reach a connection they aren’t subscribed to, enforced at the gateway, not by trust.
- Readable URLs per integration (e.g. /gateway/<brand>/<region>) layered over the default — additive, so changes never break a partner already pointed at the old one.
- Secure share — a passcode-protected, expiring, one-time link that hands a partner every endpoint and the shared key. Revoke their access and the link goes dark.
- Per-app kill switch with a recorded reason — freeze a partner’s access in one click without touching the key in their hands.
“Kong moves the traffic. We built the part the business runs on.”
