Self-hosting Notipo

When to self-host

Self-hosting makes sense when:

• You need posts, drafts, or API keys to live entirely on infrastructure you control.
• You want to keep your WordPress credentials inside your own network.
• You're already running Docker on a VPS and prefer to add another container instead of paying for a SaaS subscription.
• You want to fork or modify Notipo for an internal workflow.

The hosted version at notipo.comis faster to set up, includes managed upgrades, runs the latest version automatically, and gives you a free tier with 5 posts/month. Pro at $19/month removes the limit and unlocks AI featured images. If you don't have strong reasons to self-host, the hosted version is the lower-friction path.

What's in the self-host build

The Docker images on GHCR are built from the same source as the hosted product, with two practical differences:

• No Stripe = all features unlocked. New signups land on the Pro plan automatically. The absence of STRIPE_SECRET_KEY is the switch.
• No Resend = no email verification. Signups auto-verify on creation. Configure Resend only if you want password-reset emails or admin signup notifications.

• Built-in markdown editor with slash commands, image paste, and auto-save
• Notion sync (status-driven publishing pipeline) — optional
• Direct publish from REST API, CLI, or MCP server (13 tools)
• Featured image generation — Unsplash photos out of the box, optional Gemini AI images via GEMINI_API_KEY
• WordPress Gutenberg conversion with Rank Math / Yoast / SEOPress / AIOSEO metadata
• Multi-tenant architecture (run a single instance for multiple WordPress sites if you want)
• Background jobs via pg-boss (Postgres-backed — no Redis required)

Where the images live

Multi-arch images (linux/amd64 and linux/arm64) are published to GitHub Container Registry on every release tag:

• ghcr.io/kfuras/notipo-api — Fastify backend, MCP server, job workers
• ghcr.io/kfuras/notipo-web — Next.js admin UI (static build, served by nginx)

Tags follow semver: 1.2.0, 1.2, 1, latest. For production, pin to a specific minor (e.g. 1.2) so you get patches automatically without surprise majors.

License (the short version)

Notipo is licensed under AGPL-3.0. Plain English:

• Use, modify, and self-host for any purpose, including commercial use.
• Fork it, extend it, ship internal tools on top of it.
• If you run a modified version as a hosted service to other people, you must publish your modifications under the same license. This is the Affero clause — it closes the network-service loophole that plain GPL leaves open.
• The notipo CLI on npm and the notipo-seo WordPress plugin are MIT-licensed (so they can mix freely with the WordPress and npm ecosystems).

Support expectations

Self-hosted is unsupported. Bugs in the released code can be reported on GitHub Issues and may be fixed on a best-effort basis, but there's no SLA, no migration help, and no guidance for custom forks. If any of those matter, the hosted product at notipo.com is the supported path.