Start here
- List the jobs your current website does, including giving, forms, ministries and media. Compare them with the working tools and gaps below.
- Preview your church on a phone. Test service times, directions, calling, events, recordings and a fictional inquiry; confirm an owner can follow up.
- Arrange a verified domain and operational backup/recovery process with support. Switch only after your essential tasks work and your team can manage them.
What to know
The private pilot supports a welcoming homepage, service times, published contact details, announcement scheduling, events with calendar downloads, searchable external sermon links, inquiry forms, owner follow-up, staff roles and three themes. Visitors can find events, messages and forms from the church navigation.
A saved address offers a Google Maps link; opening it shares that public address with Google. A standard phone number offers a call link. These links use the last published settings, so review and publish changes first. No map is embedded or loaded automatically. Before replacing a current website, check whether your church needs custom pages for beliefs, ministries or staff, image uploads, online giving, event registration, newsletter delivery, a member portal or automated full-site recovery.
Those are not implemented church features yet. Public purchases, production licensing, easy customer installation and self-service domain connection also remain launch gates. Operator-verified hostname mapping exists, but a church must arrange and test its domain before migration. Keep the old website and email service until every essential visitor task and staff sign-in has been verified.
Exports are not a full disaster-recovery system. ChapelOS is suitable for evaluating a simple church site in the pilot, not a promise to replace every existing website today.