Self hosting or not self hosting?

AI-generated summary

The discussion revolves around whether it’s possible to develop and implement a new module on Discourse without self-hosting. Coban asks if custom modules can be added without self-hosting. merefield clarifies that backend API changes usually require higher-tier hosting plans, while UI/theme tweaks via Theme Components are often supported at no extra cost—depending on the host. They note that developing plugins is complex but deploying a self-hosted instance via tools like CDCK is relatively straightforward. RGJ adds that Theme Components work on any install, but plugins require host support—highlighting Communiteq as a provider that supports custom plugins. HAWK confirms official Discourse hosting also supports custom plugins, though plan-dependent. outofthebox endorses both official Discourse hosting and Communiteq, praising the latter’s value and contribution to the ecosystem. rokejulianlockhart seeks clarification on where to find official hosting info, to which merefield replies with the official pricing page: https://www.discourse.org/pricing. In short: UI/theme changes are widely supported; backend/plugin development requires host approval or self-hosting, with several providers offering managed solutions for plugins.

Hello all,

Thinking in deploying a discourse server :slight_smile:

Is there any way to develop and implement a new module without self hosting the discourse server ?

thx in advance for your answers

If you need to change the API, then hosting can become more expensive, as only higher tiers of hosting product usually allow you to deploy custom changes to the back end.

If however you are just wanting to change the look and feel and tweak the UI, leveraging the existing API set, a lot of hosts will allow you to deploy your own Theme Components at no extra cost (depending on the host and product level you are on!).

You will need to discuss this with a potential host.

All that said, if your “module” is novel and sophisticated enough it will require significant knowledge to write and so the hosting part will probably be really easy if you are that experienced. Developing Plugins is non-trivial and there is a bit of a learning curve. I’d argue a much steeper curve than the relatively easy path to deploy your own default instance on your own VPS (thanks in large part to CDCK’s effort to make things straightforward).

It depends on what you mean by “module”.

Theme components are supported on every Discourse install, regardless of being hosted or self hosted.
Plugins do require support from your hosting provider. At Communiteq we offer managed hosting with support for self-developed plugins and plugins that have been developed for you.

We also support custom plugins on our official hosting, but it is plan dependant.

Hi @coban,

I had great experiences with both official Discourse hosting and Communiteq. I’m now with @RGJ for the pricing. It’s been an excellent experience in every way!!! Their business makes the Discourse ecosystem better. No referral, just a happy customer.

@HAWK, where is information about your official hosting available at? [1] I’ve been unable to locate anything that appears “official” when searching Google or here:


  1. gitlab.postmarketos.org/postmarketOS/postmarketos.org/-/issues/200#note_482080 ↩︎