For most developers, buying a domain is treated as a normal part of building something online.
But for students, beginners, open-source contributors, and indie developers, domains are often one more barrier between an idea and actually shipping it.
A few days ago, while looking for a clean way to host my portfolio without purchasing another domain, I came across a project called DigitalPlat FreeDomain.
At first, I assumed it was another temporary subdomain generator.
It wasn’t.
What I found instead was one of the most interesting independent infrastructure projects I’ve seen in a long time — a free domain platform started by a developer who began building DNS systems at 15 years old.
Today, the platform serves hundreds of thousands of users worldwide.
And surprisingly, the system is solid enough to integrate with modern infrastructure stacks like Cloudflare and Vercel.
This article is about:
- what DigitalPlat FreeDomain is,
- why the project matters,
- the story behind the platform,
- and how I connected my own free domain to Vercel using Cloudflare.
My portfolio is now running on:
https://adithyang.qzz.io
What Is DigitalPlat FreeDomain?
DigitalPlat FreeDomain is a platform that allows anyone to register free domains under namespaces like:
.qzz.io
.us.kg
.qd.je
.dpdns.org
Official dashboard:
https://dash.domain.digitalplat.org/
The idea behind the platform is straightforward:
Give people access to a digital identity without forcing them to pay for a traditional domain first.
The platform supports external DNS providers like:
- Cloudflare,
- FreeDNS,
- Hostry,
- and custom hosting setups.
That means developers can use these domains for:
- portfolios,
- side projects,
- SaaS prototypes,
- hackathon demos,
- landing pages,
- testing environments,
- and public deployments.
Unlike many “free domain” services, the system feels surprisingly developer-focused.
The Story Behind the Platform
The most interesting part of the project is the story behind it.
DigitalPlat FreeDomain was created by Edward Hsing, who started experimenting with DNS infrastructure when he was just 15 years old.
What began as a simple experiment — letting friends use subdomains under his own domain — slowly evolved into something much larger.
According to Edward’s own write-up, there was:
- no startup,
- no funding,
- no launch campaign,
- and no formal business plan.
Just experimentation.
As more people started asking for subdomains, the project eventually became infrastructure that developers actually relied on.
He built the backend himself using:
- Python,
- Flask,
- BIND9,
- and direct DNS integration.
Over time, the platform scaled from a small personal experiment into a system serving over 400,000 users globally.
That growth happened almost entirely through developers sharing it with other developers.
In an internet dominated by heavily funded platforms, there is something genuinely refreshing about an infrastructure project that grew organically because people found it useful.
Why This Project Matters
A domain is more than just a URL.
For developers, it is identity.
It is where:
- portfolios live,
- products launch,
- experiments become startups,
- and ideas become visible.
But domains still create friction:
- recurring costs,
- DNS complexity,
- SSL setup,
- hosting integration,
- and infrastructure overhead.
For experienced engineers, these are manageable problems.
For newer developers, they are often enough to stop projects from ever being published.
Projects like DigitalPlat reduce that friction dramatically.
Combined with platforms like Cloudflare and Vercel, it becomes possible to deploy a fully production-ready website with:
- HTTPS,
- CDN support,
- custom domains,
- and global hosting
without spending anything.
That changes accessibility in a meaningful way.
My Setup
I decided to test the platform by deploying my own portfolio using the following stack:
DigitalPlat → Cloudflare → Vercel
The process ended up being cleaner than I expected.
Initially, I attempted to connect the domain directly to Vercel DNS.
However, DigitalPlat currently exposes nameserver delegation rather than complete DNS zone management.
Because of that, Cloudflare becomes the ideal intermediary layer.
The final architecture looked like this:
DigitalPlat
↓
Cloudflare DNS
↓
Vercel Hosting
Once configured correctly, Vercel handled:
- SSL certificates,
- deployment,
- edge hosting,
- and HTTPS automatically.
Connecting the Domain to Vercel
The process was relatively straightforward.
First, I added the domain to Cloudflare and updated the nameservers inside the DigitalPlat dashboard.
Once Cloudflare became the DNS provider, I added the DNS records required by Vercel.
The critical records were:
A Record
| Type | Name | Value |
|---|---|---|
| A | @ | xxx.xxx.xx.x |
Proxy mode:
DNS only
And a TXT verification record provided by Vercel.
After propagation completed, Vercel automatically:
- verified ownership,
- issued SSL certificates,
- and connected the deployment.
The entire workflow felt remarkably modern for a completely free setup.
The Part Most People Don’t Think About
Running free infrastructure at scale is not easy.
One of the more interesting parts of Edward Hsing’s story is that he openly talks about the operational side:
- abuse handling,
- phishing prevention,
- automated moderation,
- and verification systems.
That is the part most people never see.
Building software is difficult.
Maintaining public infrastructure used by hundreds of thousands of people is significantly harder.
The fact that the project continues operating at this scale makes it far more impressive than a typical side project.
What I Took Away From This
What stood out to me most was not the free domains themselves.
It was the philosophy behind the project.
The idea that access to a digital identity should not depend entirely on money is surprisingly important.
The modern web is increasingly centralized around platforms and ecosystems that prioritize scale and monetization.
Projects like DigitalPlat feel closer to the earlier spirit of the internet:
- experimentation,
- accessibility,
- openness,
- and individual ownership.
That alone makes the project worth paying attention to.
Final Thoughts
Most developer tools today focus on optimization, automation, or AI.
Very few focus on accessibility at the infrastructure level.
DigitalPlat FreeDomain does.
And despite being built independently, it already powers infrastructure for hundreds of thousands of users.
That is genuinely impressive.
If you are:
- building a portfolio,
- launching side projects,
- experimenting with deployments,
- or simply learning modern infrastructure,
it is absolutely worth exploring.
Resources
DigitalPlat FreeDomain
https://dash.domain.digitalplat.org/
GitHub Repository
https://github.com/DigitalPlatDev/FreeDomain
Edward Hsing’s Story
https://dev.to/edwardhsing/i-bought-a-domain-at-15-now-it-powers-400000-users-7ol
Cloudflare
https://cloudflare.com/
Vercel
https://vercel.com/
Portfolio
https://adithyang.qzz.io
