CiviCRM
Community2 services
CiviCRM, the open-source CRM built for nonprofits, NGOs and advocacy groups — contacts, donations, memberships, events and campaigns — with a dedicated MariaDB database.
What you get
- All 2 services provisioned together: civicrm, civicrm-db
- A community template, not yet verified end to end by the Railyard team
- Automatic HTTPS and zero-downtime deploys
How to deploy CiviCRM
- 1
Connect a server
Attach a DigitalOcean, Hetzner or Vultr server to Railyard, or any Linux box over SSH.
- 2
Click "Deploy CiviCRM"
Railyard builds the container and provisions all 2 services.
- 3
Set your domain
Point your domain at the app. Railyard issues an HTTPS certificate and keeps it renewed automatically.
Why deploy on Railyard
Railyard provisions all 2 services in this stack together — civicrm, civicrm-db — wired to reach each other over the private network, on a server you already pay for.
Deploying CiviCRM is one piece of a bigger stack you can keep building — add a database, a worker, a cache, or another app, all on the same servers you already pay for.
Good for
- A nonprofit or NGO tracking donors, donations and memberships without a paid CRM subscription
- Event registration and campaign/advocacy tracking for an association or advocacy group
Good to know
- Three separate volumes (private, public, ext) match upstream's own compose exactly — ext holds installed CiviCRM extensions, public/private split holds uploaded files by visibility
- Redis is in upstream's own reference compose as an optional cache — upstream's own docs call it experimental ('little experience with different redis versions'), so it's skipped here; CiviCRM works without it
- No admin account is pre-seeded — CiviCRM's own installer finishes setup from the web UI on first visit