DiscussionBridge Product Family Doctrine

Date recorded: 2026-07-25
Source: Phil through Bridge Boss
Status: Settled product and commercial doctrine

The following source statements are preserved intact:

Our model has been the Bridge is free for all, we support where we can, implementation and extensive hand holding is something we charge for. I have an alternative.

Do the plugin and Astro works fully featured, release for free, community support with us helping where we can, extensive help available for fee

Do the multi CMS plugin version as stand alone SaaS

Phil then settled the standalone product name:

yes Discussion Bridge SaaS

Phil settled the umbrella rule:

Everything stays under the Discussion Bridge tent

Canonical Interpretation

DiscussionBridge is one product ecosystem:

• DiscussionBridge for Discourse — free, fully featured Discourse plugin and local operational center.
• DiscussionBridge for Astro — free, fully featured Astro adapter.
• DiscussionBridge for Statamic and future publishing-system adapters — members of the same product family, with their release terms decided explicitly rather than assumed.
• DiscussionBridge SaaS — paid, managed, standalone orchestration for multiple CMSs, sites, adapters, and Discourse communities.
• DiscussionBridge Services — paid implementation, migration, customization, training, operations, and extensive support.
• DiscussionBridge Community — public documentation and community support, with the DiscussionBridge team helping as capacity permits.

The free products must be genuinely capable. DiscussionBridge SaaS sells managed multi-system orchestration, scale, convenience, governance, and operational relief—not freedom from artificial limitations.

All offerings remain under the DiscussionBridge name and share the portable DiscussionBridge Core, contracts, policies, terminology, identity model, and trust boundaries. Deployment host and service level may differ; the product does not fragment.