A robust gateway for your APIs
Centralize authentication, rate-limiting, routing, and observability for all your APIs behind Kong, installed and maintained by DINAO. A single, fast, and secure entry point — hosted in France.
What is Kong?
Kong is an open-source API Gateway (API Gateway), renowned for its performance and low latency. Built on Nginx and OpenResty, it sits upstream of your services to centrally manage routing, load balancing, authentication, traffic control (rate-limiting, quotas, cache), and observability.
Its extensible architecture relies on a rich ecosystem of plugins : API keys, JWT, OAuth2, OpenID Connect, mTLS, ACL, request transformations, CORS, logging, Prometheus metrics, distributed tracing… You can even write your own plugins in Lua. Kong runs with a PostgreSQL database or in DB-less mode driven by a declarative file, which integrates naturally into a GitOps approach.
Designed for microservices architectures, Kong runs in containers, scales horizontally, and integrates with Kubernetes as an Ingress Controller. It thus becomes the single, measurable, and secure entry point for your entire API portfolio.
Host Kong at DINAO
Resource tiers compatible with Kong prerequisites (minimum 1 cœur / 2 Go / 5 Go). Hosted in France, fully managed.
- 1 dedicated vCPU
- 2 Go RAM
- 20 GB NVMe
- Daily backups
- Managed & monitored by DINAO
- 2 dedicated vCPU
- 4 Go RAM
- 40 GB NVMe
- Daily backups
- Managed & monitored by DINAO
- 4 dedicated vCPU
- 8 Go RAM
- 80 GB NVMe
- Daily backups
- Managed & monitored by DINAO
- 8 dedicated vCPU
- 16 Go RAM
- 160 GB NVMe
- Daily backups
- Managed & monitored by DINAO
Technical details
You might be wondering…
What is an API Gateway?
It is a single entry point placed in front of your services. Kong applies authentication, traffic control, routing, and measurement there, avoiding the need to reimplement these functions in each microservice.
Do I need to modify my existing APIs?
No. Kong sits upstream of your services. You declare your routes and enable plugins; your application code remains unchanged.
Which authentication methods are supported?
API keys, JWT, OAuth2, OpenID Connect (OIDC), Basic Auth, mTLS, ACL… You combine plugins according to your security needs.
Where is the data hosted?
On DINAO infrastructure in France, in one of the available datacenters. The gateway, its configuration, and its logs never leave the territory.
Can I switch to high availability later?
Yes. You can scale up at any time to a redundant multi-node configuration, without proprietary lock-in.