# Any interest in LibreTime available as a SaaS with hosting and support?

**URL:** <https://discourse.libretime.org/t/any-interest-in-libretime-available-as-a-saas-with-hosting-and-support/121>\
**Category:** Community\
**Created:** [March 15, 2018, 2:59am UTC](https://discourse.libretime.org/t/any-interest-in-libretime-available-as-a-saas-with-hosting-and-support/121 "2018-03-15T02:59:52Z")\
**Posts on this page:** 1\
**Showing post:** 18

<div class="post-metadata">

**Author:** ![gusaus](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.libretime.org/gusaus/32/42_2.png) [@gusaus](https://discourse.libretime.org/u/gusaus)\
**Post date:** [August 15, 2019, 5:05pm UTC](https://discourse.libretime.org/t/any-interest-in-libretime-available-as-a-saas-with-hosting-and-support/121/18 "2019-08-15T17:05:51Z")

</div>

One takeaway from this discussion is any sort of customer-facing service offering (including a beta) should be decoupled from LibreTime development. Using [Open Collective as a conduit](https://discourse.libretime.org/t/opencollective-to-help-sustain-the-project-and-community/84), developers could build and maintain custom features and specific integrations (i.e. Drupal, WordPress), provide security updates, mentor and train users members via a partner or organizations collective.

For example, if Fourth Estate had a collective, it could create a campaign for each custom instance of LibreTime. Developers could invoice against the collective and/or a % of funds could be transferred to the LibreTime collective as a way to fund ongoing development.

A service provider/partner could use Open Collective to help sustain the OSS project(s) and contributors in a similar fashion.

The LibreTime team is still sorting out a process for using Open Collective and other tools to sustain the project. Accommodating the needs of partners and supporters in this discussion should certainly help.

---

_[View the full topic](https://discourse.libretime.org/t/any-interest-in-libretime-available-as-a-saas-with-hosting-and-support/121)._