ComparisonsVercelCustom domains, SSL and apex

How do custom domains, apex records and SSL compare on Vercel and Naijacloud?

This is one of the closer comparisons on the site: both platforms attach a custom domain, support the apex — the bare example.com, not just www — and issue and renew certificates automatically, and both will sell you the domain in the first place. The differences are narrower and worth knowing. Vercel terminates TLS on its own global network in front of 126 points of presence, which is excellent for a worldwide audience. Naijacloud terminates at the region your service runs in, so a Nigerian app is served in-country, prices the domain in Naira on the same prepaid balance as everything else, and publishes a new custom-domain route without redeploying the service. If your audience is global, Vercel’s edge is the better answer; if it is Nigerian, ours is.

Apex support is worth explaining because it is where most platforms quietly fail. DNS does not allow a CNAME at the root of a zone, so a platform that only offers CNAME targets cannot serve example.com without either running your DNS itself or relying on a provider-specific ALIAS or CNAME-flattening record. Both Vercel and Naijacloud handle the apex properly, which is not something to take for granted.

On our side it took real work in the Nigerian region specifically, because af-west ingress arrives through a tunnel rather than a plain public address — apex domains there are served by pointing an A record at the edge and routing on SNI. The reason to mention an implementation detail on a comparison page is that it is the difference between "apex works" and "apex works everywhere we run".

Certificate issuance and renewal are automatic on both. On ours, attaching a domain publishes the route live rather than waiting for the next deploy, so a domain added at 2pm serves at 2pm.

Where Vercel is ahead: the certificate terminates at whichever of its points of presence is closest to the visitor, so the TLS handshake is short everywhere in the world. We terminate in-region, which is the right answer for a Nigerian audience and the wrong one for an audience in Sydney.

Where we are ahead, beyond the region: the domain, the DNS zone, the certificate, the app, its database and its bucket are one account, one bill and one support queue, in Naira. And registration priced in Naira on a prepaid balance avoids the annual renewal that fails because a dollar card was declined.

Platform comparison

Scored out of five on what actually changes your day.

What you need
Naijacloud
Vercel

Apex (root) domain support

Naijacloud

5/5

Supported in every region, including af-west where ingress arrives through a tunnel and the apex is served by routing on SNI.

Vercel

5/5

Supported, with an A record to Vercel’s edge and automatic certificates.

Automatic HTTPS issuance and renewal

Naijacloud

5/5

Issued and renewed automatically for every attached domain, apex included.

Vercel

5/5

Issued and renewed automatically, at a very large scale, for a very long time.

Where TLS terminates

Naijacloud

4/5

At the region serving the service — in-country for af-west, which is the shortest handshake a Nigerian visitor can get.

Vercel

5/5

At the nearest of 126 points of presence, so the handshake is short from almost anywhere on earth.

Registering the domain itself

Naijacloud

5/5

Search, register and renew in Naira from the same prepaid balance as the hosting, with the zone hosted here.

Vercel

4/5

Vercel sells domains and hosts DNS, in dollars, on a card.

Time for a new domain to go live

Naijacloud

5/5

The route publishes immediately — no redeploy — so a domain attached now serves now, once DNS resolves.

Vercel

5/5

Immediate once DNS resolves and the certificate issues.

DNS hosting

Naijacloud

4/5

Authoritative DNS for domains registered here, managed in the same dashboard.

Vercel

5/5

DNS hosting with a mature API and CLI, plus support for domains kept at another registrar.

Frequently asked

Yes, on both platforms, in every region we run. That is worth checking on any host — DNS forbids a CNAME at the zone root, so a platform that only hands out CNAME targets either has to run your DNS or lean on a provider-specific ALIAS record.

Try it against your own workload

Deploy one service from a Git repo in Port Harcourt and compare the numbers yourself. Free tier, no card, no FX.