Forem: DeBros

We Build our own decentralized DNS for AnChat — Here’s Why

DeBros — Wed, 11 Mar 2026 05:47:24 +0000

Most “decentralized” projects still trust Cloudflare to resolve their domains. We did too — until we realized that defeats the entire point.

This is the story of how DeBros moved away from Cloudflare and built a fully self-hosted DNS system into the Orama Network — and how AnChat’s backend infrastructure already runs on it.

The Problem With Cloudflare

Cloudflare is great. It’s fast, reliable, and free for most use cases. But it’s also a single company sitting between your users and your infrastructure.

When you put your domain behind Cloudflare, you’re trusting them to:

Resolve your domain correctly
Not censor your content
Not go down (they have — multiple times)
Not comply with a takedown request that kills your project overnight

For a privacy-first messaging app, this is a non-starter. If one company can flip a switch and make your app unreachable, you’re not decentralized. You’re just using a different centralized provider.

We needed DNS that works like the rest of Orama Network: distributed, self-healing, and under nobody’s control but ours.

What We Built

Every Orama Network node can run as an authoritative nameserver. When you install a node with the — nameserver flag, it spins up CoreDNS — the same DNS server that powers Kubernetes clusters worldwide — backed by our distributed SQL database (RQLite).

Here’s the architecture:

CoreDNS handles the DNS protocol — receiving queries, responding with records, caching responses.

RQLite stores all DNS records in a distributed SQL database replicated across every node via Raft consensus. When you add a DNS record on one node, every other node sees it within seconds.

Self-healing heartbeats ensure the system stays accurate. Every 30 seconds, each node:

Confirms its own DNS records exist (and recreates them if they don’t)
Checks if other nodes are still alive
Removes DNS records for dead nodes automatically

No manual intervention. No stale records pointing to servers that went offline three weeks ago.

How It Actually Works

When AnChat’s backend needs to resolve its namespace — ns-anchat.debros-orama.network — here’s what happens:

The query hits our authoritative nameservers: ns1.debros-orama.network — ns2.debros-orama.network — ns3.debros-orama.network — three independent Orama Network nodes with glue records set at the registrar
CoreDNS on that node queries RQLite, finds the A record, and responds
If that node is down, the query automatically falls through to ns2 or ns3

Three nameservers on three independent VPS nodes. No single point of failure. No Cloudflare in the middle.

Wildcard DNS & Automatic SSL

The system supports wildcard DNS out of the box. Every node gets its own subdomain pattern — like *.node1.dbrs.space — so deployed apps automatically get DNS without anyone manually creating records.

SSL certificates are handled through ACME DNS-01 challenges. When Caddy (our HTTPS server) needs a certificate for a new subdomain, it writes a TXT record directly into CoreDNS via the gateway API, Let’s Encrypt verifies it, and the certificate is issued. No Cloudflare API tokens. No external DNS provider. The whole chain is internal.

The Self-Healing Part

This is where it gets interesting. Traditional DNS is static — someone sets records, and if they break, someone has to fix them.

Orama DNS is alive. Every node continuously ensures its own records are correct:

Node comes online? It registers itself in the dns_nodes table, creates its A records, and claims an NS slot (ns1, ns2, or ns3) if one is available.
Node goes offline? Other nodes detect the missing heartbeat after 2 minutes, mark it inactive, and remove its A records from the round-robin pool. Dead IPs never get served to users.
Database gets reset? The SOA and NS records are regenerated automatically on the next heartbeat cycle.
Bad records from old code? A cleanup routine scrubs private IPs (10.0.0.x, 192.168.x.x) on every heartbeat — leftovers from an earlier bug we fixed.

The DNS system heals itself the same way the rest of Orama Network does. No ops team babysitting it at 3am.

AnChat Already Runs On This

AnChat’s backend namespace — ns-anchat.debros-orama.network — is resolved entirely by our own nameservers. The gateway, the messaging infrastructure, the deployment routing — all served through DNS that we operate on Orama Network nodes.

