Build and export production-ready Azure API Management (APIM) XML policies instantly. Visually configure JWT token validations, CORS, rate limits, HTTP retries, IP filters, and AI semantic vector caching.
No reviews yetBe the first to leave a review for ApexAPIM Policy Builder
Maker
📌
Hello Product Hunt community! 👋
I'm Anand Babu, founder at sunverge.ca / anandtechinc.
If you've ever set up an API gateway on Microsoft Azure, you know that writing and editing Azure API Management (APIM) XML policy files can be tedious. Wading through pages of documentation just to find the correct syntax for a validate-jwt or rate-limit-by-key policy wastes a lot of developer time.
To solve this, we built ApexAPIM Policy Builder—a visual playground where you can toggle your inbound backend, outbound, and on-error policies, adjust thresholds, and get clean, production-ready XML code instantly.
Key Features:
🛡️ Security: Visual configurations for Entra ID JWTs, client certificate checks, IP filters, and PII scrubbing.
⏳ Traffic Control: Easy rate-limiting, quotas, and retry configurations.
🧠 GenAI Support: Azure's new XML blocks for TPM token-limiting and Semantic vector caching.
🔒 Privacy: 100% client-side static site (your configurations never leave your machine).
It is completely open-source and free to use. I'd love to hear your feedback, feature requests, and suggestions for more policy tags!
Thank you for your support! ☕💜
Report
The visual JWT validation setup alone is worth it, no more hand-writing XML and praying the issuer URL matches. Exported clean and pasted straight into my APIM instance without a single tweak.
Report
Finally something that handles APIM policy XML without making me hand-craft those backend blocks. The JWT validation setup was surprisingly quick and the export came out clean enough that I just dropped it straight into our stg environment.
Report
The visual builder looks slick, especially for wrapping my head around all those JWT validation policies. One thing that would save me a ton of time is a "compare and merge" view where I can see my current policy XML side by side with the new one generated by the builder. It would make it way less scary to adopt this when I have tons of existing custom backend service configs to migrate.
The visual JWT validation setup alone is worth it, no more hand-writing XML and praying the issuer URL matches. Exported clean and pasted straight into my APIM instance without a single tweak.
Finally something that handles APIM policy XML without making me hand-craft those backend blocks. The JWT validation setup was surprisingly quick and the export came out clean enough that I just dropped it straight into our stg environment.
The visual builder looks slick, especially for wrapping my head around all those JWT validation policies. One thing that would save me a ton of time is a "compare and merge" view where I can see my current policy XML side by side with the new one generated by the builder. It would make it way less scary to adopt this when I have tons of existing custom backend service configs to migrate.