API Gateway Resource Template (Apache APISIX)

[mustafatoktas]

Hi Coolify team 👋,

First of all, thanks for the amazing work on Coolify.
I'm running a self-hosted Coolify instance and actively developing multiple APIs (Ktor-based), and one missing building block I’ve noticed is an API Gateway resource.

Why Apache APISIX?

Apache APISIX is a mature, open-source API Gateway with:

• Dynamic routing & upstream management
• Rate limiting (request / count / connection based)
• Authentication plugins (JWT, KeyAuth, OIDC)
• Traffic control, retries, circuit breaking
• Observability integrations (Prometheus, logging plugins)
• etcd-based dynamic configuration (no restarts needed)

It fits perfectly into Coolify’s philosophy of self-hosted, production-ready infrastructure components.

Proposed Template Scope

A built-in Apache APISIX Resource could include:

• etcd (required by APISIX)
• apisix gateway service
• (Optional) apisix-dashboard for UI-based management

This resource would:

• Be deployed via Docker Compose (similar to other resources)
• Work behind Coolify’s existing proxy (Traefik)
• Expose a single internal gateway entry point for backend services

Use Cases in Coolify

• Central API entry point for multiple backend services
• Path-based routing (/auth/*, /payments/*, etc.)
• Rate limiting per API or consumer
• Centralized authentication (e.g. OIDC with Authentik)
• Cleaner service boundaries instead of exposing each API directly

Why this matters

Many Coolify users run multiple APIs or microservices.
Right now, they either:

• Expose services directly, or
• Manually deploy and wire an API gateway

A first-class APISIX resource would significantly improve:

• Security
• Traffic control
• API lifecycle management

If this sounds reasonable, I’d be happy to help test or validate the template on a real self-hosted setup.

Thanks again for Coolify 🚀