Small groups with leaders
A member belongs to a group, the group has a leader, and the leader sees their own list and records attendance at the weekly meeting.
What gets built
Four things you could have working this week
Not a feature list. These are the apps people actually describe, and what the platform hands back when they do.
A calendar and announcements that arrive
Services, rehearsals, events and meetings in one calendar, with push to everyone or to one group. It is a notification, not a message that scrolls away.
Prayer requests and testimonies
A member submits one, chooses whether it is public or only for the leadership, and the team tracks what has been answered.
Giving with a history
Tithes and offerings by card, one-off or monthly, with a receipt for the giver and a monthly report for the treasurer.
Included
The parts nobody wants to build twice
Database, login, payments and publishing are part of the platform, not a list of services you go and wire up afterwards.
A real database, not a form dump
Every screen reads and writes models you can open, query and export. The data is a database of yours from the first minute, not a spreadsheet the app pretends to read.
Login for your own users
Email, magic link and Google sign-in, with roles and per-record ownership enforced by Postgres itself. A badly written screen cannot become a leak, because the database answers empty.
Payments that land in your account
Stripe, Pagar.me and Mercado Pago connect once. Card, Pix, boleto and subscriptions, with the card fields rendered by a hosted vault your app never touches.
Web, installable, and in the stores
One project published three ways: your own domain, an icon on the phone straight from the browser, and a signed binary submitted under your own store account.
Found in search, and by the models
Titles, metadata, sitemap, structured data and social images are generated with the app. Pages get found instead of only being linked.
React code you can take with you
Real React, edited line by line or by clicking the element on screen, exported as a ZIP or pushed to your GitHub. No lock-in you have to negotiate your way out of.
How it works
From a paragraph to a published app
Three steps, and the second one is the one people do not believe until they watch it.
Start here
A prompt you can paste right now
This is a complete first message, not a slogan. Paste it, change the nouns to yours, and you have an app to react to instead of a blank page.
Build an app for a church. Members sign up with name, contact, date of birth and the small group they belong to; groups have a leader, a day, a time and an address, and the leader sees only their own group and records attendance at each meeting; a calendar with services, rehearsals and events, and push announcements that can go to everyone or to one group; prayer requests submitted by members, with the option of public or leadership-only, and a marker for answered; tithes and offerings by card, one-off or monthly, with a receipt for the giver and reporting by period; an area with the week's announcements and schedule open to any visitor; and a leadership dashboard with members per group, average attendance, birthdays of the month and giving by period.
Ready to start from
Templates in this category
A template is a working app with data already in it. Open one, make it yours, publish it under your own account.
Questions
Frequently asked questions
Describe it. See it running. Publish it to the store.
Free to start, no credit card. You subscribe when you want your own domain without the badge or your app in the stores, and on the Builder plan you take the code with you if you ever want to.