About Duggie CMS

A modern headless CMS built by a developer, for developers and their clients.

Why Duggie exists

I'm Dave Dugas, a software engineer in Round Rock, Texas. Duggie CMS is a product of Duggie Labs, LLC, and I'm its founder and its only developer.

Duggie started with a familiar freelance problem. Every finished client site turned into a slow drip of "can you change one sentence" emails. The options were a WordPress admin with enough power for a client to break the site, or a headless platform with content modeling, SDKs, and pricing built for a team of fifty. Nothing in between was built for a developer shipping small sites and handing them off.

So I built the in-between: a content backend simple enough to wire up in minutes, safe enough to hand to a client, and structured so ownership can sit with whoever pays the bill.

Duggie runs on Duggie. Every line of copy on this website, this page included, is written in Duggie and published from its API, and the photo below is served from its CDN. I'm its heaviest user.

Meet the Founder

Dave Dugas

Dave Dugas

Founder & Developer

I build web applications for a living and have shipped a lot of small client sites along the way. Duggie is the tool I wished I had for every one of them: something I could wire up in an afternoon and hand to the client without a training session.

Built With Modern Tech

Every piece named, so you can judge the choices yourself.

Angular

Component-based frontend, prerendered for the public pages.

Tailwind CSS

Utility-first styling for a consistent, responsive UI.

.NET

The API, written in C# on ASP.NET Core.

MongoDB

Document database for content, versions, and audit logs.

Cloudflare R2

Object storage for uploaded images and documents, and for nightly database backups.

Railway

Hosts the API.

Cloudflare

Serves this website from the edge, with DDoS protection, bot checks, and page view analytics.

What happens to your content if I stop

A fair thing to ask of a service run by one person. If Duggie ever shuts down, every account owner gets at least 90 days' notice, written into the Terms, and everything keeps working for the whole of that period. Your content is retrievable as JSON from the same public API that serves your site, today, with the key you already hold, and a project can be handed to the client who owns the site so it never depends on you or on me.

What happens to your content in every scenario, including if Duggie shuts down

Ready to get started?

Build once, hand off, stay hands-off