Resource Review12 min read

Harvest (formerly HarvestSites)

3.8Editor rating

An ambitious all-in-one church platform built around managed, AI-assisted websites and connected ministry modules—promising for a church that wants one vendor, but pricing, giving fees, assurance language, portability, and production evidence need written clarification before migration.

Starting price
Harvest Sites $100/month · 14-day trial
Free tier
No
Platforms
Web · hosted church sites · social, email/SMS, ChMS, giving, teams, and apps
Developer
Harvest · founded by James and Jacqueline Taylor, Tanner Moushey, and Justin Dean
Launched
2024
Updated
Aug 9, 2026
$100/monthCurrent Sites price
14 days · no cardTrial
500+ churchesVendor adoption claim
99.9%Managed-site uptime claim
1.9% + 30¢Giving card claim
2.9% + 30¢Pricing FAQ giving claim
Jan 9, 2026Policies updated

The verdict

Harvest has expanded the former HarvestSites idea into a broad church operating platform. Its strongest proposition is coherent: describe a church, generate or commission a site, edit through conversation, host it with backups and monitoring, and connect sermons, events, forms, people, communication, social, serving, giving, and apps. The live pricing data is unusually inspectable, and the 14-day no-card trial lowers evaluation friction. Public evidence is not yet strong enough for an unqualified migration. Official pages describe Sites both as AI-generated and as designer-built, two Giving pages conflict on card fees, assurance claims lack attached reports, and the legal pages omit crucial service, export, processor, refund, and migration detail. Treat the website as a pilot, not the procurement record; require a dated order form, data map, DPA, security evidence, ownership and export terms, SEO migration plan, and parallel tests before consolidating ministry data or donations.

Try Harvest (formerly HarvestSites)

Opens getharvest.one

Harvest is the current brand for the product faith.tools listed as HarvestSites. The original focus—church websites—remains a central module called Harvest Sites, but the company now markets a connected suite: Sites, Social, Engage for email and SMS, Connect as a church-management system, Teams for volunteers and service planning, Giving, a shared or custom mobile app, Studio design tools, and Harvest One for small-church websites. The former harvestsites.co address did not respond during our review; the active official home is getharvest.one.

Harvest Sites promises two overlapping creation paths. Its feature page says a church can describe itself and receive a bespoke AI-generated site, refine design, copy, and layout through chat, and manage sermons, podcast feeds, complex events, staff, ministries, registrations, groups, forms, campuses, livestreams, and Next Steps. The live product record on the pricing page instead describes a managed church website built and maintained by Harvest designers with change requests. Both can be valuable, but buyers should determine which workflow, turnaround, revision allowance, and editor access are in the actual plan.

The public pricing application loads current product rows from Harvest’s own backend. On August 9, 2026, Harvest Sites was $100 monthly on Standard, Multi-Campus, and Influence selections. Social was $29, $79, or $159 monthly; Engage $39, $129, or $249; and Connect $29, $79, or $99. The builder says products can be combined, billing is month to month and prorated, there is no long-term contract, and the full-feature trial lasts 14 days without a card. Giving is marketed as free aside from transaction processing, but the feature page advertises 1.9 percent plus 30 cents for cards and 1 percent ACH capped at $5 while the pricing FAQ says 2.9 percent plus 30 cents. That conflict must be resolved in writing.

We reviewed the live platform, Sites, One, Social, Giving, pricing, about, privacy, and terms pages and their public product records on August 9, 2026. We did not create an account, generate or migrate a site, connect a domain, test chat editing, import people, post to social networks, send email or SMS, schedule volunteers, stream video, process or refund a gift, generate donor statements, test backups or restore, contact support, validate the claimed customer count, or perform an accessibility, SEO, legal, payment, privacy, security, SOC, PCI, uptime, or performance audit. Product metrics, testimonials, compliance language, uptime, speed, and security statements are vendor claims unless explicitly identified.

