CNAME Command: Easier DNS Management

As micro-saas solutions boom, and vibe coding gives us yet more solutions to keep track of, and we host open source tech in the cloud - we need a way to both catalog these pieces of tech, and make them easily accessible. Between logging into Cloudflare, remembering what points where, and dealing with multi-record setups for things like Firebase, AWS, Railway, or that docker container running... Somewhere... well, it's become a time-sink.

CNAME Command simplifies all of that. It's a tool I built to automate CNAME management for buildmri.com, with built-in integration to the Cloudflare API and a product-first way of thinking about DNS.

How it works

Instead of managing records one-by-one, you group them under something called a Product—think apps, microsites, tools, or integrations. Each Product can have one or more CNAMEs associated with it.

Key Features

Product-based structure: Organize records by app or service. products have a name, a description, and tags to both describe and filter by
Secure login: Sign in with your work email using a magic link or password.
Cloudflare API integration: Add/update/delete CNAMEs directly in Cloudflare without ever logging in there.
Multi-record support: Add multiple CNAMEs to a product for setups that require more than one (like Firebase hosting).
Role-aware access: Everyone can see everything; users can edit or delete only their own products. Admins can add / edit / delete anything.

How to use it

Go to the CNAME Command portal.
Sign in with your work email.
Create a Product (e.g. Weekly Reports App).
Add one or more CNAMEs: specify the subdomain (e.g. ppp) and the target (e.g. studio--weekly-ppp.vercel.app).
Save. We handle the rest via Cloudflare.

Under the hood

Next.js for the frontend
Firebase Auth + Firestore for secure logins and data
Cloudflare API to manage DNS records
Tailwind CSS + ShadCN UI for a clean, responsive UI
TypeScript throughout

Why I built it