- Starting price
- Gloo AI Studio Pro $25/mo + usage; custom assistant pricing by quote
- Free tier
- No
- Platforms
- Web · Embedded assistant · API · Custom integrations
- Developer
- Gloo, LLC (acquired Faith Assistant in 2025)
- Launched
- 2023; acquired 2025
- Updated
- Aug 9, 2026
The verdict
Faith Assistant’s original proposition remains strong: let a ministry turn its own sermons, articles, studies, and policies into a conversational doorway that cites resources and hands difficult conversations to people. The 2026 buying reality is less simple. Faithassistant.com redirects to Gloo AI, the brand is absent from current navigation and Gloo+ benefits, and the promised free church version cannot be independently found as a current self-service offer. Evaluate Gloo’s present Data Engine or an enterprise assistant on a written scope—not an old press release—and do not put pastoral care on autopilot.
Try Faith Assistant ↗Opens gloo.com
Faith Assistant began as Bible Chat, founded by Chase Cappo and Andrew Rogers, and developed into a business-to-business conversational product for churches, publishers, seminaries, broadcasters, parachurch organizations, and home-school providers. Rather than answering from a general chatbot alone, it ingested an organization’s own sermons and content, then placed a customized assistant on that ministry’s digital surface. The acquisition announcement says it could answer questions, recommend resources, and connect a user with a staff member or volunteer. Luis Palau Association, Concordia Church, The Christian Post, and KCBI were named customers.
Gloo acquired the company on 15 January 2025. The announcement said the founders would continue the work, with Cappo leading Gloo’s AI Enterprise Division. It also said a free version for churches would launch on Gloo’s Kingdom-Aligned Large Language Model, advanced features would join Gloo+, and enterprise customers could commission fully custom models. That announcement is useful history, not a current price sheet. In August 2026, faithassistant.com redirects to Gloo’s broad AI landing page. The current Gloo+ comparison lists an AI Writing Assistant but not Faith Assistant. We found no public page where a church can create the promised free branded assistant, see its limits, or buy the old advanced tier.
What Gloo sells visibly now is both broader and more technical. Gloo AI Studio provides more than fifty models across Anthropic, OpenAI, Google, Llama, and DeepSeek families, an OpenAI-compatible API, automatic routing, safety screening, provider failover, tool calling, spend controls, and a playground. Its $25-per-month Pro plan adds a Data Engine that ingests websites, files, YouTube, RSS, and other content; provides a content library and semantic search; and generates grounded responses through retrieval-augmented generation. Enterprise adds recommendations, administrative controls, request logs, analytics, private transcription as a paid add-on, custom token pricing, contracts, invoicing, and a dedicated support channel. Those are successor capabilities from which a Faith Assistant-like experience can be built, but a platform is not automatically the original turnkey widget.
This is a researched review of the legacy Faith Assistant proposition and its current home inside Gloo. We read Gloo’s acquisition release, AI and pricing pages, developer documentation, legal terms, privacy materials, and current Gloo+ benefits. We did not receive an enterprise demo, build an assistant, upload ministry content, inspect a customer contract or DPA, measure answer accuracy, test escalation, conduct red-team attacks, or interview customers and people who used their bots. Vendor testimonials and claims are reported as such. The product’s current identity and availability are central to our score.
✓ The good
- Grounded in an organization’s own corpus - sermons, articles, policies, studies, videos, and feeds can inform answers and point readers back to known sources
- Human connection was part of the original design - the assistant could recommend a staff member or volunteer instead of treating every conversation as self-service
- Acquisition gives the product substantial infrastructure - Gloo now offers multi-model routing, failover, safety screening, spend controls, APIs, data ingestion, analytics, and enterprise agreements
- Current Pro entry is public - $25 per month plus usage buys the Data Engine, content library, semantic search, grounded completions, agents, and priority support
- Enterprise governance exists - role controls, activity logs, analytics, custom retention discussions, invoicing, service terms, and dedicated support are visible capabilities
- Content rights receive explicit treatment - Gloo says customers retain their content and private non-prompt content and configurations are not used to train models without written opt-in
- Theological alignment can be configured - an organization can define its own content and position rather than accepting one generic assistant as authoritative for every church
- Sources can remain visible - retrieval-grounded answers can cite the ministry’s underlying data instead of producing unsupported prose alone
- Multiple model providers reduce single-vendor lock-in - current routing can use model families from five providers with documented failover
✗ Watch out
- The Faith Assistant product identity has effectively disappeared - its domain redirects, current navigation does not name it, and no dedicated current onboarding or price page exists
- The promised free church version is not verifiable - a 2025 announcement said it would launch, but the 2026 Gloo+ and AI pages do not expose the same offer
- Gloo AI Studio is infrastructure, not a finished church website chatbot - a ministry may need developers, design, content operations, testing, and an enterprise engagement to recreate the original experience
- Pro is not a flat $25 service - model tokens are billed in addition, and transcription, storage, integrations, implementation, and high-volume use can change the total materially
- AI terms put substantial responsibility on the customer - organizations remain responsible for prompts, permissions, outputs, actions, integrations, legal compliance, and human oversight
- A grounded answer can still be wrong - retrieval may select the wrong sermon, omit context, mix versions, misquote Scripture, follow injected instructions, or confidently synthesize a position the source never taught
- Conversation analytics are pastorally sensitive - topic clusters about grief, marriage, sexuality, health, doubt, abuse, giving, or crisis can become profiling if consent, access, retention, and use are not tightly governed
- No current public assistant-specific accessibility proof - keyboard operation, screen readers, language switching, captions, crisis presentation, and embedded-widget behavior require testing
- Continuity follows a fast-changing platform - Gloo may change models, connectors, plans, limits, and free offerings, and its terms say third-party providers can change without notice
Best for
- Large ministries, publishers, and networks with a deep owned-content corpus and staff to govern a public AI experience
- Organizations that can negotiate a written enterprise scope, DPA, retention rules, support, analytics access, escalation design, and model evaluation
- Developers building a custom cited assistant through Gloo AI Studio rather than expecting a one-click legacy Faith Assistant installation
- Churches willing to define answer boundaries, review source material, test high-risk topics, and keep named humans responsible for every ministry outcome
- Content owners seeking conversational discovery of paywalled or difficult-to-search archives with links back to canonical resources
Avoid if
- You are expecting the old free Faith Assistant tier described in the January 2025 announcement without written confirmation that it still exists
- Your church has no content owner, privacy lead, safeguarding process, escalation roster, or technical person to maintain the assistant
- You want AI to provide autonomous pastoral counseling, crisis care, doctrinal rulings, medical advice, legal advice, or discipline decisions
- You cannot lawfully upload sermons, books, member messages, counseling notes, copyrighted media, or personal information to a cloud AI platform
- You need a predictable all-inclusive price before estimating traffic, model tokens, transcription, storage, integrations, support, and implementation
What Faith Assistant is
Faith Assistant was a retrieval-grounded public chatbot for a ministry’s audience. A church or publisher supplied content and parameters; a visitor asked a natural-language question; the system retrieved relevant material, generated a conversational answer, recommended resources, and could route the person toward a human. Custom colors, fonts, language, and organizational framing made the assistant feel like part of the ministry rather than a link to a generic consumer AI.
That architecture is useful when a large archive has a discovery problem. A listener may remember that a pastor addressed grief but not the sermon date. A subscriber may need one paragraph from a long compliance library. A visitor may ask what the church believes, when an event begins, or how to request prayer. Retrieval can turn a search task into a conversation and expose content that ordinary menus bury. It should not imply that the generated response itself carries the authority of the ministry; the cited original remains authoritative.
The current Gloo platform separates ingredients that the old brand bundled: model access, safety policy, content ingestion, search, grounded generation, agents, tools, analytics, and enterprise controls. That separation is powerful for developers and potentially confusing for a small church. Before comparing prices, define whether you need an internal staff copilot, a public website assistant, an archive search box, a member-support workflow, or an autonomous agent. They have different risks, data flows, and implementation costs.
Why the Faith Assistant idea matters: ministry content becomes conversational without surrendering the source
Generic chatbots know almost nothing about a particular congregation. They may invent service times, flatten a statement of faith, quote a different Bible translation, recommend resources the church does not use, or speak confidently about local care. Faith Assistant’s organizing insight was that the ministry should control the corpus and deployment. Current Gloo Data Engine capabilities extend that idea with structured ingestion, metadata, semantic search, and grounded completions that can cite the actual materials selected.
Control of the corpus is necessary, not sufficient. Old sermons contain outdated announcements and may preserve mistakes; a speaker’s illustration may not be policy; a transcript can mishear Scripture; two teachers may disagree; and a retrieved paragraph may lose the caveat on the next page. Build a canonical source hierarchy, version and expire content, separate doctrine from personal opinion, label public versus internal material, require citations, make “I don’t know” normal, and send people to humans early. Alignment is an editorial and pastoral operation, not a switch in a model.
Content ingestion and grounded answers: the strongest capability and the largest hidden job
Gloo AI Studio Pro can ingest websites and sitemaps, files, YouTube channels, RSS or podcast feeds, PDFs, documents, audio, and video; organize them in a content library; edit metadata; search semantically; and produce a response grounded in retrieved data. An organization can use source links or footnotes to let readers inspect the supporting item. This is the technical core that made Faith Assistant more useful than a generic prompt preamble.
A content dump is not a knowledge base. Assign owners, obtain rights, correct transcripts, identify speakers, tag dates and audiences, expire event information, distinguish published doctrine from draft notes, remove confidential records, and define which versions can answer which users. Test retrieval separately from generation: did the right source appear, was the relevant passage complete, and did the answer preserve its meaning? A fluent answer grounded in a stale or misclassified document is still failure.
Customization, analytics, and human handoff: useful engagement data with surveillance risk
The legacy product emphasized a branded assistant, organization-specific theological alignment, resource recommendations, anonymized topic clusters, trends, and connection to staff or volunteers. For a large publisher, question patterns can reveal where navigation or content is weak. For a church, a clear handoff can turn an after-hours informational exchange into prayer, practical support, or a real conversation during staffed hours.
Design consent before collecting insight. Tell visitors they are speaking with AI, what is logged, who can read it, how long it remains, whether the church receives identifiable transcripts, and when a human is contacted. Do not infer spiritual condition or donor value, target vulnerable people, rank pastoral need from sentiment, or merge sensitive questions into a profile without lawful basis. Give users a private no-analytics route and staff a handoff queue with boundaries, safeguarding training, and realistic response times.
Models, agents, and safety controls: more capable than the legacy chatbot and more consequential
The current platform offers more than fifty models, automatic or direct selection, four-tier provider failover, screening across thirty content categories, streaming, function calls, agents, chains, artifacts, web access, files, commands, and external connections. Enterprise accounts can add role controls and activity logs. These capabilities can support a simple question-answer tool, an internal content workflow, or agents that act across other systems.
Every added action widens the failure surface. Gloo’s terms appropriately warn that AI can be inaccurate, unexpected, and capable of irreversible real-world actions, and place human oversight on the customer. Keep a public information bot read-only. Do not let it send messages, change records, transact, schedule care, or access member databases without narrow scopes, authenticated users, confirmation, logs, rate limits, rollback, and incident drills. “Values-aligned” does not neutralize prompt injection, compromised sources, or mistaken tool calls.
Pricing
Legacy promised free church tier
Not currently verifiable
Gloo’s January 2025 acquisition release said a free version would launch, trained on a church’s sermons and content. The legacy domain now redirects, and the current public product and Gloo+ pages do not provide a matching signup or limits. Do not budget around it without written confirmation.
Gloo AI Studio Free
Free playground only
The current documentation allows 50 playground chat messages every five hours. It does not include API access, the Data Engine, or a deployable Faith Assistant for a church website, so it is useful for evaluation rather than a replacement for the promised legacy free product.
Gloo AI Studio Pay As You Go
Per-token usage, billed weekly
Public production API access with 50+ models, playground, auto-routing, safety layer, streaming, tool calling, provider failover, OpenAI SDK compatibility, spend controls, and email support. It does not include the Data Engine needed to ingest a ministry corpus.
Gloo AI Studio Pro
$25/month + token usage
Adds website, file, YouTube, feed, and large-media ingestion; content library; search API; grounded completions; metadata and bulk tools; agents and chains; ingestion analytics; and priority support. This is the clearest public successor starting point for a developer-built assistant.
Gloo AI Studio Enterprise
Custom quote
Adds recommendations, role-based administration, activity logs, broader analytics, custom token pricing, invoicing and service agreement, shared support channel, and private transcription as a paid add-on. A full public-facing custom assistant may require this tier plus implementation services.
Gloo+
$49/month or $499.80/year
Current Gloo+ benefits center on communications, groups, workflows, insights, and an AI Writing Assistant. Although the 2025 acquisition release associated advanced Faith Assistant features with Gloo+, the current benefits table does not name them. Treat these as different products unless Gloo confirms otherwise.
The directory-level summary “free tier plus Gloo+” is no longer a safe buying statement. It describes an announced 2025 plan. The old domain now redirects, and current Gloo+ documentation does not list the assistant. Ask Gloo to identify the exact current SKU and provide its limits in writing.
Gloo AI Studio separately offers a rate-limited free chat playground—currently 50 messages every five hours—but it has no API, Data Engine, or public website assistant. It is a useful evaluation path, not evidence that the legacy free church product is available.
Gloo AI Studio Pro’s $25 base price is unusually approachable for content infrastructure, but it is only the platform fee. Model usage remains metered; audio or video ingestion, transcription, storage, traffic, developers, interface hosting, support, and enterprise controls may dominate the budget.
Build a representative traffic model: monthly conversations, messages per conversation, retrieved context size, response length, model route, re-indexing, audio hours, failed queries, evaluation calls, and abuse. Set spend caps and alerts, then test a pilot corpus before promising 24/7 availability.
Enterprise buyers should put retention, subprocessors, model-provider flow, geographic processing, security evidence, incident notice, support, uptime, content deletion, export, accessibility, evaluation, and service exit in the order and DPA. A broad public terms page cannot replace a specific deployment contract.
Price the human system. Someone must approve content, review failed and high-risk answers, answer escalations, retrain staff, manage disclosures, update events, investigate complaints, and communicate incidents. AI may reduce repeated search; it does not eliminate pastoral or editorial labor.
Where Faith Assistant falls behind
Product continuity. Publish a current Faith Assistant page that plainly states whether the name, widget, free plan, Gloo+ benefit, and enterprise service still exist or have been replaced.
Turnkey pricing. Show setup, subscription, model usage, transcription, storage, conversation limits, integrations, support, overages, annual commitment, trial, cancellation, and export costs for a normal church.
Live demonstrations. Offer a safe public sandbox with visible sources, uncertainty, refusal, correction, human handoff, multilingual behavior, and a versioned sample corpus.
Assistant evaluation. Publish results for source retrieval, biblical quotation, citation entailment, doctrinal boundary adherence, stale events, prompt injection, self-harm, abuse, medical and legal requests, privacy leakage, and adversarial content.
Pastoral safety templates. Provide configurable crisis and safeguarding flows, no-emergency disclaimers, human response windows, escalation training, audit, and guidance for minors and mandated reporters.
End-user disclosure controls. Give each deploying ministry plain-language templates for AI identity, conversation logging, analytics, identifiable handoff, retention, deletion, consent, and accessibility.
Accessibility evidence. Test embedded widgets with keyboard, screen readers, zoom, reflow, contrast, status announcements, language direction, timeouts, captions, and human-contact alternatives.
Migration and exit. Document content export, embeddings and derived-data deletion, transcript portability, custom widget removal, domain continuity, and what happens when a model, integration, or free tier ends.
Faith Assistant vs. Doctrinally.AI vs. AskMyChurch vs. a staffed search page
Doctrinally.AI is the closest conceptual comparison: a ministry trains a public assistant on approved materials and embeds it for questions. Its public product presentation is currently more explicit about the assistant-shaped outcome, while Gloo’s successor platform is broader, more technical, and better suited to enterprise integration. Compare source citations, theological configuration, escalation, analytics, contract terms, traffic pricing, and actual red-team results—not the word “aligned.”
AskMyChurch focuses on the practical church-information problem: help people find local answers and connect without making every exchange a theological synthesis. That narrower scope may be safer and easier for a congregation whose most common questions concern times, groups, events, children, giving, and next steps. Faith Assistant/Gloo is stronger when a large content archive and custom AI strategy justify more infrastructure.
A well-built search and contact page remains the honest baseline. Curated beliefs, service times, staff contacts, care pathways, FAQs, and full-text search are deterministic, accessible, inexpensive, and easy to correct. They do not converse or surface obscure content as gracefully, but they also do not hallucinate. Add AI only when measured discovery gains exceed the extra privacy, safety, editorial, accessibility, and continuity burden.
The bottom line
Faith Assistant deserves credit for seeing the right problem early. Ministries possess years of valuable teaching but expose it through menus, titles, and search boxes that assume users already know what to request. A grounded conversational layer can make that archive reachable and connect a question to a person. Gloo’s acquisition adds real platform depth. But buyers should not confuse the strength of the idea with continuity of the old product. The branded domain now resolves to Gloo AI, the free tier announced in 2025 is not plainly available, and the current route ranges from a $25-plus-usage developer plan to custom enterprise work. Define the exact experience, begin with a small canonical corpus and low-risk questions, demand sources and uncertainty, keep the bot read-only, disclose logging, staff the handoff, and test the failures that could harm a person—not just the demos that delight a board.
Alternatives to Faith Assistant
Doctrinally.AIA dedicated ministry-content assistant proposition; compare current citations, corpus controls, escalation, pricing, privacy, and measured accuracy.
AskMyChurchA church-focused answer and connection layer suited to local information and next steps, with a narrower job than a full AI platform.Gloo Ministry ChatGloo’s current internal church-team assistant for writing and workflows rather than the legacy public-facing Faith Assistant widget.Gloo AI StudioThe current developer platform beneath grounded content, agents, model routing, safety, and enterprise controls; powerful but not turnkey.Curated search and human contactA deterministic knowledge base with clear staff pathways is often safer, cheaper, more accessible, and easier to keep current.Frequently asked questions
Does Faith Assistant still exist?
The technology and team were acquired and integrated into Gloo, but the standalone brand no longer has a current product page: faithassistant.com redirects to Gloo AI. Ask Gloo which current product or service replaces the legacy assistant for your use case.
Is Faith Assistant free for churches?
A January 2025 announcement said a free church version would launch. We could not find a matching current signup or limits in August 2026, and current Gloo+ benefits do not name Faith Assistant. Obtain written confirmation before relying on that promise.
How much does the current Gloo AI platform cost?
Gloo AI Studio has a free, rate-limited chat playground; metered Pay As You Go unlocks API access; Pro costs $25 per month plus token usage and adds content ingestion and grounded responses; Enterprise is custom. A finished public assistant may involve additional implementation and services.
Can it answer from our sermons?
That is the core use case. Current Data Engine tools can ingest websites, files, YouTube, feeds, audio, and video and generate grounded completions. You still need rights, corrected transcripts, metadata, versioning, content boundaries, and evaluation.
Does Gloo use church content to train AI models?
Current services terms say Gloo will not use non-prompt customer content or private configurations to train models unless the customer expressly opts in in writing. Review the DPA, order, prompt handling, subprocessors, and retention for your specific deployment.
Can Faith Assistant replace pastoral staff?
No. It can answer repetitive informational questions and surface resources. It cannot safely own crisis response, counseling, spiritual discernment, safeguarding, diagnosis, doctrine, discipline, or relational care. Provide visible and staffed human routes.
What should a church test before launch?
Test retrieval and citations, Scripture quotation, disputed doctrine, stale information, privacy leakage, prompt injection, abuse and self-harm language, medical and legal requests, accessibility, multilingual behavior, handoff, logs, costs, outages, and deletion.
Sources & further reading
- Gloo acquisition announcement for Faith Assistant ↗
- Current Gloo AI overview ↗
- Current Gloo AI Studio plans ↗
- Gloo AI Assistants documentation ↗
- Gloo AI Studio billing and plan documentation ↗
- Gloo services terms, including AI assistants ↗
- Gloo AI Studio supplemental terms ↗
- Gloo privacy statement ↗
- Current Gloo+ membership details ↗
More AI Bible & Faith Tools
Magisterium AIA chatbot that refuses to answer Catholic questions from the open internet - and instead pulls every claim from 25,000+ Magisterial documents with citations.
BiblosOne of the clearest free demonstrations of meaning-based Bible search, now paired with substantial daily-reading tools—but semantic relevance is not interpretation, and the live service lacks the privacy and methodology pages needed for unqualified trust.
Church.tech (now Gloo Content Studio)The former Church.tech has become Gloo Content Studio, a capable sermon-repurposing workspace for clips, transcripts, devotionals, posts, podcasts, and publishing—with useful ministry context, two conflicting official price tables, and AI output that still needs pastoral review.
AnorA white-glove intelligence layer that connects a church or nonprofit’s existing email, giving, event, and commerce systems, resolves constituent identities, and answers cross-system questions—powerful for organizations with fragmented data, but costly and governance-heavy because the “complete picture” is sensitive by design.AskMyChurchA church-trained AI assistant with unusually thoughtful citations, anonymous questions, pastoral boundaries and crisis routing—stronger than a generic chatbot, yet paired with absolute accuracy claims and incomplete retention, vendor and compliance detail.
Bible BotA carefully instructed Christian companion inside ChatGPT, with unusually candid limits and pastoral safety rules—but still a probabilistic AI whose model, privacy, memory, and access belong to OpenAI’s platform.