Stackryze Domains is a free managed subdomain service that lets developers, students, and open-source projects claim a subdomain under shared public suffixes and point it at any hosting provider or their own infrastructure.

What it is

Stackryze Domains, published under the GitHub name FreeDomains, is a project from Stackryze that runs multiple base domain names and hands out free subdomains to anyone who wants one. It is written in JavaScript, licensed under AGPL-3.0, and lives in the developer tools space alongside DNS and hosting utilities. Four suffixes are currently available for claims: .indevs.in, .sryze.cc, .ryzedns.org, and .nx.kg, with the README stating that more extensions are coming soon.

The problem it addresses is the cost and complexity that stand between a developer, student, or open-source community and having a public hostname. In place of buying a domain, the service gives you a subdomain that you own and control outright, which you can point at any hosting provider or at your own machines. The project frames this as removing lock-in: you are not tied to Stackryze's hosting, because the only thing being supplied is the name and its DNS records.

Key capabilities

• Claim free subdomains under .indevs.in, .sryze.cc, .ryzedns.org, and .nx.kg, with more extensions announced as coming soon.
• Point the resulting name at any hosting provider or at your own infrastructure, with full ownership and complete control of where it resolves.
• Resolve through globally distributed name servers: ns1.stackryze.com (New York City, USA, primary), ns2.stackryze.com (Nuremberg, Germany, secondary), and ns3.stackryze.com (Hyderabad, India, secondary) for reliability and low latency.
• Manage claims through the hosted dashboard at https://domain.stackryze.com.
• Follow live service status and incident updates for all Stackryze services at https://status.stackryze.com.
• Report abuse directly to reportabuse@stackryze.com, with support handled at support@stackryze.com.
• Inspect the published infrastructure diagram (architecture.png) and raise feedback through the GitHub issues tracker and the project's Discord server.

Who uses it and how

• Developers who need a public hostname for a project and want to avoid paying for a domain registration.
• Students who are learning deployment and want a real address to point at their work.
• Open-source communities running projects that need a stable, community-visible name.
• Homelab operators who claim a subdomain and point it at their own infrastructure rather than a hosting provider.
• Users who monitor https://status.stackryze.com and the Discord community for service health and support.

Getting started

There is no package or container to install: you claim a name through the hosted dashboard at https://domain.stackryze.com, then set the records at your DNS or hosting provider to the Stackryze name servers.

How it compares

This registry lists no other project against which the facts support a comparison, so Stackryze Domains stands alone here.

When to use it — and when not

Because the DNS infrastructure is operated for you by Stackryze rather than by yourself, a self-hoster is not taking on databases, storage, or SMTP in exchange for the name — the trade-off instead is that the suffix, the dashboard, and the name servers belong to someone else, so your hostname depends on their continued operation of ns1.stackryze.com, ns2.stackryze.com, and ns3.stackryze.com. Anyone who needs a domain they register and control independently, or who requires a first-level domain rather than a subdomain, should not pick this. The README is also fairly sparse: it gives no install or contribution instructions beyond links to the dashboard, issues, and Discord, and anyone evaluating it should read the AGPL-3.0 licence and the published architecture before depending on the service.