Skip to main content
Point your own domain at a pod without leaving the terminal. Alias: domain. A domain goes live in two steps: add it and create the DNS record it prints, then verify it. Verification issues the SSL certificate and starts routing the domain to the pod.

List Domains

instapods domains my-app does the same. Shows each domain with its status, SSL status, and verification method. A domain serves the pod only once its status is active.

Add a Domain

Prints the DNS record to create:
With --method txt, the command prints two records: a TXT at _instapods.<domain> holding a verification token, and the CNAME that points the domain at the pod. Create both. The TXT record only proves ownership, and the SSL certificate cannot be issued until the domain itself resolves to the pod.

Verify a Domain

Alias: check. Checks the DNS record. When it is correct, an SSL certificate is issued via Let’s Encrypt and the domain starts serving the pod:
If the record is not visible yet, the command prints the record again and exits non-zero. DNS changes usually propagate within a few minutes; run verify again once the record is live. If DNS is correct but the certificate could not be issued, the command prints the reason and exits non-zero. Fix the cause, then run verify again. Running verify on a domain that is already live changes nothing and exits 0.
verify exits 0 only when the domain ends up active, so a script or an AI agent can rely on the exit code.

Remove a Domain

Aliases: rm, delete. The domain stops serving the pod immediately. Your pod’s default *.instapods.app address is not affected. In a script, in CI, or with --json there is nobody to answer the prompt, so remove requires -f and fails without it.

JSON Output

Every subcommand accepts --json:

Limits

  • Maximum 5 custom domains per pod
  • A domain can be attached to only one pod at a time
  • Worker pods have no public URL, so they cannot take a custom domain
See Custom Domains for how verification and SSL work.