✓ The good

  • Church-specific website scope - sermons, podcast feeds, events, staff, ministries, groups, forms, campuses, livestreams, and next steps are first-class concepts
  • AI plus managed help - conversational creation and editing can accelerate work while a designer-maintained path may help teams without a web volunteer
  • Connected product vision - people, forms, communication, social, volunteering, giving, websites, and apps can share one account and data source
  • Current modular prices - the live builder exposes per-product costs instead of requiring a sales call for every normal plan
  • Low-friction trial - 14 days of selected products with no card and a paused account at the end supports a real sandbox
  • No stated long contract - public FAQ says month-to-month, prorated plan changes, and cancellation without a cancellation fee
  • Managed operations - the Sites page promises hosting, SSL, updates, daily backups, malware scanning, support, and 99.9 percent uptime
  • Unlimited-user claim - the pricing page says plans do not charge per staff user, helpful for volunteers and distributed ministry teams
  • Founder visibility - the company names its leadership, 2024 origin, locations, ministry experience, and contact paths

✗ Watch out

  • Product description conflict - public pages alternately describe an AI-generated chat-edited site and a designer-built managed site with change requests
  • Giving fee conflict - official pages currently state both 1.9% + 30¢ and 2.9% + 30¢ for card gifts
  • Assurance language is unsupported publicly - “SOC 2 compliant” and “SOC 2 Type II Certified” appear without a named audited entity, scope, date, or report
  • Portability is undocumented - public terms do not explain full site, content, design, database, media, donor, people, message, or audit-log exports on exit
  • Generic legal coverage - policies lack a public DPA, subprocessor list, breach notice, recovery objectives, data regions, controller roles, and detailed retention schedule
  • AI provenance is unclear - model providers, prompt and church-data use, training, human review, image and copy rights, retention, and opt-out controls are not published
  • Young platform risk - a 2024 company combining many high-stakes modules needs deeper uptime, support, migration, reconciliation, and continuity evidence
  • Marketing proof is limited - adoption figures and testimonials are vendor-selected and do not substitute for references or independently measured outcomes
  • Concentration risk - consolidating website, communications, members, volunteers, donations, and mobile access magnifies one outage, account compromise, or failed exit

Best for

  • Small or midsize churches that want a managed church website and may add connected communications or member tools gradually
  • Teams with limited design and development capacity that value natural-language editing and human support over complete platform control
  • Churches willing to pilot one lower-risk module before considering donor, member, communications, or volunteer consolidation
  • Multi-campus ministries that can negotiate written implementation, security, service, data, and exit terms for a broader suite
  • Organizations able to verify every AI-generated statement, image, accessibility label, event, sermon, and next-step workflow before publication

Avoid if

  • You need proven enterprise assurance, attached audit reports, SSO, detailed SLAs, recovery objectives, mature incident history, or a public trust center now
  • Your domain, content, design, redirects, search equity, donor records, recurring gifts, or member data cannot be exported in tested standard formats
  • You need exact international payments, tax receipts, consent, SMS, accessibility, privacy, residency, or retention support not established in contract
  • A single young vendor may not hold your website, directory, communications, volunteer scheduling, giving, design, and mobile experience simultaneously
  • Your church expects AI output, giving reconciliation, donor statements, or migration automation to replace human editorial, financial, legal, and pastoral accountability

What Harvest (formerly HarvestSites) is

Harvest is a modular software platform for church digital operations. Its website products create and host the public front door; Connect holds people and groups; Engage communicates by email and text; Social publishes content; Teams plans services and volunteers; Giving accepts contributions; Studio produces graphics; and app products extend church content to phones. The promise is that these modules share identity and data rather than requiring repeated integrations.

It is not the former time-tracking company with the same name, a denominational body, a bank, an accounting system, a legal or tax adviser, an independent security auditor, or a replacement for ministry governance. Even an integrated platform cannot decide what a church should publish, who may access pastoral data, whether a gift restriction is valid, or whether a message has meaningful consent.

Why church teams consider Harvest: one public story from first visit through belonging and giving

Most church stacks are assembled from a website builder, form tool, ChMS, email service, text provider, volunteer planner, social scheduler, giving processor, graphics app, and mobile app. Staff copy names, rebuild audiences, reconcile brands, and ask vendors to debug integrations. Harvest’s appeal is a shared platform: a visitor can discover an event on the site, submit a next step, enter Connect, receive Engage messages, join a group or team, give, and see consistent content in an app.

