Duggie CMS

Stop Being Your Client's
Content Editor

A lightweight headless CMS built for developers. Let clients update content safely. No rebuilds, no broken layouts, no support tickets.

No credit card required • One site free per account • Set up in minutes

app.duggiecms.com

A field and a Save button. Nothing is live until it's published.

How Duggie Works

From your first fetch call to a client managing their own content.

Create a Project

Set up a project for your website. Define which content can be edited.

Add One Fetch Call

Drop one fetch() into your site. Works with React, Vue, Angular, or any framework.

Hand It Off

Invite your client as an editor. They publish their own copy and the site picks it up on the next fetch. No redeploy, no ticket.

See it live

Here's Riverside Studio, a real site running on Duggie

Not a video, not a sandbox screenshot. Two live sites and the CMS behind them: one you own, one you write for. Change a headline, watch it land, then send a rewrite to someone else's site for sign-off.

Open the demo

One click puts you in a workspace with two real projects: Riverside Studio, which you own, and Fieldstone Bakery, where Sam owns the site and you write the copy.

Change the headline

Open the hero-title asset, press Edit this content, change the words. Preview the draft on the live site, then publish. Every version is kept, so nothing can break.

Refresh, then hand off

Riverside Studio picks up the new copy on its next fetch. No build, no deploy, no developer. Then try the bakery: your rewrite came back with a note, and Sam decides what goes live.

No signup. No credit card. Ready instantly.

No SDKs. No schemas. No GraphQL. Just fetch your content.

Make a Request

const res = await fetch("https://api.duggiecms.com/v1/content", {
  headers: { "x-api-key": "YOUR_CLIENT_KEY" }
});
const { assets } = await res.json();

Get JSON Back

{
  "assets": {
    "hero-title": "Welcome to Our Site",
    "hero-subtitle": "Built with Duggie CMS",
    "cta-button": "Get Started",
    "hero-image": {
      "original": "https://cdn.duggiecms.com/.../hero.jpg",
      "large": "https://cdn.duggiecms.com/.../large/hero.jpg",
      "meta": { "width": 2400, "height": 1600 }
    }
  }
}

One CMS, two jobs

What you get out of it, and what your client gets out of it.

For you

No redeploys
Published content is live on the next API response. No build step, no pipeline.
No emergency content requests
Clients publish their own copy. The 6pm "can you change one word" email stops.
One fetch call, any framework
A GET with an API key returns JSON. React, Vue, Angular, or vanilla Javascript.
You decide what's editable
Mark assets editable per project. Everything else stays read-only to the client.
No staging server
Preview tokens render drafts on your live site. There's no second environment to maintain.

For your client

Nothing to learn first
Five asset types and one Save button. No tutorial, no admin-panel tour.
They can't break the site
They edit content, not code or layout. The design you shipped stays the design.
Preview before publish
Drafts render on the real site behind a short-lived token. Nothing is public until they publish.
Rollback in one click
Every publish is a version. Restore a previous one without calling you.
Approval when it matters
Editors submit for review; admins approve or reject with a note the editor sees.

Nobody's locked to anybody

The dependency question every freelancer gets asked, answered in the product instead of the contract.

Your client can own the project

They can hold the account and pay for it directly. You don't have to carry their subscription on your card.

You get invited in

You build it; they invite you as their developer. Admin access, per project, revocable by either side.

Transfer in one click

Hand a project to any member when the engagement ends. No downtime, no key rotation. The previous owner stays on as an Admin.

No lock-in, and you can check: export your full activity log as JSON or CSV any time, and transfer ownership whenever either side wants to. What happens to your content if a client leaves, or we do

How Duggie Compares

Most CMS platforms weren't built with the developer-client handoff in mind. Duggie was.

	Other CMS Tools	Duggie CMS
Content Updates	Redeploy or developer edit.	Instant via Content API.
Ownership	Sits with whoever built it.	Transfer the website in one click.
User Interface	Built for developers or admins, often steep learning curve.	Simple and focused. Built for non-technical users.
Integration	Theme system, SDK, or GraphQL schema.	One GET returns flat JSON.
Content Preview	Separate staging environment required.	Short-lived token allows exclusive draft viewing on your real site.
Approval Workflow	Enterprise tiers, or plugins	Built in. Optional per asset.
Version history	Higher tiers or plugins.	Every publish is restorable.
API Requests	Often metered, with overages.	Unlimited on paid projects.
Pricing Model	Per seat, tier or usage.	Per project. No per-seat charge.
Developer Workload	On call for content changes.	Hands-off after handoff.

Is Duggie Right for You?

A great fit if you're building:

Client sites you hand offthey edit safely, you stay out of the inbox
Multiple client projectseach isolated, with its own keys and members
Sites for non-technical editorsclient-safe editing without a heavyweight CMS
Team workflowsper-project Admin, Editor, and Viewer roles
Multi-language siteslocale delivery built in
Content someone answers forfull audit trail on every change
Sites that update without redeployspublished content is live on the next fetch

Not a fit if you need:

A visual page or layout builder
Relational content modeling (build your own in a JSON asset)
Parallel editing or content branching
E-commerce or checkout
A GraphQL API
Self-hosting or on-premise deployment
Enterprise SSO or compliance certifications

This page is powered by Duggie CMS

The content you just read (features, comparisons, steps) is served live from our own API. No hardcoded copy. No redeploys to update it. Just one fetch call, exactly like the one above.

Simple, Transparent Pricing

Other CMS platforms charge hundreds of dollars a month before you hit meaningful limits. Duggie is built for freelancers.

Free

One client site, free

$0/month

✓ 1 project
✓ 50 assets
✓ 250 MB storage
✓ 2 members, you and your client
✓ All content types (text, HTML, images, JSON, documents)
✓ Live Preview before Publish

Pro

As your client roster grows

$19/month first project

Founding rate, locked for as long as your subscription stays active.

Each additional project $29/month. Full pricing

✓ Unlimited API requests, no metered overages
✓ Unlimited assets, no per-project cap
✓ 2 GB storage per project, pooled across your account
✓ Invite your whole team, no per-seat charge
✓ Add projects as your roster grows
✓ Full audit trail and approval workflow
✓ Per-project roles: Admin, Editor, Viewer
✓ Ownership transfer, so your client can own and pay directly

No credit card required to start. Cancel or upgrade any time.

What if a client stops paying? Their site keeps serving on the free limits. What if Duggie shuts down? 90 days' notice, in the contract, and your content is one API call away. How that works

Ready to Stop Being on Call for Content Updates?

Build once, hand off, stay hands-off

Stop Being Your Client's Content Editor