Why You Should Own Your Content (Not Rent It)

Medium, Substack, and WordPress.com remove a great deal of setup. They provide an editor, hosting, account management, and, in some cases, distribution or email delivery. That convenience is useful, especially when the alternative is spending the weekend configuring a server.

Using a hosted platform does not usually mean giving up the copyright to your work. The practical question is how much control you retain over the website around it: the domain, URLs, design, source content, subscriber data, and the process of moving elsewhere.

I would not leave that question until the day a price changes or a migration becomes urgent. A custom domain, a current export, and a tested backup are far easier to arrange while the site is working normally.

What website ownership means in practice

Copyright is only one layer. You can own every word in an article while depending on a platform to display it, deliver it to subscribers, preserve its URL, and keep the publication online.

For a working website, control usually comes down to five things:

• You control the domain readers use to find you.
• You can export the source content and original media in a useful format.
• You can move subscriber or customer data where the law and the reader's consent permit it.
• You have a backup that can restore the editable site, not only a copy of the public pages.
• You understand which features depend on the current provider.

A platform can score well on several of these points. WordPress.com provides content and media exports. Substack lets publishers export their subscriber list. Medium states that writers retain the rights to their work and provides account-data exports. The friction appears when an export does not include the design, URLs change, paid subscriptions need to be transferred, or a platform-specific feature has no equivalent at the destination.

Convenience has a contract attached

A hosted service chooses the limits of its plans, the features available in its editor, and the rules for content distributed through its network. Those terms can change. So can prices and recommendation systems.

This is not evidence that every platform is waiting to trap its writers. It is the operating model. The provider manages the infrastructure and product; the publisher accepts its current terms in exchange for that work.

The arrangement can be sensible. Medium offers access to its reading network. Substack combines web publishing, email delivery, subscriptions, and discovery. WordPress.com manages hosting, WordPress updates, security controls, and backups on eligible plans. Replacing those services with an independent site may create more control, but it also gives you more decisions to make.

The first protection is simple: use a domain you control. If the canonical address belongs to you, moving the site does not also require abandoning every URL readers already know.

How Publii changes the publishing model

Publii is a desktop content management system. You write and manage the site locally, then the application generates HTML, CSS, JavaScript, images, and other files for publication.

The public server does not need the Publii application, PHP, or a content database to serve those generated pages. Publii can publish through FTP or SFTP, Git, Netlify, GitHub Pages, GitLab Pages, Amazon S3, Google Cloud, and compatible manual workflows. You can change the destination later because the generated site does not require a Publii-specific server stack.

Its plugins and themes are installed in the desktop application. Themes shape the generated site, while plugins can modify the build or add browser-side integrations. A comments or analytics plugin may still connect the finished site to an external service, so “static” does not mean every feature runs without third parties.

If you want the architectural detail, this comparison of static and dynamic websites explains the difference.

Static output can be fast, but it still needs care

A static page can be delivered without waiting for a CMS and database to assemble it for each visitor. That removes a common source of server delay and makes caching straightforward.

It does not guarantee a sub-second website. Large images, web fonts, advertising, video embeds, analytics, and an overloaded host can slow down static pages too. Publii provides responsive-image settings, modern image formats, lazy loading, and output optimization, but the theme and services you choose remain part of the result.

This is the useful performance advantage: Publii starts with generated files and lets you see what each added integration costs. Test the published site on a real connection instead of relying on a performance claim made before your content and scripts existed.

You can read more about Publii's SEO and performance features.

Privacy starts with the services you choose

A basic Publii site does not need an advertising network, analytics script, or visitor account system. The application works locally and Publii does not collect app telemetry. That gives you a restrained starting point.

Your complete setup may still process personal data. Hosting providers keep operational logs, contact forms receive submissions, newsletter tools store email addresses, and embedded media can contact third-party servers. Whether you need a consent banner depends on what the site uses and the laws that apply to it.

Publii includes privacy and consent controls for grouping supported scripts and integrations. They still have to be configured and tested. No CMS can declare a site compliant with GDPR or CCPA without knowing its services, purpose, audience, and legal obligations.

If privacy is part of the reason for leaving a hosted platform, list the services the new site will need before you migrate. Replacing one bundled platform with six separate tools may improve control, but it does not automatically reduce data sharing.

A smaller public attack surface

Generated static pages remove several components commonly exposed by a live CMS: there is no public Publii login, no Publii application running on the host, and no content database behind each request.

That is a meaningful reduction in attack surface, not immunity. Your hosting account, domain registrar, deployment credentials, custom JavaScript, and third-party services still need protection. Use unique credentials, enable multi-factor authentication where available, keep local software and plugins current, and maintain a separate backup.

It is also important to distinguish WordPress.com from a self-hosted WordPress installation. WordPress.com manages core updates and provides security controls as part of its hosting. On a self-hosted site, the owner or host is responsible for the server and the chosen plugin stack.

Plugin choice is a maintenance decision

