Why we're called Ezra
“And they set the priests in their divisions and the Levites in their courses, for the service of God at Jerusalem, as it is written in the Book of Moses.”
Ezra 6:18
Ezra 6 records one of the great mornings in Israel's story: the rebuilt temple is finished and dedicated. And the very next verse, before the celebration is even over, is about organization. Priests set in divisions. Levites arranged in courses. Rotations, teams, and order, so that the service of God would not depend on a burst of opening-day enthusiasm, but continue faithfully week after week.
That verse is the whole idea behind this product. A church's ministry is not carried by one heroic Sunday; it is carried by ordinary people serving in their turn, week in and week out: greeters, kids-ministry volunteers, sound techs, hospitality teams. Someone has to set the divisions and keep the courses. In most churches, that someone is drowning in spreadsheets, group texts, and last-minute phone calls.
Ezra exists to carry that load: filling serving gaps before Sunday, noticing when a volunteer is quietly burning out, making sure every guest is followed up with. It is the modern version of divisions and courses, so that leaders can spend their energy on people, not coordination.
Who's behind Ezra
Built by people who serve on Sundays
Ezra was founded by two people who are still doing the work: both co-founders serve at their local churches today, with more than twenty years of ministry experience between them. The unfilled roster on a Saturday night, the volunteer who said yes six weeks in a row and then disappeared, the first-time guest nobody called. None of that is hypothetical to us. We built the tool we kept wishing existed.
That background shapes how Ezra is built. Volunteer health signals exist because we've watched good people burn out. The AI proposes and a leader approves, always, because software should never send a message to your congregation that a human didn't sign off on. And nothing in Ezra ever scores anyone's faith, character, or spiritual maturity, because that is pastoral ground, and software doesn't belong on it.
What we hold ourselves to
Order in service of people
Structure isn't the goal; it's what makes room for ministry. Every feature answers one question: does this help real people serve and be served?
Support, never replace
Ezra assists with operations. Discernment, care, and pastoral judgment belong to leaders: the AI drafts and proposes, a human always decides.
Worthy of a church's trust
Churches hold sensitive stories about real people. Strict data isolation, role-based access, and a full audit trail aren't features to us; they're obligations.
Set the divisions. Keep the courses.
See what your church's operations look like with the coordination handled.