See the Directory page.
See the Meals page.
See the Pricing & Sustainability page.
Communities deserve great tech, and great tech is expensive to build and maintain. See the Pricing & Sustainability page for more detail.
Almost certainly. Gather is already in heavy use in multiple communities which depend on it to run their meals programs, common spaces, member directory and more.
Building a bigger community of paying subscribers will only deepen the system’s sustainability.
Yes, as long as there is a firm and accountable hours commitment and those offering to contribute possess the necessary skills. Contact us and let’s talk!
See the Reservations page.
See the Wiki page.
See the Work page.
It depends on the type of help you need!
Not yet but there will be. We have been focusing our resources to date on building functionality, and relying on communities members to support each other in using Gather.
We recognize documentation is necessary, especially for some areas of the system. We will cover the most commonly asked questions in this document for now. When more substantial documentation is rolled out, we will move much of this content there.
There will be very soon. We have plans to set up a Discourse forum for the community within the next few weeks.
Please contact us. We appreciate it!
We have chosen a very well established technology stack to ensure Gather’s longevity:
Currently we offer CSV export of member data. Meals and accounts are not far behind. CSV is great for doing data analysis, importing to other tools, etc.
However, we recognize that CSV outputs are not complete archives of your data. For this reason, we also pledge to provide full SQL and filesystem dumps of your community’s data upon request.
We do not believe in data lock-in!
Not yet. What would you need one for? Let’s talk.
Gather is open source so anyone is free to setup their own instance.
Self-hosting is also not likely to be a cost-saving measure once you consider the value of your members’ time. Maintaining an active, complex web application takes a lot of time and expertise.
Self-hosting could be a sensible model if you have a lot of developer talent (and time) in your community and you want to do a lot customization. In that case, it would be great to work together to keep as much of that code as possible in the mainline and available for other communities to benefit from.
We like to think that contributing to Gather (either with code or with dollars) is an investment in a movement.
Heroku’s free tier is designed for experimentation, not production use, and Gather is a beefy enough application that your members’ experience will likely not be good on Heroku’s free tier. Some considerations:
Then there is support. As mentioned above, maintaining a production web application is not a trivial matter. (We like to say a web application is more like a dog than a hammer!) Heroku helps with some maintenance tasks but not all of them.
Given all this, we’d be much happier if your dollars were going towards supporting Gather instead of Heroku!