Update modules without redeploying your site.

Both. The CLI (packdog) is the canonical path for automation and CI/CD. Every action is a one-liner. The customer dashboard at app.packdog.dev is the more pleasant path for daily admin: create packages, manage channels, grant project access to CI tokens and members, view activity and usage, all from the web. Same capabilities, different surface.

Both are designed for build-time package consumption. Packdog is for runtime browser loading: you upload once, browsers fetch from the edge on every page view, and you can roll back without a redeploy. See the comparison table above for the full diff.

It gives you the part of micro-frontends everyone actually wants, deploying and rolling back a piece on its own, without the part that hurts. Module federation exists to share dependencies across pieces, and that's where the version skew, bundle bloat, and coupling come from. Packdog skips all of it: each module is a self-contained bundle at a versioned URL, so you get independent deploys with no shared runtime to wrangle. If your pieces genuinely need to share one framework instance, you still want federation. If they're self-contained, like a widget, an embed, or a web component, you don't.

That's why channels exist. Mark prod as a protected channel; developers push freely to test, and only those you trust can promote to prod. If you've already promoted and a bug surfaces: packdog rollback --channel=prod steps back atomically. No redeploy.

Each channel shows the version it currently points at, and a version can carry a release label (v1.2.3) and the git commit it was built from. Set your package's repository and the dashboard links each commit straight to the source, so “what’s on prod?” is one glance, not an archaeology dig.

Yes. CI tokens (ci_*) are built for exactly this: scoped machine credentials, separate from any human login. Set PACKDOG_TOKEN as a CI secret; the CLI reads it. Same one-line install (npm i -g packdog) as on a laptop. Tag each push with its commit via --commit=$GITHUB_SHA so every version traces back to the source it shipped from.

None specifically. If your build produces a directory of files, Packdog accepts it. There's no required entry filename; your site loads what it needs from the version's URL. Vite, esbuild, Rollup, plain tsc, or hand-written JS: all work. ES modules, web components, plain bundles.

Technically, yes. A version is just a versioned bundle of files at a URL. If it's a plain ES-module library, your app imports it and calls what it exports; no DOM needed. Packdog is built for modules that ship to live sites, but nothing stops you using it as a versioned, rollback-able CDN for your own code.

Every successful GET /v1/packages/{id}/channels/{channel} that resolves to a version is one load. Failed auth, 404s, and 304s don't count. Logged in real-time to Cloudflare Analytics Engine, queryable from the admin API.

Start free: 25,000 loads a month, the whole platform, no card. Pro is $29/mo for commercial use: a million loads included, then $2 per 1,000, and we never bill you for bandwidth. Enterprise is custom. Full breakdown on the pricing page.

Cloudflare D1 (metadata) and Cloudflare R2 (files), in the EU region. The load and CI keys are random tokens, not user accounts, so no customer-identifiable data is required to use Packdog itself. Human sign-ins (admins and members) are handled by WorkOS, a dedicated identity provider, so Packdog never stores passwords, and enterprise SSO/SAML/SCIM are available through it. If your modules collect user data, that's your pipeline, not Packdog's.

Once you're approved, you're self-serve from minute one. Sign up at app.packdog.dev, name your workspace, and create a project. Install the CLI (npm i -g packdog), run packdog login, and packdog deploy your first module. It's live on a channel. Invite your developers by email; they accept, sign in, and they're in.

The honest reassurance isn't 'trust us to be around forever'; it's that you're never locked in. Your published modules are plain files served over standard URLs, and you keep your own source, so there's no proprietary format to get trapped in. If Packdog ever went away, you'd host the files anywhere else and repoint your loader. No rewrite, no migration project. Everything runs on managed Cloudflare infrastructure under Jetbit AS, not a personal machine.