🗂️For Executive Directors

The operations layer between membership and the bimah.

ShulCloud is the books. MyBimah is the people.

Membership systems handle dues, donations, accounting, billing — the financial-transactional layer. They don't handle pastoral care, lifecycle workflows, facilities maintenance, the transparent backlog of congregant requests, or the relationship layer that makes a synagogue feel like a community. MyBimah fills that gap. Deploy alongside your existing books-of-record system. No data migration. No replacement risk.

Pulse — the transparent backlog

Stop fielding the same five questions at kiddush every week. Congregants submit ideas, requests, questions, issues at /help (no login required). Staff triage in a workspace with proper state machine + audit trail. Public Project Board at /community shows what's shipping. Reports give you board-meeting metrics: volume, response times, SLA compliance, top categories.

  • Pastoral category auto-flags confidential — bypasses the public board
  • Email pipeline tenant-editable: ack, status-change, idle nudges
  • Reports: median response, median resolution, SLA-acked-in-2-business-days %, top categories
  • Daily idle-nudge cron — admins get a digest of stale tickets
Replace 5 inboxes, 3 voicemail boxes, and a suggestion box no one empties.

Lifecycle workflows in one workspace

Shivas, B'nei Mitzvah, weddings, funerals, brit milah, baby naming — every lifecycle moment with its own template, off-site logistics, family-facing communication, trained leader registry, RSVP forms. One-click 7-night shiva series. Address autocomplete. Per-service custom messaging.

  • 14 placeholder lifecycle templates seeded — extend per tenant
  • Address autocomplete: Mapbox / Google Places / OpenStreetMap fallback chain
  • Visibility tiers per service: Private / Community / Public
  • Tenant-editable email templates with variable substitution + send history
  • Visitor edit + cancel via tokenized links — no account required

Operations + Facilities (in development)

Facilities Maintenance + Building Access modules in active development. Track work orders, vendor relationships, key holders, security camera audits — the operational machinery that keeps the building running. Same workspace as everything else, same audit trail, same membership directory.

  • Facilities Maintenance: work orders, vendor catalog, asset registry
  • Building Access: keyholder roster, RFID + key audit log, contractor day-passes
  • Coming Soon — already in the navigation as Pipeline modules

Yahrzeit Memorial Board — replace your kiosk vendor

If you're paying Joltone or Wallplaques, you know what kind of software they ship. MyBimah's Yahrzeit Memorial Board is the modern replacement: warm bronze plaques, engraved gold names in Frank Ruhl Libre serif, today's yahrzeits highlighted, calm credits-roll of upcoming yahrzeits, photo + biography in the profile modal. Bulk import from your current vendor's CSV. Idempotent migration script.

  • AA migrated 2,608 plaques from a Joltone XLSX export in one script run
  • Multi-photo support per plaque, default photo enforced via partial unique index
  • Hebrew gematria date rendering
  • Public touchscreen URL on your tenant subdomain — lockable to a stationary display

Audit-quality data + admin tooling

Multi-tenant by design — tenant isolation enforced at every query via withTenant(). Audit log with append-only DB triggers — even compromised app users can't UPDATE / DELETE the trail. Sentry for runtime errors. Role-based permission tiering with view < edit < manage hierarchy. Platform admin portal at admin.mybimah.com (Ryan-only today, will be the path your IT staff uses tomorrow).

  • Audit log immutability: trigger-level rejection of UPDATE / DELETE / TRUNCATE on audit_log
  • Permission expansion: services.edit implies services.run_sage implies services.view at session-load
  • Sentry error reports tied to user / tenant / commit SHA
  • Per-tenant admin role auto-created at provisioning

ShulCloud, ShulSuite, Chaverware — works alongside

MyBimah does NOT try to be your books-of-record system. We don't process payments. We don't generate tax receipts. We work alongside what you have for membership + financials, and we do the operational + relational work better than any tool you've seen. Eventually integrations make the dual-system feel seamless; today, the dual-system is itself the value proposition.

  • Email-based member match for honors confirmations + ticket attribution
  • OAuth: Google + Microsoft SSO (works with your tenant's M365 / Workspace)
  • Resend for outbound, Postmark for inbound (configurable)
  • Cloudflare DNS, Vercel hosting, Neon Postgres — modern infrastructure stack

The work between membership system and bimah doesn't have a category yet. We're building it.

We're onboarding new launch-partner synagogues selectively while we mature the platform with our beta partner. Send a note and we'll set up a conversation.