Practical overview
When it fits
Use Culturestake when a community or cultural organization wants a blockchain-based quadratic-voting process for local cultural choices and has the technical capacity to run the application.
Who it is for
- Communities seeking input on local cultural activities.
- Artists and cultural organizations involved in collaborative arts commissioning.
- Developers or organizations able to self-host a JavaScript application with PostgreSQL.
Documented uses
- Collect community preferences about the kinds of cultural activity people want locally.
- Support shared decisions between communities and artists about cultural programming.
- Give cultural organizations information about local interests to inform commissioning and investment.
Requirements & limits
The project is a public repository licensed under AGPL-3.0. The README documents a Node 14 environment and PostgreSQL database as requirements.
- The documented voting use case is cultural decision-making and investment, not broad-purpose governance.
- Local development requires Node 14, PostgreSQL, database setup and a client-asset build.
- The README points to a separate repository for local Docker development support.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Prepare a local development environment
Install the application dependencies, initialize its database and build the client assets required before starting the local server.
Before you start
- Node 14 environment
- PostgreSQL database
Steps
Install dependencies with the command below and copy
.env.exampleto.envfor local development.npm installInitialize the database with the command below and the command below.
npm run db:migratenpm run db:seedBuild the client assets with the command below, or use the command below to rebuild them as changes are made.
npm run client:buildnpm run client:watchStart the local server and watch for changes with the command below.
npm run server:watch
Expected outcome
A locally prepared development instance with initialized database data and client assets, followed by the local server process.
Guide limitations
- The README requires client assets to be built at least once before running the local server or tests.
- The documented seed process creates an initial admin user for development; the README does not describe production account configuration.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 16 October 2026
- Original website title
- bitspossessed/culturestake · Official homepage title · retained in its source language