The public-facing anchat.io domain still uses traditional DNS for now. But the actual infrastructure underneath — the part that routes your messages, handles authentication, and runs the decentralized backend — that’s already on our DNS. No Cloudflare in the chain.

When we say AnChat is decentralized, we mean the full stack:

Messaging: Decentralized — routed through independent Orama Network nodes, no central servers
Identity: Wallet-based, no email or phone
Metadata shielding: ANyONe Protocol onion routing
Infrastructure: Orama Network distributed nodes
DNS: Our own nameservers resolving the backend namespace

Most projects claiming decentralization still have a Cloudflare dependency hiding in their infrastructure. We’re removing ours — layer by layer.

Why This Matters

DNS is the most overlooked single point of failure in the decentralization stack. Your app can run on decentralized infrastructure, your data can be encrypted end-to-end, your code can be open source — but if Cloudflare resolves your domain, one compliance email can take you offline.

Running your own DNS isn’t easy. You need multiple nodes for redundancy, proper glue records at the registrar level, health monitoring, and automatic cleanup of stale records. We built all of that into Orama Network so that any project running on our infrastructure gets sovereign DNS by default.

No middlemen. No kill switches. No asking permission to exist on the internet.

That’s what infrastructure sovereignty actually looks like.

DeBros builds privacy-first infrastructure. AnChat is our first app — decentralized messaging with zero metadata collection. Try the beta at anchat.io

DeBros NFT’s — Decentralized Development

DeBros — Tue, 14 Oct 2025 13:43:24 +0000

DeBros is more than a team; it is a decentralized brotherhood united by a shared vision, to build a more secure and liberated internet through our network and strategic partnerships.

Non-Fungible Tokens (NFTs) represent a significant milestone in our infrastructure and roadmap, paving the way for a more connected and decentralized future. Holders of DeBros NFTs will gain exclusive privileges and tangible utility, far beyond mere hype or a simple digital image.

We are thrilled to announce the official launch of our two NFT collections: DeBros 700 and DeBros Team 100. Each collection offers remarkable real-world utilities, which we will explore in detail below.

“A dark, dystopian world is approaching fast — while we’re asleep. Our generation risks going down in history as the last one that had freedoms — and allowed them to be taken away. We’ve been fed a lie.
— Pavel Durov

“Ultimately, arguing that you don’t care about the right to privacy because you have nothing to hide is no different than saying you don’t care about free speech because you have nothing to say.”
— Edward Snowden

Our generation is inching closer to a dystopian future where freedom of speech and privacy are luxuries only a few can imagine. DeBros stands as a resolute resistance against the encroaching forces of globalists, unchecked AI, and overreaching governments.

The DeBros NFT collections is not merely a digital image stored in a Solana wallet; it is a unique key for generations to come, granting access to a wide array of DeBros projects and real-world assets.

DeBros NFT 700

Apps & Software

Holders of the DeBros 700 NFTs will enjoy unlimited access to current and future DeBros applications, including:

Payme.sol Pro: A secure, decentralized payment platform designed for seamless transactions.
Blaze: A private, encrypted email service tailored for our community.

Additionally, holders will gain early preview and beta access to upcoming applications, such as:

AnChat (CLI, Lite): A lightweight, privacy-focused communication tool.
DeViewer: An innovative platform for remote desktop viewing.

Voting DAO

As a DeBros 700 NFT holder, your voice matters. You will have one vote in our Decentralized Autonomous Organization (DAO), empowering you to influence major decisions regarding treasury management, development priorities, and strategic partnerships. This ensures that our community remains at the heart of DeBros’ growth and direction.

Airdrops

DeBros 700 NFT holders will be eligible for exclusive airdrops from partnerships and new projects. These airdrops may include digital assets, such as tokens, or real-world assets, such as hardware equipment, computers, and crypto hardware wallets. Looking ahead, we plan to distribute hardware nodes (currently under active R&D) to all 700 holders, further enhancing the utility and value of these NFTs.

DeBros Team NFT 100

The DeBros Team collection is an ultra-exclusive, limited-edition set of 100 NFTs crafted for our most dedicated supporters and contributors. This elite group will play a pivotal role in shaping the DeBros ecosystem, with unparalleled access and influence. The Team 100 NFTs come with the following unique benefits:

Exclusive Developer Access

Team 100 NFT holders will gain exclusive developer access to a collaborative and secure hub for application development under the DeBros umbrella and our R&D Center. This hub provides access to our proprietary toolkit, enabling holders to contribute directly to the creation of cutting-edge, privacy-focused applications. Whether you’re a developer or an innovator, this access empowers you to build alongside the DeBros team, shaping the future of our decentralized network.

Enhanced DAO Governance

As a core supporter, each Team 100 NFT holder will wield five votes in our DAO governance, ensuring significant influence over development-focused decisions, treasury management, and strategic partnerships. This elevated voting power reflects the critical role Team 100 members play in guiding DeBros’ mission and vision.

Passive Income Opportunities

Team 100 NFT holders will benefit from passive income generated through revenue-sharing from fees and services of existing DeBros applications on our network. This unique utility provides a tangible financial reward for supporting our mission, aligning your success with the growth of the DeBros ecosystem.

Access to Private Events and Real-World Hubs

Team 100 members will enjoy exclusive access to private, in-person events hosted by DeBros, fostering networking and collaboration among our most committed supporters. Additionally, holders will have access to our physical DeBros hubs worldwide, fully equipped with cutting-edge hardware and amenities. Our mission is to create a worldwide network of safe havens for individuals committed to advancing our vision of privacy and decentralization. These hubs serve as secure spaces for innovation, collaboration, and advancing our decentralized vision.

Our Vision

At DeBros, we are driven by a commitment to empower individuals and communities through decentralization. Our NFT collections are not just digital assets; they are a gateway to a movement that champions privacy, freedom, and innovation. By holding a DeBros NFT, you are not only investing in a secure and decentralized future but also becoming an integral part of our brotherhood.

You can join our mission by purchasing DeBros NFTs on leading marketplaces. Both DeBros NFT collections are available on Magic Eden and Tensor.

Join us in resisting centralized control and building a world where privacy and freedom are not just dreams but realities for generations to come.

Magic Eden:
https://magiceden.io/marketplace/debros
https://magiceden.io/marketplace/debros_team

Tensor:
https://www.tensor.trade/trade/debros
https://www.tensor.trade/trade/debros_team

Decentralized Development Ecosystem - DeBros Network

DeBros — Mon, 22 Sep 2025 07:12:52 +0000

As the official DeBros Development Team, we are thrilled to announce that we have open-sourced the DeBros Network, the first decentralized development ecosystem for developers.

You can find the first public version of the Network in our official GitHub repository: Github Repo

In this article, we will address the two most important questions about the Network:

What is the Network, and why should developers care?
The current state of the Network and how to contribute.

You can read the whitepaper for the Network here: Whitepaper

What is the Network

The DeBros Network is a decentralized ecosystem for developers that enables them to build applications with fewer bottlenecks, streamlined deployments, and simplified testing and development. It provides an extensive suite of tools, including:

Serverless functions - Under R&D
Network Buckets (Private IPFS Swarm for saving files) - Internal Testing
Network SQL (RQLite Based distributed database) - In Beta
Network Memory (Distributed in-memory cache storage) - Under R&D
Network DNS (ENS, SNS, yggdrasil) - Under R&D
Network AI (Distributed AI models hosted directly on the network and custom neural networks) - Under R&D
Network P2P (LibP2P implementation for internal network communications) - In Beta
Network KV (Distributed key-value storage) - Internal Testing
Network Agents (Network base distributed based on custom neural networks) - Under R&D
Network Analytics (E2E encrypted analytics implementation for debugging and maintenance) - Under R&D
Network Compute (Compute engine for running docker images) - Under R&D
Network Payments (Get paid anonymously via DeBros Network and recurring payments with ABT protocol) - Under R&D

WEB2 Challenges

Creating a fully featured application often requires extensive knowledge of various technologies and tools, such as finding a hosting provider for your database (e.g., PostgreSQL), event streaming platforms like Kafka, AI providers like OpenAI, or edge networks like Vercel. While these technologies may be manageable to develop locally, deployment presents significant challenges.

