If your org qualifies for Google for Nonprofits, take the free Workspace. Here's the honest list of who gets turned away — and what those orgs should do instead.
Let's start with the part that's bad for our business: if your organization qualifies for Google for Nonprofits, take the free Workspace. Don't buy email from us. Don't buy it from anyone. Free Google Workspace for Nonprofits, plus $10,000/month of in-kind search advertising through Google Ad Grants, is the single best software deal available to a small charity, and no flat-fee provider is going to beat zero dollars.
So the question worth answering is: who gets turned away, and what should they do?
Everything below comes from published documentation, not from us:
One limitation up front: eligibility rules vary by country, and Google validates through Goodstack (formerly Percent; Google used TechSoup before that, which is why half the guides online still tell you to go make a TechSoup account). We're describing the US rules in detail and the general shape elsewhere. Outside the US, treat the specifics as directional and read your local page. And Google moves this stuff — any pricing number here, ours included, deserves a fresh look before it goes in a budget.
This is the part that surprises people. Google publishes categories that are ineligible regardless of charitable status:
| Organization type | Eligible for Google for Nonprofits? | Where they get routed |
|---|---|---|
| 501(c)(3) public charity | Yes | Free Workspace + Ad Grants |
| Governmental entity or organization | No | Standard paid Workspace |
| Hospital or health care organization | No | Standard paid Workspace |
| School, university, academic institution | No | Google for Education (separate program) |
| 501(c)(4) advocacy organization | No | Standard paid Workspace |
| 501(c)(6) trade association | No | Standard paid Workspace |
| 501(c)(7) social or recreational club | No | Standard paid Workspace |
| Fiscally sponsored project (no own EIN) | Not directly | Applies through the sponsor |
Look at the middle of that table. Hospitals and health care organizations are out. So are government entities. Schools have their own program, which is fine for schools, but a community education nonprofit that looks school-adjacent can get stuck in a validation loop nobody enjoys.
The one that catches the most orgs is the tax-code detail. The IRS master file lists roughly 1.8 million registered tax-exempt organizations in the US, around 1.5 million of them 501(c)(3)s. The remainder — the (c)(4)s, the (c)(6)s, the (c)(7)s — are legitimately tax-exempt, run on volunteer labor and thin budgets, and outside Google's rules entirely. A neighborhood civic association is usually a 501(c)(4). A regional restaurant association is a 501(c)(6). Both feel like nonprofits to everyone who works there. Neither gets the grant.
(We wrote a whole post about the email mess that HOAs and community associations end up in — same shape of problem, different acronym.)
Google's admin docs cap a Workspace account at 600 domains — one primary plus secondary and alias domains. That's a generous number. No nonprofit is hitting it.
But the domain count was never the constraint. The constraint is that every domain in that account belongs to the entity that passed validation. Federated nonprofits — the ones with a national body and semi-independent state or metro affiliates, each with its own EIN, its own board, its own 990 — don't have one entity. They have thirty.
Three ways that plays out:
The affiliate qualifies on its own. Best case. It applies, validates, gets its own free Workspace — once someone digs up the determination letter and works through validation with Goodstack.
The affiliate is unincorporated. No EIN, no application. It either lives on subdomains inside the parent's account — which makes the parent's admin responsible for chapter password resets forever — or it goes buy email.
The affiliate is a (c)(4) or (c)(6) sister entity. Very common in advocacy: a (c)(3) that does education and a (c)(4) that does lobbying, same building, same staff, deliberately separate books. The (c)(3) gets free Workspace. The (c)(4) does not, and putting the (c)(4)'s mail inside the (c)(3)'s account is the kind of commingling counsel usually advises against.
That last one is the honest edge case where a paid provider earns its keep. Not because the software is better. Because the entity boundary has to be real.
Free Workspace gets you mailboxes. It does not get you a transactional email API, and that gap is bigger than the mailbox conversation.
Every nonprofit running online giving sends automated mail: donation receipts, recurring-gift failure notices, event confirmations, volunteer shift reminders, year-end tax acknowledgments. That's application mail. It comes from a server, not a person.
Google's published sending limits sit at roughly 2,000 messages per user per day through Gmail and 10,000 per day through SMTP relay. Fine for a spring appeal. Wrong tool for anything with a webhook behind it — no idempotency keys, no per-message logs, no delivery notifications.
So the free Workspace org adds a sending provider on top. Completely reasonable thing to do! But it means the free email stack has a paid line item in it, and it's worth budgeting for before year-end receipts go out rather than after.
For comparison, the JustEmails base plan bundles 1,000 transactional API emails per month into the $49/year, with additional 10,000/month tiers at $25/year each. Not because that's more generous than Google — Google doesn't sell this at all, at any price, inside Workspace. One caveat: a tier raises the monthly allowance only, not the daily sending ceiling, so check the daily limit against your busiest day before you plan a year-end receipt run around it.
Google for Nonprofits requires re-verification. Status lapses if the org's registration lapses, if the validation request goes unanswered, or — the easiest one to miss — if the staff member who owns the account leaves and nobody catches the renewal email.
When the grant ends, keeping the account means paying for it. Google Workspace's standard rate starts at $84 per user per year, so a 14-person org that stopped being eligible in March is suddenly looking at $1,176/year on a line item that was $0 in February. The timing is cruel, too, because the orgs most likely to lose status are the small volunteer-run ones with no slack in the budget.
The lesson isn't "don't use Google." It's: put the re-validation date in a shared calendar owned by the board, not in one person's inbox. (Boring advice. Also the advice nobody follows until it bites.)
Say you're the (c)(6) trade association, or the hospital, or the chapter that can't validate. You're paying retail. Here's the math at three sizes, using list prices as of September 2026:
| Mailboxes needed | Google Workspace (from $84/user/yr) | Zoho Mail (from $12/user/yr) | JustEmails |
|---|---|---|---|
| 5 | $420/yr | $60/yr | $49/yr |
| 15 | $1,260/yr | $180/yr | $49/yr |
| 40 | $3,360/yr | $480/yr | $49/yr |
Zoho is genuinely cheap and I'm not going to pretend otherwise — for a five-person org that wants familiar webmail and doesn't care about a second domain, it's a fine answer. The per-user model just stops being cheap once you want real mailboxes for volunteers@, events@, board@, giving@ and a per-program address for each of six programs.
And yes — that 40-mailbox row flatters us, and I'd rather point at it than let you catch it. An org running 40 mailboxes usually wants SSO and a shared calendar. We sell neither. Read the trade-off below before you screenshot the table.
Flat-fee changes what you're willing to create. JustEmails is $49 a year, flat, for unlimited custom domains and unlimited mailboxes with a unified inbox across all of them — additional team members are $2 per member per month, and storage beyond the included 10 GB is $99 a year per 100 GB. A role address costs nothing and nobody has to ask permission.
The trade-off, stated plainly: 10 GB total storage on the base plan, shared across the account. Google's Workspace storage figure is 30 GB per user. If your org has ten years of attachment-heavy mail and no archiving discipline, Google's storage is better and that's just true. No calendar, no contacts app, no native mobile apps, no SSO either — it's mail, not a productivity suite. If Docs and Meet are load-bearing for you, this comparison isn't really about email anymore. We've laid out that whole trade in the flat-fee vs per-mailbox pricing breakdown.
If you're a US 501(c)(3) and you haven't applied: stop reading and go apply. Free Workspace, plus Ad Grants if you have anyone who can manage a search account. This is the correct answer and there's no asterisk on it.
If you're a federated org with affiliates: audit which ones have their own EIN and determination letter, and get those validated individually — separate accounts, less support burden on national. For the ones that can't validate, decide deliberately whether they live on your subdomains or buy their own. Don't let it default.
If you're a (c)(4), (c)(6), (c)(7), hospital, or government entity: you were never getting the Google for Nonprofits grant. Price flat-fee against per-seat at your real mailbox count, including the role addresses you'd create if they were free. Coming off a paid Workspace tenant? Our Google Workspace migration walkthrough covers the IMAP move and DNS cutover order, and the flat-fee alternatives roundup covers the other providers worth quoting.
If you already have free Workspace but you're bolting on a sending provider: that's the one place worth a second look. Keep Google for mailboxes — it's free, obviously keep it — and price the transactional side separately. Mailboxes on Google, application mail somewhere with an actual API, is a perfectly sane split.
One related product from the same studio: JustAnalytics does cookieless site analytics if you'd rather not run GA4 on a donation flow.
The thing I'd want a nonprofit ops person to take away isn't a product. It's that the assumption that Google is free because you're a nonprofit is worth testing against your actual EIN and entity type before you build a plan on it.
Google's published exclusions cover governmental entities, hospitals and health care organizations, and schools, academic institutions and universities (those route to Google for Education instead). In the US, you also need 501(c)(3) status specifically — 501(c)(4) advocacy groups, 501(c)(6) trade associations and 501(c)(7) social clubs are outside the rules even though they're tax-exempt. Fiscally sponsored projects apply through their sponsor, not on their own.
Yes, within one account. Google's admin docs cap a Workspace account at 600 domains total — one primary plus secondary and alias domains — which is far more than most nonprofits need. The real limit isn't the domain count, it's that every domain has to belong to the same legal entity that passed validation. An independent affiliate with its own EIN can't ride on the parent's grant; it has to qualify separately.
No. Workspace gives you mailboxes and Gmail's SMTP relay, not a REST API for sending donation receipts, event confirmations or recurring-gift failure notices. Google publishes hard sending caps too — roughly 2,000 messages per user per day through Gmail and 10,000 per day through SMTP relay. Nonprofits sending automated mail typically bolt on a separate provider and pay for it on top of the free grant.
For more than a handful of mailboxes, flat-fee hosting usually costs less than per-user plans. JustEmails is $49/year for unlimited domains and unlimited email accounts, with 10 GB storage, full IMAP/SMTP/POP3, auto SPF/DKIM/DMARC setup and 1,000 transactional API emails per month included. Google Workspace's standard rate starts at $84 per user per year, so against Google the gap widens with every mailbox you add.
Unlimited custom domain email hosting for $49/year flat — unlimited domains, unlimited mailboxes, 10 GB storage, full IMAP/SMTP. Built for agencies, freelancers, and anyone managing email across more than one domain.