Softwr

Nonprofits · head to head

CharityEngine vs Fluxx

CharityEngine logo

CharityEngine

Nonprofits

Nonprofit CRM with its own in-house payment processing rather than a third-party gateway

From
On request
Rated
-
Full reviewWebsite
Fluxx logo

Fluxx

Nonprofits

Configurable grants management for foundations that run complex, multi-stage funding programmes

From
On request
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: CharityEngine payment processing rates are negotiated and never published, so the total cost cannot be compared to a licence-only CRM without getting a quote and modelling your own volume in basis points.; Fluxx configuration flexibility means the system does very little until someone configures it, and foundations without a dedicated systems administrator end up paying the vendor or a partner for every change.
  • They diverge on capability: CharityEngine covers In-house payment processing, Fluxx covers Configurable data model.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which CharityEngine and Fluxx actually diverge.

Attributes where CharityEngine and Fluxx differ
AttributeCharityEngineFluxx

Identical on both: starting price (On request), pricing model (quote), free tier (No), platforms (Web), user rating (Not yet rated), category (Nonprofits).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in CharityEngine

  • In-house payment processing
  • Recurring giving recovery
  • Direct mail segmentation
  • Peer-to-peer and events
  • Advocacy and membership
  • Marketing automation

Only in Fluxx

  • Configurable data model
  • Card-based interface
  • Multi-programme workflows
  • Board and committee review
  • Payment scheduling
  • Applicant portal

What people use each for

The jobs each tool is most often brought in to do.

CharityEngine

  • A nonprofit processing high recurring gift volume that wants card updater and dunning built into the CRM rather than bought separatelynot Fluxx
  • Replacing a stack of a CRM, an email tool and a separate donation gateway with one contract and one reconciliationnot Fluxx
  • A direct mail heavy organisation that needs offline gift entry and mail file segmentation as first-class features, not add-onsnot Fluxx
  • An organisation whose finance team wants a single settlement file that already reconciles to donor recordsnot Fluxx

Fluxx

  • A foundation running six distinct funding programmes that each need their own application form, review panel and payment schedulenot CharityEngine
  • A regranting intermediary administering funds for multiple donors who each require separate reportingnot CharityEngine
  • A public agency distributing grant funds with statutory eligibility rules that must be enforced before an application can be submittednot CharityEngine
  • A funder moving off spreadsheets and email after grant volume made manual board packet preparation unworkablenot CharityEngine

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

CharityEngine

  • Payment processing rates are negotiated and never published, so the total cost cannot be compared to a licence-only CRM without getting a quote and modelling your own volume in basis points.
  • Because the vendor is both the software provider and the merchant processor, switching CRM also means re-papering merchant services and re-tokenising every recurring donor, which is a far larger project than a normal migration.
  • Subscription pricing is quote-only and reported entry points come from third parties rather than the vendor, so small organisations often discover the floor is well above what they budgeted.
  • The interface is dense and configuration-heavy, and organisations without a dedicated database administrator tend to use a fraction of what they pay for.
  • Implementation and data migration are billed on top of the subscription and are commonly the largest first-year line item, which is easy to miss when comparing monthly figures.

Fluxx

  • Configuration flexibility means the system does very little until someone configures it, and foundations without a dedicated systems administrator end up paying the vendor or a partner for every change.
  • Implementation commonly runs four to eight months and is priced separately from the subscription, so first-year cost is far above the annual licence figure.
  • No pricing is published and quotes scale with assets under management, which means two foundations making the same number of grants can be quoted very differently.
  • The card-based interface is unfamiliar to new users and reviewer adoption suffers without training, which matters because trustees use it a few times a year and forget between meetings.
  • Reporting is capable but the report builder is technical, and many foundations end up exporting to a spreadsheet or a BI tool for board-ready output.

Pricing, plan by plan

CharityEngine

On request
  • CharityEngine$undefined/year
    • Donor CRM and gift processing
    • In-house payment processing at a negotiated rate
    • Email, SMS and direct mail tools

Fluxx

On request
  • Fluxx Grantmaker$undefined/year
    • Configurable grantmaking workflows
    • Applicant portal and reviewer access
    • Priced by assets under management and grant volume
  • Fluxx Grantseeker$undefined/year
    • Free portal for applicants submitting to Fluxx funders
    • Tracks submissions and requirements across funders

Which should you pick?

Choose CharityEngine if

  • You need in-house payment processing.
  • You also want recurring giving recovery.
CharityEngine review

Choose Fluxx if

  • You need configurable data model.
  • You also want card-based interface.
Fluxx review

Questions people ask

Is CharityEngine or Fluxx better?
Neither clearly leads. CharityEngine starts at On request and Fluxx at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, CharityEngine or Fluxx?
CharityEngine starts at On request and Fluxx at On request.
Does CharityEngine or Fluxx run on more platforms?
Both run on Web, so platform support will not decide this one for you.
What is CharityEngine best used for?
CharityEngine is most often used for a nonprofit processing high recurring gift volume that wants card updater and dunning built into the crm rather than bought separately, replacing a stack of a crm, an email tool and a separate donation gateway with one contract and one reconciliation, a direct mail heavy organisation that needs offline gift entry and mail file segmentation as first-class features, not add-ons, an organisation whose finance team wants a single settlement file that already reconciles to donor records. Of those, a nonprofit processing high recurring gift volume that wants card updater and dunning built into the crm rather than bought separately and replacing a stack of a crm, an email tool and a separate donation gateway with one contract and one reconciliation are not what Fluxx is typically brought in for.
What can CharityEngine do that Fluxx cannot?
CharityEngine covers In-house payment processing, Recurring giving recovery, Direct mail segmentation, Peer-to-peer and events. Fluxx covers Configurable data model, Card-based interface, Multi-programme workflows, Board and committee review.

Answered from the vendors’ own pages

CharityEngine: Does CharityEngine publish pricing?

No. Both the subscription and the payment processing rate are quoted. Third-party sites report a starter tier around 550 US dollars a month, but the vendor does not confirm this.

Fluxx: Is Fluxx Grantseeker really free?

Yes, for applicants. It is the submission portal, and funders pay for Grantmaker.

CharityEngine: Is the payment processing optional?

In practice no. The processing is the product. Using an external gateway removes most of what distinguishes CharityEngine from cheaper CRMs.

Fluxx: How is Fluxx priced?

By quote, scaling with assets under management and grant volume. Implementation is a separate professional services fee.

CharityEngine: Is there a nonprofit discount?

Every customer is a nonprofit, so there is no separate discount; pricing is tiered by contact count and gift volume instead.

Fluxx: Can we configure Fluxx ourselves?

Yes, that is the point of it. But it requires a trained internal administrator; foundations that do not appoint one become dependent on paid services.

CharityEngine: How long is the contract?

Annual terms are standard, and multi-year commitments are used to buy down the rate.

Fluxx: How long does implementation take?

Typically four to eight months for a multi-programme funder, driven mostly by how long the foundation takes to agree its own process.

Share

Related pages

More on CharityEngine

More on Fluxx

Keep looking

Other head to heads