Do I need an API gateway if developers want self-service changes?

Not necessarily — but an API gateway can help a lot, depending on what “self-service changes” means.

You likely want an API gateway if developers need to self-serve:

• Create or publish APIs without ops help
• Manage authentication, rate limits, and keys
• Version APIs and route traffic safely
• Apply consistent policies like logging, throttling, CORS, and quotas
• Expose internal services securely through a controlled entry point

In that case, the gateway becomes the place where developers can make changes in a governed way, rather than asking a central team for every update.

You may not need one if:

• Developers are only changing their own service internals
• You have a small system with simple routing
• You already have another layer handling ingress, auth, and policy
• “Self-service” just means deploying code independently, not managing API exposure

A common rule of thumb

If you need centralized control + decentralized development, an API gateway is often useful.

But note

A gateway alone doesn’t guarantee self-service. Usually you also need:

• good CI/CD
• infrastructure as code
• API specs and templates
• clear governance/approval rules
• portal/documentation for developers

If you want, I can help you decide with a quick checklist based on your architecture and what “self-service” means in your team.