Free domain for open source projects
Last updated: September 27, 2026
If you are looking for a free domain for your open source project, you probably mean what most people mean by that: a serious address for the project, without an annual bill. OpenRepos provides exactly that — a free, permanent address on a domain that reads like a project home.
Two very different things called "free domain"
- A registrable domain you own — bought from a registrar, renewed every year, with full DNS control: MX for email, NS delegation, transfers.
- A free address under an existing domain — a subdomain like
your-project.openrepos.org, created with one DNS record and no fees.
OpenRepos is the second kind, on purpose: it keeps the service free forever, keeps records DNS-only, and keeps the abuse surface small.
Why a subdomain is usually enough for a project
- Stable and memorable — a clean address you can put in a README, docs, slides or a release note, instead of
user.github.io/project. - HTTPS included — the record is DNS-only, and your hosting provider issues the certificate for the custom domain (GitHub Pages calls it Enforce HTTPS; Cloudflare Pages does it automatically).
- Portable — it is one CNAME. Change hosts and the address stays the same.
- No renewal, no expiry — there is nothing to pay and nothing to renew; working names are not recycled.
What OpenRepos gives you
- 7 domains to choose from —
.org,.ioand.sh-class TLDs that suit an open source project, for any language or ecosystem. - A claim flow that runs through a public file and CI: edit
register.json, add the badge to your README, open a pull request, and DNS is created after merge. - Approved hosting providers only (GitHub Pages, Cloudflare Pages, Vercel, Netlify, GitLab Pages and more), plus an optional verification TXT record when a provider requires one.
- Free forever, MIT-licensed claim engine, and a documented abuse and removal policy.
When you should buy a domain instead
Be honest with yourself about the one thing a subdomain cannot do: it is not yours. Choose a registrar when you need:
- email at your own domain (MX records, SPF/DKIM/DMARC control);
- nameserver delegation (NS) or wildcard DNS beyond our policy;
- full ownership: transfer, resale, or a brand you will keep for years;
- an apex domain (example.com rather than project.example.com).
For everything else — a project page, docs, a demo — a free subdomain on a serious domain does the job, and you can move to your own domain later without touching your site.
How to claim yours
- Pick a name with the domain picker on openrepos.org.
- Edit register.json and add the OpenRepos badge to your README.
- Open a pull request; after a maintainer merges, DNS is provisioned automatically. Follow a setup guide for your host.
Frequently asked questions
Is OpenRepos a domain registrar?
No. OpenRepos hands out subdomains on domains it operates: you get a permanent address like your-project.openrepos.org, not a registrable domain you own.
Do I own the subdomain?
You control the DNS record while your claim is active, but the domain itself stays with OpenRepos. That is what keeps the service free: no renewals, no transfer fees, no expiry.
Can I move to my own domain later?
Yes. Your site does not change — you point your own domain at the same host and drop the CNAME. Nothing about the hosting setup is tied to the subdomain.
Why is a subdomain enough for most projects?
A project site needs a stable, memorable address and working HTTPS. A subdomain on a .org/.io/.sh-class domain gives you both, and your host (GitHub Pages, Cloudflare Pages, Vercel, Netlify, GitLab Pages) issues the certificate automatically.
When should I buy a domain instead?
When you need email at your own domain (MX records), nameserver delegation (NS), full ownership and transfer rights, or a brand you want to control for years. For a project landing page or documentation, a subdomain is usually the practical free option.
Related
New to the idea? Read what a free subdomain is, or compare free subdomain services. Claims happen in the register repository.