FAQ
Frequently asked questions about civic-dialog.org.
Is this really free?
Yes. Browsing and downloading assets is free with no account required. Publishing assets requires a contributor account, which is also free — just contact us to request access.
What kinds of assets are available?
The marketplace hosts automation assets across several categories: AI/LLM prompt chains, Make/Zapier/n8n workflow templates, Python and shell scripts, data transformation pipelines, and configuration files for common nonprofit tools. All assets must be documented with safety notes and setup steps.
How do I know an asset is safe to use?
Every asset goes through human review before being published. Contributors are required to document what the asset does, what it doesn't do, any known risks, and all prerequisites. After publishing, community members can leave reviews and flag concerns. Look for assets with high ratings and many clones as a starting signal — but always read the safety notes before running anything.
Can I use these assets in my organization right now?
Yes, with common sense. Read the documentation, check the license, and test in a non-production environment first. Assets are community-contributed and come with no warranty.
What license do assets use?
Each asset declares its own license — check the asset detail page. The platform defaults to recommending MIT or Apache 2.0 for maximum reuse, but contributors can choose any OSI-approved license.
How do I publish an asset?
You need a contributor account. Contact us to request access (we verify you're contributing in good faith), then use the publish form to submit your asset. It will go into a review queue and be live within a few days of approval.
I found a bug or safety issue with an asset. What do I do?
Click the "Report" button on the asset page. For serious safety issues, choose "Inaccurate safety information" or "Harmful content" as the reason — these are escalated to reviewers immediately.
Can I contribute code to the platform itself?
Absolutely. The platform is open source at github.com/civic-dialog-org/civic-dialog.org. Read the CONTRIBUTING.md to get started.
Who runs this?
A volunteer team. We have no investors and receive no revenue from the platform. Read more on the About page.
How is this funded?
Currently through volunteer time. We're pursuing foundation grants to cover infrastructure costs (hosting, storage, CI). If your foundation supports nonprofit technology infrastructure, we'd love to talk.
How does the matching work?
Nonprofits post an automation need through the Discovery Wizard, which helps translate the problem into a structured brief. Volunteer automators browse open needs, find ones that match their skills, and submit a proposal. The nonprofit reviews proposals, selects one, and the platform facilitates the introduction. Both sides confirm scope before work begins. The full project runs through an eight-phase structured workbench — from requirements through deployment — so both sides stay aligned throughout.
What if the automator doesn't finish?
It happens. Volunteer capacity is real. If an automator goes quiet or can't complete the project, the need returns to the wishlist and becomes available for a new match. We encourage both sides to communicate early if timelines shift — the platform has a built-in project workspace for exactly that. Nonprofits aren't locked in, and automators aren't penalized for life getting in the way — but sustained engagement builds the kind of portfolio record that actually matters.
Is there a cost to nonprofits?
No. The matching program, Discovery Wizard, project workbench, and impact tracking are all free for nonprofits. There are no subscription fees, no paywalls, and no vendor lock-in. Civic Dialog is operating as a nonprofit and is in the process of obtaining 501(c)(3) status in New York.
Still have questions?
Open an issue on GitHub or reach out via the contact information in the repository.