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.

Try Demo

No credit card required • Zero egress fees • Instant setup, no SDK needed

app.duggiecms.com

The Duggie asset editor with an unsaved draft

Edit this content. Nothing changes until you save.

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.

Step 3: try it yourself

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

Not a video, not a sandbox screenshot. A live site and the CMS behind it. Change the headline, refresh the site, watch it change.

Open the demo

One click puts you in a real project. Pick the Admin seat or the Editor seat.

Change the headline

Edit the hero-title asset the way a client would, then publish it.

Refresh the site

Riverside Studio picks up the new copy on its next fetch. No build, no deploy, no developer.

Open the demo No signup. No credit card. About a minute.

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

Make a Request

fetch("https://api.duggiecms.com/v1/content", {
  headers: { "x-api-key": "YOUR_API_KEY" }
})
.then(res => res.json())
.then(data => console.log(data.assets));

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",
      "medium": "https://cdn.duggiecms.com/.../medium/hero.jpg",
      "thumb": "https://cdn.duggiecms.com/.../thumb/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. Each said once, with the thing that proves 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
No SDK, no schema, no GraphQL. A GET with an API key returns JSON.
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.
Every project isolated
Its own keys, members, and quota. One client can't see another's content.
A record you can point at
Every edit, approval, and publish is logged with the actor, the timestamp, and a diff.

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 edits over anybody
Locked assets go read-only, with the editor's name on the banner.
Their languages, built in
Per-locale drafts and publishing from the same asset. No restructuring.

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.

Security & Safety Built In

Clients Can't Break the Site

They edit content, not code. Your design stays intact.

API Keys Are Secure

Scoped permissions. Revocable keys. Rate limiting.

Drafts Stay Private

Only published content is public. Drafts never leak.

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 (static) or developer edit (WordPress)	Instant via API. No redeploys, ever.
Ownership	Agency holds the account; client is locked to their developer	Client can own and pay directly. Transfer anytime with no downtime and no key rotation.
Client Interface	Built for developers or admins, not clients	Simple and focused. Built for non-technical clients.
Integration	Theme system, SDK, or GraphQL schema	One fetch call, any framework.
Content Preview	Separate staging environment required	Preview tokens put drafts on your live site. No staging server.
Developer Workload	On call for every content change	Hands-off after handoff
Approval Workflow	Enterprise tiers, or plugins	Simple Draft → Review → Publish, built in.
Audit Trail	Paid tier or unavailable	Included on all plans.
API Requests	Metered, with overage fees at scale	Unlimited on paid plans.
Pricing Model	Starts at $100–$400/month for meaningful usage	$19 first project, founding price.

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 redeploys

Not a fit if you need:

A visual page or layout builder
Relational content modeling (reference fields, linked entries)
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

Perfect for students and POCs

$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

Founding rate

$19/month first project

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

✓ 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.

Ready to Stop Being on Call for Content Updates?

Build once, hand off, stay hands-off

Try Demo Free

Stop Being Your Client's Content Editor

How Duggie Works

Create a Project

Add One Fetch Call

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

Open the demo

Change the headline

Refresh the site

Make a Request

Get JSON Back

One CMS, two jobs

For you

No redeploys

No emergency content requests

One fetch call, any framework

You decide what's editable

No staging server

Every project isolated

A record you can point at