ZuploZuplo
LoginSign Up
  • Documentation
  • API Reference
Introduction
Getting Started
    Develop using the Portal
      1 - Setup Your Gateway2 - Rate Limiting3 - API Key Auth4 - Deploy5 - Dynamic Rate LimitingMCP - Quick start
    Develop Locally
      1 - Setup Your Gateway2 - Rate Limiting3 - API Key Auth
Concepts
Development
Policies
Handlers
API Keys
MCP Server
MCP Gateway
AI Gateway
Developer Portal
Monetization
Deploying & Source Control
Observability
Networking & Infrastructure
    Overview
    Managed Dedicated
      OverviewSource ControlArchitectureNetworkingAWS Private NetworkingAzure Private NetworkingGCP Private NetworkingCustom DomainsFederated GatewaysArchitectureAkamai CDNCDN CachingAI-Powered Applications
    Managed EdgeSelf Hosted
    Custom Domains
    Securing Your Backend
    Web Application Firewalls
    DDoS Protection
Account Management
Programming API
Build with AI
Zuplo CLI
Migration Guides
Platform LimitsSecuritySupportTrust & ComplianceChangelog
powered by Zudoku
Managed Dedicated

Managed Dedicated: Custom Domains

Configuration of custom domains with your managed dedicated instance of Zuplo varies depending on how your instance networking is configured. For customers using their Zuplo API Gateway as the ingress the bulk of the configuration is managed by Zuplo. You will be provided an IP address or CNAME to point your DNS to. Normally, Zuplo manages the SSL certificates in this type of configuration as well.

Custom configurations are supported with Zuplo Managed Dedicated instances. For example, you can use your own SSL certificates, or if you are using your own VPC as the ingress, you can even use your own IP addresses.

For the full details on how to configure custom domains with your managed dedicated instance of Zuplo, please contact your account manager.

Preview environments

By default, preview environments are deployed to a wildcard subdomain managed by Zuplo. For example, if your account name is acme, the preview environment URLs are hosted at *.acme.zuplo.work, so each environment will have a URL like https://my-environment-123.acme.zuplo.work.

Some customer want to use their own domain for preview environments. For example, *.dev.acme.com. This is supported with Zuplo Managed Dedicated instances. Depending on your cloud provider, this may require you to create a wildcard certificate for your domain.

Edit this page
Last modified on November 17, 2025
GCP Private NetworkingFederated Gateways
On this page
  • Preview environments