Integration also enlarges the privacy graph. A donation should not silently create a marketing profile; a prayer request should not become an AI prompt or social audience; a child check-in record should not be broadly searchable; and a website form should record the notice and consent that applied at submission. Before consolidation, map every field, legal purpose, role, sync, retention period, deletion path, export, and administrator. Limit each module to the minimum data it needs and test whether access or deletion propagates correctly.

Harvest Sites and Harvest One: fast creation must preserve ownership, search, and accessibility

Sites advertises a bespoke AI build from a description, chat-based revisions, sermon and podcast management, advanced events, staff and ministry directories, forms, volunteer signups, group finding, multi-campus pages, and integration with the rest of Harvest. Hosting includes SSL, daily backups, malware scanning, updates, support, and a 99.9 percent uptime claim. Harvest One offers a simpler theme-based path with YouTube, Google Calendar, Next Steps, a custom domain, and mobile design for smaller churches.

Pilot on a temporary domain. Verify DNS and domain registrant ownership, TLS, admin MFA, roles, staging, version history, backup restore, accessibility, image rights, semantic headings, alt text, keyboard navigation, captions, performance, structured data, canonical tags, sitemap, robots, redirects, analytics consent, spam protection, form delivery, and complete export. A migration must inventory every old URL and install permanent one-to-one redirects before launch. Human editors must fact-check AI copy, times, leaders, beliefs, locations, and calls to action.

Social, Engage, Connect, Teams, and apps: convenience depends on permissions and consent

Social promises scheduling, a content calendar, verse automation, analytics, marketplace designs, team approvals, and multiple accounts. Engage adds email, SMS, audiences, templates, automation, and AI credits. Connect manages people, households, groups, check-ins, prayer requests, tags, and next steps. Teams handles service plans, positions, availability, scheduling, songs, and reports. The app can be shared or custom-branded. Together these cover much of a church’s weekly coordination.

Test the boundaries more rigorously than the happy path. Require least-privilege roles, MFA, approval for mass sends and social posts, opt-in evidence, STOP and unsubscribe handling, quiet hours, guardian rules, child-data separation, prayer confidentiality, pastoral-note restrictions, duplicate and household merge controls, bounced-message hygiene, platform-token revocation, audit logs, and emergency offboarding. AI-written messages and verse graphics need source, translation, license, context, tone, and schedule review. Never let one compromised social or church account inherit every product.

Harvest Giving: attractive pricing claims require processor and reconciliation proof

Giving advertises one-time and recurring card or ACH gifts, funds, campaigns, donor history, receipts, tax statements, mobile checkout, optional fee coverage, public campaign and allocation views, reporting, and Stripe-powered payments. The feature page claims PCI-DSS Level 1, 256-bit SSL, SOC 2 Type II certification, no card numbers stored on Harvest servers, and a 1.9 percent plus 30-cent card rate. ACH is shown as 1 percent capped at $5.

The official pricing FAQ states 2.9 percent plus 30 cents instead. Resolve the rate and the audited entity before collecting a real gift. Obtain the merchant of record, Stripe account ownership, deposit timing, reserves, refunds, chargebacks, failed ACH, fee coverage, international and Amex rates, recurring-gift portability, donor data ownership, token migration, PCI scope, tax-statement responsibilities, fund mapping, reconciliation export, public-dashboard privacy, incident notice, and termination process. Run cents-level reconciliation from gift through fee, settlement, bank, ledger, refund, and statement before launch.

Pricing

Best value

Harvest Sites

$100/month

The live public product table listed the same $100 monthly amount for Standard, Multi-Campus, and Influence selections on August 9, 2026. Confirm campuses, build method, revisions, hosting, domains, storage, traffic, and support.

Harvest Social

$29–$159/month

Standard $29, Multi-Campus $79, and Influence $159 in the live builder. Public features include account scheduling, verse automation, marketplace content, analytics, collaboration, and approvals by tier.

