cloud.hiyve.io is a neutral public name in front of the MULTI-TENANT
hiyve-cloud. Tenancy is resolved per CREDENTIAL (api key -> brand org) on
every request, so each consumer keeps its own store behind its own key —
the hostname is not a tenant boundary.
Both previous names were dead (verified 2026-08-24): api.muziemedia.com
was deleted from its zone when the dev stack was decommissioned, and
api.hiyve.dev had an ACM certificate on the legacy us-east-1 ALB but no
DNS record in any zone, so it never resolved. Anything relying on these
defaults could not connect at all.
BOTH entries resolve to the same host because there is exactly one
hiyve-cloud in the estate. development therefore does NOT mean "a
sandbox" — it reaches the same live store as production. Pass an
explicit baseUrl to target anything else; resolveEnvironmentUrl warns
once when the alias is used, because identical URLs are precisely what
makes that mistake invisible.
Environment-specific base URLs.
cloud.hiyve.iois a neutral public name in front of the MULTI-TENANT hiyve-cloud. Tenancy is resolved per CREDENTIAL (api key -> brand org) on every request, so each consumer keeps its own store behind its own key — the hostname is not a tenant boundary.Both previous names were dead (verified 2026-08-24):
api.muziemedia.comwas deleted from its zone when the dev stack was decommissioned, andapi.hiyve.devhad an ACM certificate on the legacy us-east-1 ALB but no DNS record in any zone, so it never resolved. Anything relying on these defaults could not connect at all.BOTH entries resolve to the same host because there is exactly one hiyve-cloud in the estate.
developmenttherefore does NOT mean "a sandbox" — it reaches the same live store asproduction. Pass an explicitbaseUrlto target anything else; resolveEnvironmentUrl warns once when the alias is used, because identical URLs are precisely what makes that mistake invisible.