Custom domains
Your own domain, serving your card at its root.
Once a domain is attached to your Kard, typing yourdomain.com opens your card — no eKard path in the address. The sharing surfaces switch over with it: the "Share link" box, the share buttons, the one-tap quick links, even the address printed on the card itself all start handing out your domain instead of the ekard.app link.
What moves and what stays
Setting a domain is additive, not a move. Your ekard.app link keeps working alongside it, so links you have already shared and QRs you have already printed stay live. Two details worth knowing:
- Your card's QR starts encoding the domain only when it next regenerates — it is not re-drawn the moment the domain is set. The course on your QR code covers what triggers that.
- Document links and QRs stay on
ekard.app, so they outlive the domain.
The one-tap links ride along too: yourdomain.com/whatsapp opens a WhatsApp chat with you, and yourdomain.com/location opens your Maps listing. Everything else on the card — the save button, the exchange, documents — works from the domain exactly as it does from the ekard.app address.
How to get one
Organizations can do the same for a whole team: the company domain serves the team's main card at its root and each member's card beneath it — see the course on organizations.
There is no self-serve setup today. A domain is arranged with the eKard team — write to hello@ekard.app with the domain you own and the card it is for.