Harvest Engage

$39–$249/month

Standard $39, Multi-Campus $129, and Influence $249, with public product records showing tiered email, SMS, and AI credits. Confirm credit definitions, overages, carrier fees, deliverability, and consent tools.

Harvest Connect

$29–$99/month

Standard $29, Multi-Campus $79, and Influence $99. Public records identify people limits of 1,250, 5,000, and 20,000. Verify households, groups, check-ins, permissions, imports, duplicates, and exports.

Harvest Giving

No platform fee claimed · processing applies

One page says cards cost 1.9% + 30¢ and ACH 1% capped at $5; the pricing FAQ says cards cost 2.9% + 30¢. Obtain the processor agreement, all transaction and event fees, settlement schedule, and exact rate.

The 14-day trial is useful because it provides selected products without a card. Use synthetic people, gifts, prayer requests, and messages; do not upload the membership database merely to evaluate navigation.

Harvest Sites currently appears as $100 monthly regardless of the selected organizational tier, while other products vary. Ask whether that reflects one feature set or a pricing-data simplification and what multi-campus and Influence labels change.

Month-to-month and prorated changes reduce commitment risk, but public terms do not spell out refunds, post-cancellation access, export window, deletion, domain transfer, content handoff, or recurring-gift migration. Contract those before import.

Module pricing can be attractive relative to multiple vendors. Total cost also includes email and SMS overages, app-store accounts, custom builds, content packs, payment processing, migration, training, integrations, support level, data cleanup, and exit work.

Do not compare Giving on headline percentage alone. A lower rate is valuable only when all card types, ACH, failures, refunds, chargebacks, fee coverage, deposits, reserves, statements, token portability, and reconciliation perform reliably.

Where Harvest (formerly HarvestSites) falls behind

Reconcile public product definitions and pricing so AI generation, designer builds, chat editing, change requests, tiers, campuses, hosting, revisions, and support are unambiguous.

Correct the conflict between the Giving feature page’s 1.9% + 30¢ card claim and the pricing FAQ’s 2.9% + 30¢ claim, with a complete dated fee schedule.

Publish a trust center with the exact SOC 2 audited entity, report type and period, scope, bridge letter, PCI roles, penetration-test summary, status and incident history, security contact, and vulnerability process.

Publish a DPA, subprocessor and model-provider list, data locations, transfer safeguards, breach-notice term, retention by record, backup deletion, child-data handling, and controller or processor roles.

Document AI providers and data flows, prompt and output retention, training use, human review, tenant isolation, image and text rights, safety checks, opt-out, provenance, and correction workflow.

Guarantee portable exports for site content and redirects, media, people and households, groups, notes, permissions, messages, consent, volunteers, gifts, funds, recurring tokens where possible, and audit logs.

Publish service commitments for uptime calculation, exclusions, support hours and targets, maintenance, backup frequency, tested restore, RPO and RTO, regional resilience, credits, and business continuity.

Provide migration matrices and reconciliation playbooks for domains and SEO, ChMS records, consent, email and SMS, social tokens, volunteer schedules, giving history, funds, deposits, and recurring donations.

Harvest vs. Subsplash vs. Tithely vs. a best-of-breed church stack

Harvest competes on modern creation, modular pricing, integrated workflows, unlimited staff users, and a young team moving quickly. Subsplash and Tithely have longer operating records, larger ecosystems, established apps and giving footprints, and more public customer history, though bundles and fees can be complex. Website specialists may offer deeper design, SEO, content modeling, and agency service while leaving the church to integrate member and giving tools.

A best-of-breed stack reduces single-vendor concentration and lets each team select a mature product, but creates identity, sync, permission, support, and reporting work. Harvest can win if its shared model genuinely removes that work without trapping the data. Start with the website or social calendar, demand portable interfaces, and measure support, uptime, editing, search, accessibility, and export. Move member or financial records only after contract, security, reconciliation, and exit evidence pass independent review.

The bottom line

