# One ODK Central Instance, many domains / per project domain

**URL:** <https://forum.getodk.org/t/one-odk-central-instance-many-domains-per-project-domain/57380>\
**Category:** Support\
**Tags:** odk-central\
**Created:** [January 5, 2026, 8:28am UTC](https://forum.getodk.org/t/one-odk-central-instance-many-domains-per-project-domain/57380 "2026-01-05T08:28:29Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![jniles](https://getodk.b-cdn.net/user_avatar/forum.getodk.org/jniles/32/2819_2.png) [@jniles](https://forum.getodk.org/u/jniles)\
**Post date:** [January 6, 2026, 4:38pm UTC](https://forum.getodk.org/t/one-odk-central-instance-many-domains-per-project-domain/57380/4 "2026-01-06T16:38:18Z")

</div>

An interesting use case!

I wonder if the [recent proposal to ship ODK without nginx would help meet this use case](https://forum.getodk.org/t/odk-central-deployment-without-nginx-for-deployment-in-multi-app-and-kubernetes-environments/57156). I agree having the option to make ODK Central more oblivious to its domain name would reduce the complexity for those of us that want to tinker with it and/or push it to the edge of its design specs.

---

_[View the full topic](https://forum.getodk.org/t/one-odk-central-instance-many-domains-per-project-domain/57380)._