Custom domains for Neon Functions

Neon Functions, now generally available, supports custom domains that let developers replace default Neon invocation URLs with branded hostnames for APIs, webhooks, MCP servers, real-time services, and multi-tenant applications. Domains can be registered through the Neon Console, CLI, SDK, API, or configuration files, after which users add a returned CNAME record to their DNS provider; Neon then activates routing and automatically provisions TLS certificates through Let’s Encrypt at no separate domain charge. Each hostname is tied to a specific Function and branch, so preview deployments require separate subdomains rather than inheriting a production domain. The feature is particularly intended for MCP servers, allowing them to run directly alongside Lakebase Postgres with injected database credentials, while avoiding external reverse proxies and providing stable URLs suitable for customer-facing documentation, plugin manifests, and marketplace listings.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.