Harvest’s rebrand from HarvestSites reflects a much larger ambition: become the connected operating layer for a church’s public presence, people, communication, service planning, giving, design, and mobile experience. The company has built a polished product surface, church-native concepts, transparent live module prices, a no-card trial, month-to-month language, managed hosting, daily-backup claims, and a plausible path for a small team to produce more without maintaining WordPress or a patchwork of tools. Those benefits deserve a real pilot. The public procurement record is not yet mature enough for blind consolidation. Sites is described both as an AI-generated chat-edited product and a designer-managed service. Giving advertises two different card rates on official pages. SOC 2 and PCI language is not tied publicly to precise entities and evidence. Privacy and terms are short and generic for a platform that can hold member, child, prayer, communication, financial, social, website, and AI data, and they do not establish the exports and exit rights a church needs. Begin with synthetic data and one reversible module. Require a dated feature and fee schedule, DPA and subprocessors, security reports, incident and recovery commitments, role matrix, AI data rules, domain ownership, complete exports, SEO redirects, gift reconciliation, and recurring-donor exit. Harvest may grow into a compelling all-in-one; responsible buyers should make evidence grow with it.

Alternatives to Harvest (formerly HarvestSites)

Frequently asked questions

What happened to HarvestSites?

HarvestSites became part of the broader Harvest brand at getharvest.one. The website product is now called Harvest Sites, while Harvest also markets Social, Engage, Connect, Teams, Giving, Studio, apps, and Harvest One.

How much does Harvest Sites cost?

The live pricing data we reviewed on August 9, 2026 listed Harvest Sites at $100 per month across Standard, Multi-Campus, and Influence selections. Confirm the exact included workflow and campus rights in a dated quote.

Does Harvest have a free trial?

Yes. Its public pricing FAQ describes 14 days of full access to selected products without a credit card. At the end, the church can subscribe or the account is paused.

Is Harvest Giving free?

Harvest says there is no platform subscription for Giving, but processing applies. Official pages conflict: one lists 1.9% + 30¢ for cards while the pricing FAQ lists 2.9% + 30¢. Get the complete processor fee schedule in writing.

Does Harvest use AI to build church websites?

The Sites page says it generates bespoke sites from a church description and supports chat editing. The pricing product record describes designer-built, maintained sites and change requests. Ask which creation and editing model your plan includes.

Is Harvest SOC 2 certified?

Marketing pages use “SOC 2 compliant” and “SOC 2 Type II Certified,” but the public material we reviewed did not identify the audited entity, scope, period, or report. Request the current report and confirm which Harvest products and processors it covers.

Can a church export everything if it leaves?

Do not assume so. The public terms we reviewed do not define complete exports for websites, designs, redirects, media, people, consent, messages, schedules, gifts, recurring tokens, or logs. Test exports and put ownership and exit duties in the contract.

Sources & further reading

More Church Management Software

B1 Church 4.9A genuinely free, open-source church platform - app, website, giving and check-in on one database - run by an Oklahoma nonprofit. The catch is not the price - it is that the vendor own docs call the native app deprecated.Involv Chat (church.chat) 4.9Involv Chat combines ministry-team messaging, rosters, blocked dates and service scheduling in a focused church workspace—useful when leaders protect volunteer consent and resist turning attendance or gifts data into a spiritual score.ChurchSoftware 4.9ChurchSoftware—formerly StoreHouse—offers an unusually broad church-management core for $0, including giving, check-in, accounting and a shared mobile app, while charging transparently for vendor-heavy extras.Pastor Notes App 4.9A two-app system that lets leaders publish sermon notes and invite live congregational response while attendees use the free Bible Notes companion—but its pricing math, refund terms and app privacy disclosures need correction before a church commits.Take Root 4.9A low-cost, offline-friendly relationship tracker built specifically for evangelism and discipleship follow-up—more intentional than a spreadsheet, but its old generic privacy policy does not adequately describe the sensitive ministry data the product exists to hold.Develop.Me 4.9Develop.Me packages course building, cohorts, discussion, assignments, gamification and mobile learning for churches and mission-driven organizations—with unlimited learners on paid plans, but a vague free tier and a 2022 website privacy notice leave procurement questions open.
Try Harvest (formerly HarvestSites)