The first publication rarely exposes the architecture of a publishing platform. The second one does. It may become another item in the same workspace, another paid site under the same login, another managed newsroom in a federation, or another organization inside software the operator controls. Those are different portfolio topologies, not plan names.
Pluma is a multi-publication operating system sold once as source. You deploy it under your own brand and run publication organizations with branded sites, selectable runtime templates, structured editing, newsletters, subscriber operations and paid memberships. This guide compares where credible alternatives place the second publication and who controls the surrounding platform.
The category map
| Where the second publication lives | Representative route | What the operator acquires |
|---|---|---|
| Inside the same managed workspace | beehiiv | Subscription access to a vendor-run multi-publication workspace |
| In a separate managed subscription | Ghost(Pro) | One managed publication per account and subscription |
| As another independent site under one login | WordPress.com | Separate hosted sites and plans managed from one dashboard |
| In a managed newsroom federation | Newspack | A newsroom-specific service with multi-site terms handled by quote |
| As another organization inside operator-controlled software | Pluma | Source for a purpose-shaped multi-publication operating system |
| Inside a commissioned system | Custom build | A delivery contract whose topology and operating model must be specified |
None of these routes is universally best. A managed workspace can remove infrastructure work. Separate subscriptions can preserve publication independence. A newsroom service can supply migration, revenue operations and support. Owned source can make the platform itself the asset. A custom build can express a requirement no existing product models well.
The useful shortlist begins by deciding which topology matches the business. Feature comparison comes after that decision because every feature inherits the account, ownership and operating boundary around it.
Five tests before comparing products
What is the platform's native container?
A product may call its container a workspace, account, site, publication, network or organization. The label is less important than the rule. Can several publications exist inside one commercial account? Are they independent sites that happen to share a login? Does every site require a separate subscription? Is the network relationship a custom service? Does the buyer control the container itself?
This test prevents a common category error. “Manage several publications” can mean switching between unrelated accounts from one dashboard. It can also mean operating several organizations under a platform role. Both are legitimate, but they solve different problems.
Who controls each publication?
An agency may need to manage a publication while keeping the client inside a limited area. A media group may want central platform control while each editorial brand retains its own owner. An independent publisher may prefer complete separation so no portfolio-level operator exists at all.
Look for the actual authority boundary rather than the number of team seats. Pluma's available record makes one boundary explicit: the instance operator controls the platform, and each publication owner controls only the relevant organization. beehiiv documents a different boundary: several publications can share a workspace, but a client needing its own login, billing or full ownership should use a separate account.
Which operating organization is included?
Managed publishing services sell more than interface access. They supply hosting, updates, backups, security operations, delivery systems, support and a product roadmap. Some add migration, design help, analytics, advertising networks or newsroom expertise. Those services can be more valuable than source control when the buyer does not want to become the platform team.
A source product transfers a different asset. The buyer controls and operates the codebase, but the purchase does not quietly include a competitor's infrastructure or support organization. Pluma's catalog record does not establish hosting, deployment, maintenance, delivery infrastructure, integrations, analytics, support or an SLA. Those are adoption questions, not implied features.
Does the audience relationship belong to the publication?
Pluma's documented publication unit includes newsletter, subscriber operations and paid memberships. beehiiv says each publication in a workspace keeps an independent subscriber list, settings and content. Ghost organizes members and subscriptions around one publication per managed subscription. Newspack combines audience and revenue tools with a managed newsroom service. WordPress.com supplies a broad site and plugin base from which the operator assembles the desired audience stack.
The distinction affects more than data organization. It determines where the operator configures the audience relationship, which vendor carries delivery responsibility and whether membership is native to the publication product or assembled from additional services.
What happens when the portfolio grows?
Growth can trigger another subscription, a higher workspace plan, a custom multi-site quote, more infrastructure responsibility or a new engineering project. The public price should therefore be read together with the product's container rule. A low single-site entry point can become a repeated portfolio expense. A one-time source price can still sit beside recurring hosting, delivery and maintenance costs that the source vendor did not document.
No total-cost claim is made here. The comparison records only first-party public ranges and the rule that determines when another publication changes the commercial relationship.
Several publications inside one managed workspace: beehiiv
beehiiv is the clearest managed multi-publication option in this shortlist. Its current help center says Launch and Scale plans can contain up to three publications, Max up to ten and Enterprise a custom number. Each publication has its own subscriber list, settings and content. The same documentation gives agencies two patterns: keep several client newsletters inside one account when the agency handles the work, or use separate client accounts when the client needs its own login, billing or full ownership.
At the 1,000-active-subscriber setting, beehiiv's public annual-billing prices ran from US$0–US$96 per month as of September 1, 2026, with Enterprise on custom pricing. The live page showed Launch at $0, Scale at $43 and Max at $96. Cost changes with active-subscriber tier and plan, according to beehiiv's official pricing and plan-tier documentation.
The topology is a vendor-run workspace. That brings meaningful advantages: web hosting, newsletter delivery, campaign and subscriber analytics, automations on paid plans, recommendation and advertising networks, paid-subscription tooling, and vendor support. A portfolio can begin without the buyer deploying a publishing platform.
The limit is equally clear. The workspace remains inside beehiiv, its plan rules and its roadmap. A client that needs complete account ownership moves to another account. Choose beehiiv when managed newsletter operations are the asset the buyer needs. Do not choose Pluma on the assumption that it recreates beehiiv's delivery, analytics or growth networks; those capabilities are not established by Pluma's record.
One managed publication per subscription: Ghost(Pro)
Ghost integrates a website, newsletter, members and paid subscriptions around a publication. Its open-source core, theme ecosystem and integrations make it one of the strongest publishing references in the market. Ghost(Pro) adds managed hosting, weekly updates, backups, CDN, security and support.
The portfolio rule is explicit. Ghost's help center states that one Ghost(Pro) subscription hosts one publication. Several sites with separate domains require separate accounts and subscriptions. At the 1,000-member setting, public annual-billing plans ranged from US$18–US$199 per month as of September 1, 2026, with a custom plan beyond them, according to Ghost(Pro) pricing and Ghost's multiple-sites guidance.
That topology is not a defect. It gives each publication a clear account and managed service. For one publication, or for a portfolio that values strong separation and accepts repeated subscriptions, Ghost can be the most direct route. A technical team can also evaluate self-hosting the open-source software rather than using Ghost(Pro).
Ghost remains stronger than Pluma when the priority is its mature ecosystem, managed operations, integrations and established publishing community. Pluma's distinction is not “Ghost with more sites.” It is a different source product whose native unit already includes several publication organizations under an instance operator.
Independent sites under one account: WordPress.com
WordPress.com lets one account own and manage several websites from a hosting dashboard. Its current support documentation says every site remains independent, with its own design, domain, subscribers and settings. Every paid site needs its own plan; one plan cannot be shared across the portfolio.
The public monthly-billing range was US$0–US$70 per site as of September 1, 2026, from the free plan through Personal, Premium, Business and Commerce, according to WordPress.com pricing. The multi-site rule comes from WordPress.com's account and site management guide, last reviewed August 28, 2026.
This route is broader than a purpose-built publication operating system. WordPress.com provides managed hosting, automatic updates, security, support and access to a very large plugin and theme ecosystem. An agency with enough client sites can also evaluate Automattic's agency program. The operator assembles the publishing, newsletter and membership combination required for each site.
That ecosystem breadth is WordPress.com's advantage and the main reason to choose it. A buyer can draw on established plugins, themes and specialists instead of accepting one product's narrower shape. The trade is that the portfolio relationship lives in the hosting dashboard and agency conventions rather than a Pluma-style instance-operator/publication-owner product boundary.
Pluma should not be presented as a replacement for WordPress.com's ecosystem. Its available record names no plugin marketplace, theme count, migration service or managed hosting. It is relevant when the buyer wants one source product whose publication unit already combines the branded site, runtime template, editor, newsletter, subscriber operations and memberships.
A managed federation for newsrooms: Newspack
Newspack is designed for small and mid-sized digital news publishers and combines a WordPress-based publishing platform with a managed service. Its official offer includes migration, staging, design and technical support, hosting, newsroom publishing tools, advertising, audience management, payment systems and a technical account relationship.
Public plans ranged from US$750–US$2,500 per month as of September 1, 2026 for publications below US$1 million in annual revenue. Publications above that level, and news operations with more than one site, are directed to a custom quote. Those ranges and conditions come from Newspack's official pricing. Its features and services page documents federated sites, managed infrastructure and newsroom support.
Newspack's second publication therefore lives inside a negotiated managed relationship, not a standard self-service plan. That can be exactly right for a media group that wants a vendor with newsroom expertise, migration capability, advertising operations and continuing support.
Newspack is the stronger choice when those services are required. Pluma's current facts do not establish migration, advertising, federated content, analytics, managed hosting, technical account management or newsroom support. The Pluma route is a source acquisition for an operator prepared to own a different platform, not a discounted way to obtain Newspack's service.
Publication organizations inside source-owned software: Pluma
Pluma places the second publication inside another organization on the same operator-controlled platform. Each publication receives a branded website, a selectable runtime template, a structured editor, a newsletter, subscriber operations and paid memberships. The instance operator controls the platform; each publication owner controls only the relevant organization.
That topology fits a buyer whose business model depends on operating the publishing platform under the buyer's own brand. It gives agencies, independent media groups and author networks a product-level relationship between the platform owner and publication owners. It also turns the codebase into an asset the buyer controls rather than an account the buyer rents.
The product record is unusually narrow in other areas. It does not establish analytics, automations, content migration, imports, APIs, advertising, recommendations, delivery infrastructure, payment-provider details, integration depth, deployment requirements, security controls, support or an SLA. It also does not state the number or customization range of runtime templates. Those omissions prevent a feature-parity claim against any managed vendor in this guide.
Pluma's catalog value resolves from $249 and checkout is open at https://saascode.ai/products/pluma. The demo at https://pluma.saascode.ai is the appropriate surface for evaluating the documented organization boundary and publication bundle first.
Source ownership also has a licence boundary. The buyer may customize the product, deploy it under the buyer's brand, operate it for paying end users and deliver a configured product to a client. The buyer may not resell, sublicense or redistribute the underlying source code. Pluma is software to build and operate a publishing SaaS business with, not software sold for onward redistribution.
A commissioned platform: custom build
A custom build is the right route when the portfolio relationship is the differentiator and no existing product expresses it. A buyer may need a specific editorial workflow, rights model, revenue arrangement, migration path or distribution system that should not be forced into a general platform.
The advantage is scope control. The limit is that the buyer must fund discovery, engineering, quality assurance, deployment and continuing maintenance. No universal dollar range is credible without a defined scope, team, region and service contract, so this guide does not invent one.
Custom also creates an evidence burden. “Bespoke” does not guarantee that membership, newsletter delivery, organization boundaries or multi-site runtime behavior are complete. Those outcomes must be written into the delivery contract and verified. Pluma may provide a more advanced starting shape when its documented publication model fits; custom wins when the difference itself is the business.
Which route fits the portfolio?
Choose beehiiv when several newsletters need to launch inside a managed workspace and beehiiv's delivery, analytics, growth networks and support are assets. Choose Ghost when the unit is one strong publication at a time and its ecosystem or managed service matters. Choose WordPress.com when ecosystem breadth and independent site assembly are acceptable. Choose Newspack when a newsroom needs a managed publishing, revenue and support organization.
Evaluate Pluma when the required shape is several publication organizations under an operator-controlled source platform, with a branded site, runtime template choice, structured editor, newsletter, subscriber operations and paid memberships for each publication. Commission a custom build when that shape is still too generic.
The shortlist should be narrower after this test. The platform that handles the second publication correctly is more likely to handle the tenth without forcing the business into an account structure it never intended.
Questions publication operators ask
Which platform supports several publications in one managed workspace?
beehiiv documents up to three publications on Launch and Scale, up to ten on Max and a custom number on Enterprise. Pluma also supports several publications, but through source-owned software the buyer operates rather than a vendor-managed workspace.
Which option is strongest for one mature publication?
Ghost is a strong answer when one publication needs an established publishing ecosystem and managed hosting. One Ghost(Pro) subscription covers one publication. Pluma becomes relevant when the native unit must be a portfolio under an instance operator.
Which option is strongest for a managed newsroom network?
Newspack is the strongest service-led option in this guide because it includes newsroom migration, design, hosting, advertising, audience tools and support. Multi-site operations receive custom terms. Pluma does not claim those managed services.
Can WordPress.com manage several publication sites?
Yes. One WordPress.com login can manage multiple independent sites, but each paid site needs its own plan. Pluma instead defines several publication organizations inside one operator-controlled source product.
When does Pluma fit better than a managed platform?
Pluma fits when the buyer wants the publishing platform itself under the buyer's brand and needs a platform role above organization-limited publication owners. It does not fit merely because source sounds cheaper; operating costs and responsibilities are not established by the current record.
Is Pluma available for immediate purchase?
Yes. Pluma is listed at $249 and can be bought at https://saascode.ai/products/pluma. The demo at https://pluma.saascode.ai can be evaluated first.