Your own domain on your project in minutes, with HTTPS you never think about again.
Add a domain you already own and set the records we print, or hand us the nameservers and manage DNS from the same CLI. You can also search for and register a domain without leaving your terminal. Certificates are issued and renewed automatically; one address can be pinned to one release when a client must see exactly that version.
How it works
- 1
Add or buy
nesly domain addfor a domain you have;nesly domain searchandnesly domain buyto register a new one through the platform. - 2
Point it at us
Set the CNAME or A records the command prints, or use
nesly domain delegateand set our nameservers once; after that DNS lives here andnesly dns addchanges records. - 3
HTTPS, done
nesly domain verifyre-checks DNS and activates the domain; the certificate is issued and renewed for you. Your project's default address keeps working too.
What you get
Records or nameservers, your choice
Keep DNS where it is and set two records, or delegate the whole domain and manage it from the CLI alongside your deploys.
Certificates without a calendar
Issued at activation, renewed before expiry, no e-mail reminders to act on. Browsers trust it from the first request.
Pin an address to a release
nesly domain pin fixes one hostname to one deployment; unpin lets it follow the project again. Useful for sign-off and for a known-good version.
Buy from where you deploy
nesly domain search shows availability and the yearly price; nesly domain buy registers it, and domain add puts it on the project.
Status in plain words
nesly domain ls says exactly what is missing: waiting for DNS, which record, or ready.
Pricing
Custom domains are a Pro feature: 10 per project on Pro (TRY 869 a month with VAT in Turkey, $18 without VAT elsewhere), more with an add-on pack. Free projects use their platform address.
- Bringing a domain, DNS hosting and certificates carry no fee of their own.
- Registering a domain through the platform is charged at the yearly price the
searchcommand shows before you buy.
Use cases
Launching a client site
Add the client's domain, send them the one record to set (or our nameservers), verify, and the site is on their name with HTTPS.
A stable staging address
staging.example.com pointed at a preview alias, protected by sign-in, reviewed before every release.
A new product name
Search, buy and attach the domain in one terminal session; nothing to copy between a registrar and a DNS panel.
Questions, answered
- Can I keep my DNS at my current provider?
- Yes. Set the printed CNAME (or A record for a root domain) there; nothing else changes. Delegation is optional.
- How long until HTTPS works?
- As soon as the record is visible, which is usually minutes.
nesly domain verifyre-checks on demand and says what it still waits for. - Can I use a root domain, without www?
- Yes, with an A record to the address the command prints, or by delegating the domain to our nameservers.
- Does the platform address stop working when I add a domain?
- No. Your project's default address keeps serving; the custom domain is added next to it.
Related products
Applications
Push your code; it is live in minutes. Every change gets its own address, and one command puts the last release back.
Sign-in
Put a sign-in in front of your site in one command, or give your app its own OpenID Connect client. No auth code to write.
For AI agents
The CLI is also an MCP server. Claude, ChatGPT and Cursor deploy, read logs, add databases and fix failures for you.
Put your project on your domain
nesly domain add example.com prints the one record to set; verify does the rest.