Blog
Ideas and patterns for shipping APIs safely—lifecycle, gateway policy, workflows, developer portal, observability, and AI agent access—without vendor lock-in.
Written for platform, security, and integration leads who run Zerq on-prem, hybrid, or cloud.
Subscribe via RSSUpdated when we publish—no inbox required.
Featured
Gateway, MCP, workflows, developer portal, observability, and compliance in one self-hosted platform. Why we built Zerq this way.
Looking for a Kong alternative? Map every Kong service, consumer and plugin to a self-hosted gateway with built-in audit, AI agent access and flat pricing.
Read articleAI agents in open banking will reach your account and payment APIs through TPP apps and your own assistants. Separate their identities and keep SCA in place.
Read articleAn AI gateway can mean an LLM gateway for outbound model calls or an agent gateway for inbound API calls. How they differ, where they meet, and which you need.
Read articleAn API governance framework where every policy maps to an enforced gateway control and evidence, with a YAML mapping, audit log example and maturity checklist.
Read articleChoosing an API management platform for a regulated enterprise: eight requirements as RFP questions, a reference architecture and a two-week POC test plan.
Read articleWhat the SAMA framework asks of a bank platform team for Saudi open banking, and how to run the AIS and PIS API layer, logs and audit trail inside the Kingdom.
Read articleAI agent change control at the API gateway: how to scope Management MCP roles, stage writes as drafts, audit every change, and keep humans in the loop.
Read articleCan banks rate limit TPPs under PSD2? Nothing forbids it, but open banking API rate limits must be sized from capacity, applied evenly to TPPs and evidenced.
Read articleOpen banking TPP onboarding on Zerq: check authorisation and certificates, issue sandbox and production profiles, run a go-live gate, and offboard cleanly.
Read article