Docs
Route your own hostname to any Fieldwick service. DNS verification, certificate provisioning, and renewal are handled for you.
Run fieldwick domains attach with your service name and the hostname you want to use. The platform registers the intent and returns the DNS records you need to set.
fieldwick domains attach <service> app.example.comYou can also attach a domain from the dashboard: open the service, go to the Domains tab, and type the hostname into the attach field. The same DNS instructions are shown inline.
At your DNS provider, create a CNAME record pointing your hostname at apps.fieldwick.com. For example:
app.example.com. CNAME apps.fieldwick.com.For ownership verification, also add the TXT record shown in the attach output or on the dashboard Domains tab. The record looks like:
_fieldwick.app.example.com. TXT "fieldwick-verify=<token>"DNS changes can take a few minutes to a few hours to propagate depending on your provider and existing TTL values.
Once your DNS records are live, trigger verification. Fieldwick checks the TXT record to confirm you control the hostname, then moves the domain into the provisioning state where certificate issuance begins.
fieldwick domains verify <service> app.example.comVerification is also triggered automatically on a short polling interval, so you can skip this step and the domain will advance on its own once DNS propagates.
Every custom domain moves through three states. Use fieldwick domains list to see the current state for all domains on a service.
fieldwick domains list <service>The three states:
pending - domain attached, DNS not yet verified. Traffic is not routed.provisioning - ownership confirmed. A Let's Encrypt certificate is being issued via on-demand TLS. The CNAME must already point at apps.fieldwick.com for this step to complete.active - certificate issued. HTTPS traffic is live and renewals are automatic.Detaching a domain is a hard delete. The hostname is removed from the service, the certificate is revoked, and traffic stops routing immediately. You can re-attach the same hostname later, but verification and certificate provisioning restart from the beginning.
fieldwick domains detach <service> app.example.comRemove the DNS records at your provider after detaching to avoid dangling CNAME entries.
503 on the custom hostname or TLS stuck in provisioning. Almost always means the CNAME is not pointed at apps.fieldwick.com yet, or the change has not propagated to all resolvers. Check the CNAME with:
dig CNAME app.example.com +short
# expected: apps.fieldwick.com.Once the CNAME resolves correctly, re-run verify to advance the domain:
fieldwick domains verify <service> app.example.comIf the domain remains stuck in pending after the CNAME is correct, confirm the TXT ownership record is also present. Both records must exist for provisioning to start.