The WordPress ecosystem offers more than 60,000 plugins. That is valuable when a site needs specialized integrations, but the number does not translate into 60,000 vulnerabilities. A plugin becomes part of your maintenance surface only when you install it.

The real issue is dependency management. Each installed extension has an author, an update history, compatibility requirements, and code that may run on the public server. Reports from security companies such as Wordfence are a useful reminder to review extensions and remove abandoned ones, not a reason to treat every WordPress site as compromised.

Publii usually needs a shorter list because publishing and page delivery are separated. Its plugins still need updates, and browser-side services can still fail or change their terms. Install the feature you need, record why it is there, and delete it when that reason disappears.

Portability requires more than public HTML

Hosted platforms are not export-free. WordPress.com can export posts, pages, comments, taxonomy data, and media references, with a separate media download. Substack publishers can export subscriber data, and Medium provides account exports. These tools make leaving possible.

They do not make every move lossless. Theme design, comments, recommendations, analytics history, paywall rules, email automations, and platform-specific blocks may require separate work. Redirects matter if URL structures change.

With Publii, the editable project lives on your computer and the application can create a complete site backup. Keep a copy of that backup on another device or storage service. The generated HTML is useful as a portable public output, but it is not a substitute for the source project.

You can edit generated files in a code editor, although Publii may overwrite those edits during the next synchronization. Permanent changes belong in the content, theme, plugin, or custom-code settings used to generate the site.

If Publii development stopped, an existing generated site could continue to be served by a compatible host. I would not promise that the current application would run forever on future operating systems. Backups, source files, and published output are what make that risk manageable.

What the options cost in October 2026

Pricing depends on billing period, country, tax, audience size, and usage. The figures below use the providers' US pricing published on October 18, 2026:

• Medium: publishing is free. Partner Program earnings follow Medium's current engagement-based calculation rather than a fixed creator subscription plan.
• WordPress.com Personal: $4 per month when billed annually, or $9 on monthly billing. The annual plan includes a domain for the first year, and paid plans now support plugins.
• Substack: publishing is free until you enable paid subscriptions. Substack then keeps 10% of each subscription payment, with Stripe processing fees charged separately.
• Ghost(Pro): the Starter plan is $18 per month when billed annually. Paid subscriptions require the Publisher plan, listed at $29 per month, and Ghost charges no additional transaction fee.
• Publii: the application is free. You pay separately for a domain and any hosting or external services that exceed a provider's free allowance.

The percentage model deserves a quick calculation. Ten thousand subscriptions at $5 per month produce $50,000 in gross monthly revenue; Substack's 10% platform fee would be $5,000 before payment-processing fees. At a much smaller revenue level, the bundled publishing, email, payment, and discovery tools may be worth that fee. The decision changes with the publication.

A Publii site can run on free hosting, but “free” still has terms. Netlify's current Free plan has a hard monthly credit limit and pauses projects that exhaust it. Cloudflare Pages offers a free plan with its own service limits. Vercel's Hobby plan is restricted to personal, non-commercial use. Check the provider's current policy before choosing it for a business site.

When Publii is the practical choice

Publii suits articles, portfolios, documentation, project sites, and small business websites whose pages can be generated before a visit. It is especially useful when you want a local writing environment, direct control over hosting, and a site that does not require a public CMS runtime.

The workflow is less attractive when several people need to edit the same site in real time, or when the product depends on customer accounts, live inventory, complex commerce, or personalized dashboards. External services can add comments, search, forms, newsletters, and payments, but every integration adds another account and another point of maintenance.

Hosted platforms also provide forms of distribution that an independent website does not acquire automatically. Moving a publication does not move Medium recommendations or Substack's internal network. If those channels produce a meaningful share of your readers, include that loss in the migration plan.

A useful ownership test

Before committing to any publishing system, answer these questions:

1. Can I use a domain that I control?
2. Can I export the content, original media, and subscriber data I am entitled to move?
3. Can I restore the editable site from a backup on another computer?
4. Which URLs and features would need rebuilding after a move?
5. Which part of my audience comes from the platform rather than from channels I control?

If those answers are documented and tested, you have a workable exit plan whether you publish with Publii, WordPress.com, Ghost, Medium, or Substack.

Try the complete workflow

1. Download Publii for Windows, macOS, or Linux.
2. Create one representative page or post in the WYSIWYG, Markdown, or Block Editor.
3. Choose a compatible host and connect it in the server settings.
4. Add only the external services the test site needs, then check their privacy and performance impact.
5. Create a Publii backup, store a copy outside the project folder, and synchronize the site.

That test exposes the real trade: Publii gives you local project ownership and portable static output, while you take responsibility for hosting choices, backups, publishing, and any external services.

Choose it when that responsibility is lighter than the limits of a hosted platform. Choose the hosted platform when its collaboration, email, payment, or distribution system is worth the dependency. In either case, keep control of the domain, maintain recoverable copies, and test the route out before you need it.

Pricing and plan details were checked against the providers' official pages on October 18, 2026.