# Use One Premium Route Layer For Imported Starter

The merged Premium runtime should expose one public Kong/api-gateway entrypoint. Starter/Essential v1 imports add Starter-specific routes to the Premium route layer rather than running a second Starter-only gateway or host inside the same session.

The merged route layer still keeps Starter route ownership explicit. Starter management routes such as `/v1beta1/clusters`, `/v1beta1/regions`, and `/v1beta1/shadowPools` route to `tidb-mgmt-portal`, while higher-priority Starter serverless public subroutes such as `/v1beta1/clusters/{clusterId}/branches...` route to `serverless-svc-http`. Kong Ingress manifests may use the `/~` regex marker internally, but probes and user traffic use the public `/v1beta1/...` path. Premium and Dedicated routes remain in the same public entrypoint contract.