A small nonprofit usually runs three systems nobody budgets for properly: a donor database, a mailing list, and an archive of receipts and grant paperwork. Commercial SaaS for those three runs $60 to $250 per month at charity rates, often more once contact counts pass a few thousand. A single $8 to $12 budget VPS can carry all three with open-source software, but only if you size the box for the heaviest component rather than the average, and only if the backup story is genuinely defensible to a board.
The numbers below assume a charity with 1,500 to 8,000 donor records, a list of 3,000 to 12,000 email contacts sending two to four campaigns a month, and 20 to 80 GB of scanned receipts and grant documentation accumulated over several years.
Sizing the box for three workloads at once
Donor databases built on MariaDB or PostgreSQL are light: 1,500 to 8,000 records is a few hundred megabytes, and query load is a handful of requests per minute. The mailing list is the memory consumer, and the receipt archive is the disk consumer. Plan for 4 GB RAM and 80 GB of NVMe at minimum; 2 GB will run the database but leaves nothing for the mail queue during a campaign.
CPU matters less than you expect. A 2 vCPU plan handles all three comfortably except during a mail send, when the queue processor and the database compete. Set a send rate cap in your mailer (10 to 20 messages per second is ample for 12,000 contacts) so the campaign does not starve the donor portal for the twenty minutes it runs.
Software that costs nothing and is defensible
CiviCRM is the standard open-source donor database and runs on WordPress or Drupal; it handles donations, pledges, recurring gifts, tax receipts and contact history. For the mailing list, Listmonk is a single-binary mailer with a clean admin UI, list segmentation and bounce handling, and it stays fast with tens of thousands of contacts on modest hardware. Paperless-ngx covers the archive: it OCRs scanned PDFs, tags documents, and makes grant paperwork searchable.
All three are free, actively maintained, and backed by real documentation. Total licence cost: zero. What you pay for instead is a competent sysadmin afternoon and the discipline to keep the stack patched. Our budget VPS guides cover the LEMP baseline these three expect.
The outbound email problem, and how to solve it cheaply
Most budget hosts block port 25 to prevent spam, and even where it is open, a fresh IP sending 12,000 messages will be filtered by Gmail and Outlook. Do not try to run your own MTA for campaigns. Use Listmonk pointed at a transactional relay — Amazon SES at $0.10 per 1,000 messages, or Postmark and Mailgun in the $15 to $35 per month range for 10,000 to 50,000 sends.
At 12,000 contacts and three campaigns a month, SES costs roughly $4 monthly after the free tier, plus a few dollars for bounce and complaint processing. Set up SPF, DKIM and DMARC properly on the sending domain; a nonprofit whose appeal lands in spam has saved money and lost donations. Budget $0 to $35 per month for this line and treat the higher end as the safe default for a first campaign.
The monthly cost breakdown
| Item | Monthly | Notes |
|---|---|---|
| VPS, 4 GB / 80 GB NVMe | $8–$14 | 2 vCPU sufficient |
| Off-site backup storage | $2–$4 | 100 GB encrypted, versioned |
| Email relay | $4–$35 | Depends on volume and provider |
| Domain and TLS | $1–$2 | Let’s Encrypt free |
| Monitoring | $0–$3 | Uptime Kuma on the same box or free tier |
| Total | $15–$58 | vs $80–$250 for SaaS equivalents |
Annualised, that is $180 to $700 against $960 to $3,000 for a comparable SaaS stack. For a charity, the saving is often a grant line item’s worth of money, but it comes with an obligation: somebody must own the server.
Backups a board can actually sign off on
Donor records and receipts are regulated data in most jurisdictions, and losing them is a governance incident, not an inconvenience. Run Restic or Borg nightly to object storage with a separate credential from the server root, enable versioning on the bucket, and keep 30 daily and 12 monthly restore points. Encrypt client-side so the storage provider holds ciphertext only.
Then write the restore drill into the operations calendar: once a quarter, restore the database and a sample of documents to a scratch directory and confirm they open. Two hours, four times a year. A backup nobody has restored is a belief, not a control, and auditors increasingly ask for evidence of the test.
Access, handover and the volunteer problem
Nonprofits turn over staff and volunteers, so the server must survive the person who set it up. Store credentials in a shared password manager (Vaultwarden on a $4 box, or a free Bitwarden organisation) rather than in one person’s notes. Document the stack in a single README: what runs where, how to restart each service, where backups live, and who holds the domain registrar login.
Give the executive director a read-only observer account for monitoring and a written page describing what to do if the site is down. Two named people should be able to restore service, not one. This is the real difference between a cheap server and a fragile one.
Privacy, compliance and hosting location
Donor data is personal data under GDPR and similar regimes. Choose a host with a clear data-processing agreement, a stated data centre country, and a documented deletion process. EU-based hosting is the simple answer for European charities; US hosting needs a lawful transfer basis and careful vendor review. Budget hosting does not exempt you from this — if anything, a small provider is less likely to have a DPA ready, so ask before you buy.
Also decide on a retention schedule for receipts before you upload years of scans: statutory retention for financial records typically runs six to ten years depending on jurisdiction, and documents past that window are a liability rather than an asset.
What this setup is not good for
It is not a payments processor — take donations through Stripe or PayPal and record the transaction in CiviCRM rather than handling card data on the box. It is not a good fit for a team that cannot commit two hours a month to patching. And it is not appropriate for an organisation whose fundraising depends on 99.99% uptime during a giving day, unless you add a second small box and a load balancer.
For the other 90% of small charities, one well-run budget VPS with CiviCRM, Listmonk and Paperless-ngx replaces three subscriptions, keeps donor data under your own control, and costs less per year than a single month of the SaaS alternative. Start with a 4 GB plan, run the stack for a month before migrating real data, and only then cancel anything.