Developers typically face two options:

Host everything on your own VPS: This can be complex to set up and requires advanced server knowledge, especially for load balancing to ensure no downtime.
Use a cloud provider like AWS: This involves a complicated setup and can incur extremely high costs, even for simple applications (terraform).

Both options require you to independently set up a database, communication protocols, reverse proxy services, frontend, backend, storage buckets (for images and videos), and AI integrations. Moreover, your data and your customers’ data are not encrypted by default. Instead, they are stored and processed by third-party companies, leaving you vulnerable to risks like account bans, missed payments, or service shutdowns.

These companies sell the lie of extreme up time like five 9’s which is rarely the case because these numbers are hard to get because of the complexity of the architecture of these ecosystems.

Let’s consider a basic technology stack for a standard application using Web2 technologies:

MongoDB Atlas for deployment of your database
Vercel for deployment of your frontend
AWS Bucket for hosting images and videos
Stripe as a payment provider
Cloudflare for setting up your domain and DNS
OpenRouter as the AI Model provider

You have other options as well, deploying all of the above inside AWS or GCP but this risks centralization and higher costs. Even if you don’t care about privacy and decentralization setting up all of the above services can be frustrating and difficult, because you need 6 different accounts and API key’s.

For all of the WEB3 developers out there, we all know that creating a fully featured application with WEB3 and blockchain technologies is not even possible, like a social network for example. WEB3 Developers in cases like this use blockchain technologies like SUI or Ethereum as there databases but we will know doing 1 million transactions to just store 3 likes and 2 comments is not ideal nor easy to do.

Our Network approach is trying to solve this problem by making everything decentralized and encrypted by default without the developer even knowing about it. For you to understand if you put on a scale WEB3 Development, WEB2 Development and DeBros Network it will look like this:

Even in WEB3 development right now nothing is truly decentralized because we are doing workarounds and using different providers to fix our issues.

Let’s take a simple look at what DeBros Network is promising:

_You need to know that our network is still under active development some of the features you will see below are either unstable or unreleased, you can see the current state of our released features here: https://network.debros.io/docs/network/client-sdk/#database-api

Our Network Client SDK is Currently written in Go and we also have a Gateway HTTP Interface_

Initializing the Network

To get started, import the Network package and set up your API key. This grants you access to the DeBros Network and all of its services.

SQL Database

For SQL databases, we leverage a decentralized, open-source solution called Rqlite in the background. While the current table creation process can be somewhat repetitive, we are committed to simplifying it in future updates. You can help us achieve this by forking the project and contributing to its development.

NoSQL Database (unreleased)

The DeBros Network supports not only traditional SQL databases but also decentralized and encrypted NoSQL databases, providing developers with flexible and secure options.

Save in Cache Storage (unreleased)

Similar to traditional systems, our Network offers fast in-memory cache storage. As you’ll see, it’s designed to be simple and intuitive to use.

PubSub Events

Another powerful feature is our event system, built on PubSub and LibP2P. This allows you to publish or subscribe to events, enabling an event-driven architecture for your applications, including mobile apps.

We don’t want to overwhelm you with a long list of features, but rest assured, we plan to include nearly every tool you’d find in a traditional cloud provider—only simpler and more cost-effective. Upcoming features include AI, bucket storage (for files), AI agents, analytics, payments, serverless functions, and compute resources.

The current state of the Network and how to contribute.

The DeBros Network is currently under active development and not yet in a stable release. We aim to reach a stable version by the end of 2026. As we’re in the early stages, you may encounter bugs and errors. Below is the current architecture of the Network:

Contributing is straightforward: fork the repository, work on your changes in a separate branch, and submit a pull request. We encourage you to engage in discussions, ask questions, and share feedback on GitHub or in our Telegram group.

Start here by reading the developer documentation:
https://network.debros.io/docs/network/overview/

Explore our official links: https://linktr.ee/debrosofficial

Thanks for reading,
The DeBros Team