One engine, 14 front doors

Everything the Hub does, in one place.

Each vertical site tells one kind of organization why. This page is the how: every capability, every door in and out, and what it costs. If you run a Hub, or you are deciding whether to, this is the long answer.

  • People connect by consent
  • They pick their interests
  • You send once
  • Everyone reachable is reached

What is the Blasts Hub?

The Blasts Hub is the console an organization uses to communicate through Blasts, a permission-based channel where every recipient chose to connect. The same engine runs behind a dedicated site for each kind of organization (churches, nonprofits, restaurants, gyms, schools, employers, cities and more): audiences people pick for themselves, two-way conversations, scheduled campaigns and journeys, an email leg for people not on Blasts yet, CSV and CRM imports, webhooks and Zapier, member and employee portals, and plain per-message pricing through BlastCredits.

Start with the first article: What the Hub is β†’

What a Hub does

The short version every vertical site gives is: your people connect once, choose what they care about, and one send reaches all of them. Here is the whole machine, and each card links to the full article in the Hub documentation.

Consent-first connections

Nobody is ever added to a list. A person connects through your enrollment code or a connection request, and the Hub detects the right path automatically: on Blasts already, they get a request in their app; not yet, they get your invitation email with the code. Invitations from lists are spread at up to 200 a day so they never look like cold mail.

Audiences people choose

Open audiences are published to your enrollment code as interests; each person picks theirs in their own Blasts app and can change them any time from their preferences page. You can group people inside an interest (a camp inside youth), and closed audiences for staff or leadership are yours to assign and never shown. Tags are preferences, never access.

Compose, campaigns, journeys

One Blast reaches everyone in an audience who can be reached. Schedule it, repeat it weekly, run a Content Series on the calendar, a Journey relative to each person, or an Event Campaign counting down. Rich text, images, up to three attachments, RSVP tallies, a test-to-yourself button, and optional administrator approval before a leader's Blast goes out.

Two-way conversations

Replies land in a shared inbox with lanes (including a confidential prayer lane where a prayer audience exists), "who is replying" presence for teams, per-person history, staff notes, and STOP/START handled automatically on every rail.

The email leg

People who prefer email still hear everything: each Blast is mirrored by email from your organization's own sending address (we provision the subdomain at activation), one by one or as a weekly digest. Email credits are separate and cheap: $10 for 2,500 up to $100 for 50,000, with a 20% bonus for verified organizations and 50 free to start.

Every way in

Enrollment code, QR code, a printable kit, one-person invitations, pasted lists and CSV import with cleaning (bad addresses, duplicates, dead domains) and a preview before anything is sent, plus one inbound webhook URL any form, CRM or Zapier can post a new person to.

Data in, data out

Signed webhooks tell your systems when someone connects, opts out or replies, and when a Blast goes out. A private Zapier app (available on request) wraps both directions. Named connectors per vertical, starting with Planning Center People for churches. A Reach funnel shows exactly where everyone stands: known, invited, requested, connected, by channel and by source.

Team and roles

Owners, admins, leaders limited to the audiences you grant, and read-only viewers. Everyone signs in as themselves; sending to everyone, changing roles and leaving ask for a passkey or phone confirmation. Members who sign in through Blasts can request Hub access, and nobody gets in until you approve.

Portals, households, birthdays, calendar

A members portal and an employees portal, each activatable and renameable, give people a place to manage their choices: Blasts or email, each update or a weekly digest, name and language. Group families so a mailing reaches one person per household. Members can share birthdays and anniversaries and the Hub sends your greeting at 9:00 local, once a year. Point the Hub at your public calendar and upcoming events appear on Home with one-click announcing.

External content and Flow

Automated producers (an alert engine, a publishing system) file content through signed HMAC ingest. Each item waits in a review queue rendered exactly as it would go out. A human approves it and explicitly publishes; ingest can never send on its own. Producer credentials are issued by BlastsHub staff today.

Ownership and safety

Sign-in by email code, passkey, or through Blasts itself, with step-up approval for dangerous actions. The organization owns everything: leaving takes one typed confirmation plus a step-up, revokes our authority, and emails the owner a complete JSON export. Recovery material is held sealed. No hostages, ever.

Read the Hub documentation 15 articles. Inside your Hub, Help covers the same ground in your vertical's own vocabulary.

Or explore the Hub in your vertical's terms:ChurchBlasts documentation β†’NonProfitBlasts documentation β†’DirectToEmployees documentation β†’LeagueBlasts documentation β†’RestaurantBlasts documentation β†’DirectToAttendees documentation β†’RetailBlasts documentation β†’FitnessBlasts documentation β†’DealerBlasts documentation β†’ResidentBlasts documentation β†’DirectToResidents documentation β†’DirectToParents documentation β†’DirectToMembers documentation β†’

One engine, a front door for every kind of organization

All 14 verticals below run the same Hub. Each site speaks its audience's language, and most have a permanent fictional demo organization whose site shows the whole system in the wild.

What it costs

The Hub is part of Blasts; there are no seats, tiers or contracts. Sending costs credits from BlastCredits.com: one Blasts credit per recipient per Blast, one email credit per email on the email leg. The Hub unlocks with your first credit purchase. Hub Pro, which adds Journeys and Event Campaigns, unlocks at $500 in cumulative purchases and stays unlocked.

Verification is separate from Hub Pro: a verified church or nonprofit receives bonus credits (20% on everyday and email packs), not Pro. Credits, refills and Hub Pro β†’

Questions

Do I need a technical person to run a Hub?

No. Setup is a guided wizard: connect your organization's Blasts account, name your audiences, invite your people (paste a list or upload a CSV), send your first Blast. The technical doors (webhooks, Zapier, connectors) are there when you want them, never required.

What does it cost?

The Hub itself is part of Blasts. Sending costs credits from BlastCredits.com: one Blasts credit per recipient per Blast, one email credit per email. The Hub unlocks with your first credit purchase; there are no seats, tiers or contracts. Hub Pro (Journeys and Event Campaigns) unlocks at $500 in cumulative purchases. Verified churches and nonprofits receive bonus credits, which is separate from Pro.

Can people really choose what they receive?

Yes, that is the core of it. Your open audiences are published as interests; each person picks theirs in their own Blasts app and can change them any time. Closed audiences (staff, leadership) are assigned by you and never shown.

What happens to people who are not on Blasts?

They still hear from you. The Hub invites each person the consent-first way, and anyone who prefers email receives every Blast by email, individually or as a weekly digest, sent from your own domain.

Can we leave?

Any time. Leaving revokes the Hub's authority to act for you, and a complete JSON export of everything you put in is emailed to the owner. Your Blasts account, connections and credits are untouched; they belong to you, not to the Hub.

Which organizations is this for?

There is a dedicated Hub front door for churches, nonprofits, restaurants, retail, fitness, dealerships, property managers, cities and local government, schools, associations, events, employers, leagues and publishers, with more coming. Same engine underneath; each speaks the language of its vertical.

Where is the documentation?

On this site, under /en/docs/: fifteen articles covering connections, audiences, sending, the email leg, conversations, campaigns, enrollment, roles, integrations, credits, ownership and Flow. Verticals whose front door is open also have the same documentation in their own terms, under /en/docs/for/ (churches and nonprofits today). Inside your Hub, Help shows the same articles next to the screen each one describes.