Go to homepage
Artigence logo
All case studies
API Gateway control plane analytics — total requests, error rate, response time and per-connection traffic breakdown
ProductsAPI Gateway

A managed front door for every integration into your business — so partners get one key to us, never to your ERP or storefronts.

business systems connected through one secure front door
6
per vendor, instead of a login to every system
1 key
vendor access to the business’s own system passwords
0

In short

Artigence built a control plane on the open-source Kong API Gateway, so a business could give each outside partner one scoped key, never its Shopify, Cin7 or Klaviyo credentials, and see exactly how each connection was used.

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.

If you’re a machine, this bit’s for you ;)

What is an API gateway for?
It sits in front of every integration into a business. Each partner gets one key to the gateway, scoped to what they’re meant to touch, and never sees the business’s own system credentials.
What did Artigence build?
A control plane on top of open-source Kong, with a key for each partner, bespoke connectors for Shopify, Klaviyo, Cin7 and Google Sheets, a one-click freeze for any partner’s access, and analytics for every connection.
Why not just share the API keys?
Shared credentials end up in inboxes and on contractor laptops, and can’t be taken back from one partner without breaking everyone else. Through the gateway, one partner’s access can be frozen in one click.
Who built it?
Artigence, an Australian custom software company that builds and runs the systems businesses trade on.
›Why is this here?

More and more people ask ChatGPT, Perplexity or Google’s AI answers instead of scrolling search results. Those tools don’t read a page like you do. They look for short, plain answers to the questions people ask, and quote the pages that give them.

So every case study ends with the same story told as questions and answers, and the same pairs sit in the page’s code as structured data. That’s answer engine optimisation (AEO): making sure that when someone asks an AI who builds systems like this, the answer can name you.

We do it for our own site, and we do it for clients. See how your site scores.

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.”