Appearance
Heritage Community Hub — Leadership Briefing ​
For Core Ministry LeadershipStatus: Active Development · All features subject to change based on ministry feedback
"And let us consider how we may spur one another on toward love and good deeds, not giving up meeting together, as some are in the habit of doing, but encouraging one another — and all the more as you see the Day approaching." — Hebrews 10:24–25
Vision and Purpose ​
Heritage Virginia Community in Nickelsville, VA is establishing a digital platform to serve our faith-centered community of approximately 200+ members. As an agrarian Christian community, we hold that a measure of separation between technology and the world is necessary to protect the life we are called to. At the same time, we recognize that complete withdrawal from technology is neither realistic nor required of us. Used deliberately and within the right guardrails, technology can serve as a tool for good — strengthening our fellowship, stewarding our shared work, and keeping our community connected without surrendering our values to the broader culture.
This platform is being built in that spirit: not as an embrace of the digital world for its own sake, but as a carefully bounded instrument that supports our community's needs while upholding our Christian convictions and maintaining appropriate access controls for all members. This is not a social media platform. It is not a business tool. It is a protected space that belongs entirely to Heritage Virginia — one place where our community can coordinate, stay connected, and care for one another. Every decision about who can join, what they can see, and how they communicate is made by ministry leadership, not by an algorithm or outside company.
The platform lives at heritageva.app. It works in any web browser today. Native iPhone and Android apps are planned as the platform matures.
What the Platform Does ​
One platform, available on the web today and as a mobile app in the future, covering every area of community life. The platform is live now at heritageva.app.
Members sign in with their existing Apple or Google account — no new password to create. Each member has a profile with their name, birthday, wedding anniversary, address, phone, email, gender, and baptized designation. Families are connected as a unit: spouses are invited by email, and children are added as sub-accounts with a parent-set PIN — no email address required for children.
The platform can be installed directly from the browser on an iPhone, Android phone, or Windows desktop (via Microsoft Edge) — choose "Add to Home Screen" or "Install App" and it behaves like a regular app, without waiting for an app store. A dedicated iPhone app and Android app are planned for a future phase and will use the same accounts, data, and content.
Administrator and minister tools are live: a full member list with approval and CSV export, an audit log of every action taken in the platform, a platform status dashboard, and a minister oversight page with baptized indicator for pastoral care.
The platform is designed so that Sermons and Music could eventually be offered as a standalone app built on the same foundation — a separate product that members of any community could use to access Heritage Virginia's media library, while the community hub itself remains members-only.
Access, Security, and Membership Control ​
This is the most important part of the platform, and it was designed with ministry leadership in full control.
This is a closed community ​
There is no open registration. No one can browse Heritage Virginia's platform from the outside. Every person who joins goes through a human approval process run by ministry leadership. That is a design decision, not a setting that can accidentally be turned off.
How membership works ​
- A person requests access.
- A minister or administrator reviews the request, confirms the person is a real community member, and approves them.
- Once approved, a Family Group is created for their household.
- Spouses are added by the member and approved separately by leadership before they gain access.
- Children are added as sub-accounts within the family group by the parent — no email address required for children, no independent logins. Each child signs in with a parent-set PIN. The parent controls what the child can access.
Community leaders — Administrator and Minister (Full leadership access) ​
- Complete system oversight and configuration
- Member management, family-group creation, and invitation controls
- Approval authority — verify and approve new members, spouses, and all submitted content
- Access to sensitive member data, approval workflows, and the full audit log
- All community feature administration
Note: Administrator and Minister are two distinct roles at this level. An Administrator holds full system control — member approval, audit log, platform diagnostics, and configuration. A Minister holds pastoral care access — member records, family groups, and baptized status — but not system administration. These two roles exist because the person who cares for a member's soul and the person who manages the platform are not always the same person, and they should not carry the same keys.
Ministry leaders ​
- Manage their specific ministry area and the members within it
- Access to members within their ministry
- Event creation and coordination for their ministry
- Ministry-specific communication and announcements
Small group leaders ​
- Manage their assigned small groups
- Group member communication and coordination
- Small group event planning and management
- Access to group-specific resources
Community members (standard access) ​
- Participate in community events and activities
- Access the community calendar and RSVP for events
- Browse and post to the members-only marketplace listings
- Receive announcements and standard messaging features
- Manage their own family group (add a spouse or children, subject to approval)
Prospective members and visitors (limited, approval-gated) ​
- Request access to join the community
- See only the minimal information needed to begin that request
- No open public browsing — this is a closed community; a minister verifies and approves every member before access is granted
Family groups and approval — how membership works ​
Heritage is a closed, member-only community — a family, not just a church — where everyone is known and vetted. Minister and Administrator approval gates everything.
- Request → Verify → Approve. A prospective member requests access; a minister confirms they are a real community member, approves them, and creates their Family Group.
- Spouses are added by the member through the family area, then approved separately by a minister; each adult signs in with their own Apple or Google account.
- Children are added as sub-accounts within the family group. The platform deliberately supports accounts that are not tied to Apple or Google — each child signs in with a parent-managed PIN instead of an email or social login. A child's access is scoped to the areas the parent approves.
- All members of a household share one Family Group, giving leadership a clear, trustworthy picture of who belongs.
Homeschool portal access (same platform, dedicated area) ​
The homeschool portal is not a separate system — it is the same platform and the same accounts, presented with education-specific roles and features.
Homeschool Administrator ​
- Overall homeschool program oversight
- Curriculum planning and teacher coordination
- Compliance and reporting responsibilities
Parents (primary account holders) ​
- Manage all their children's accounts — students cannot self-register
- Monitor academic progress across all children
- Communicate with teachers and administrators
Teachers (community members teaching classes) ​
- Class management and curriculum delivery
- Grade and assignment management
- Student progress reporting
Students (parent-controlled access) ​
- Cannot create their own accounts — managed entirely by parents
- Access to educational resources and assignments
- Participate in classes with limited, parent-supervised communication
Marketplace access (member-only listings) ​
The marketplace is a members-only directory of listings for mutual support — connecting members' farms, trades, and small enterprises. No payments or transactions are processed through the platform; members arrange everything between themselves. This keeps the marketplace simple, safe, and aligned with our values.
Marketplace Steward ​
- Oversee listings and posting guidelines
- Approve members who wish to offer goods or services
- Help resolve concerns and keep listings consistent with community values
Members offering goods or services ​
- Create and manage listings for products, produce, or services
- Communicate with interested members directly — no payment handled in-platform
- Optionally connect with the community delivery network (future Pony Express)
Members browsing listings ​
- Browse listings from fellow community members
- Reach out directly to arrange a purchase or trade
- Leave respectful feedback that helps the community support one another
Role assignment ​
Every role — pastor, elder, deacon, minister, ministry leader, small group leader, homeschool administrator, and all others — is assigned by an administrator. There are thirteen defined roles in total. No member can grant themselves a role or elevate their own access.
Roadmap — What Comes Next ​
This is the planned order. Nothing here has a firm date. Each item is built, tested with ministry leadership, and released when it is ready.
| Step | What it is | Notes |
|---|---|---|
| ✅ Platform Foundation | Accounts, profiles, family groups, admin and minister tools | Released June 25, 2026 |
| Sermons and Music | Watch sermons, listen to music and worship — on demand and live stream; downloadable for offline listening | Could also become a standalone app on the same foundation |
| Community Calendar | Everything happening at Heritage in one place — services, work days, gatherings, special events. RSVP and check-in. | The primary reason most members will use the platform daily |
| Announcements and Messaging | One-way broadcasts from leadership to the whole congregation or specific groups. Email, SMS, and in-app. No reply threads or open comment sections. | |
| iPhone App | Native app in the App Store — same accounts, same content, push notifications, offline access | Requires Apple Developer Program ($99/year) |
| Homeschool Portal | Parent-managed student accounts, courses, grades, and teacher tools — purpose-built for Heritage homeschool families | |
| Community Marketplace | Members-only listings of farms, trades, and services. No payments handled in-platform — just connecting members. | |
| Android App | Same experience as iPhone, built for Android phones | |
| Pony Express | Coordinating local deliveries and errands among members already traveling | Future |
| Ride Share and Travel | Carpools, travel coordination, and cost-sharing for church events and longer trips | Future |
| Sister Communities | Connecting with other Heritage communities on the same platform | Future |
Investment and Technology Costs ​
All costs below are estimates. Actual costs vary with usage and platform growth.
Current setup — Microsoft Azure ​
Azure is where the platform runs today. Costs are broken down by service so leadership can see exactly what each piece does.
| Service | What it does | Monthly | Annual |
|---|---|---|---|
| Azure Static Web Apps | Hosts and delivers the website to members' browsers | $9 | $108 |
| Azure Container Apps | Runs the application's backend — the engine that powers everything | ~$10 | ~$120 |
| Azure Database (PostgreSQL) | Stores all member data, family records, and community information | ~$13 | ~$156 |
| Azure Container Registry | Stores the software packages the app is built from | $5 | $60 |
| Azure Storage | Media files, backups, and uploaded content | ~$2 | ~$24 |
| Azure Key Vault | Secure storage for credentials and system secrets | <$1 | <$12 |
| Azure App Insights | Error monitoring — lets the team catch problems before members notice | $0 | $0 |
| Azure subtotal | ~$40 | ~$480 |
| Other Service | What it does | Monthly | Annual |
|---|---|---|---|
| Cloudflare | DNS, content delivery, DDoS protection, free SSL certificates for all subdomains | $0 | $0 |
| Clerk | Secure sign-in with Apple and Google accounts (free up to 50,000 users; see note) | $0 | $0 |
| Twilio (SMS) | Text message notifications sent to members | ~$9 | ~$108 |
| Apple Developer Program | Required to publish the iPhone app to the App Store | $8.25 | $99 |
| Domain (heritageva.app) | Annual domain registration | $1.25 | $15 |
| Total — without nonprofit credits | ~$58/month | ~$702/year |
Microsoft Nonprofits grant: Microsoft offers up to $3,500/year in Azure credits to qualifying nonprofits. If Heritage Virginia applies and is approved, the entire Azure portion ($480/year) would be covered at no cost.
Net annual cost with Microsoft nonprofit credits: approximately $222/year (~$18.50/month) — covering only SMS, Apple Developer, and the domain.
Clerk — production note: Clerk's free plan supports up to 50,000 monthly active users, which far exceeds Heritage Virginia's current size. Apple and Google sign-in are included at no cost on the free plan. However, two features cost money if we want them:
- Multi-factor authentication (MFA) — an extra security step for admin and minister accounts requiring a code in addition to their Apple/Google login. This requires the Clerk Pro plan at $25/month ($300/year).
- Custom authentication domain — so the sign-in screen shows heritageva.app rather than Clerk's own URL. This adds $10/month ($120/year) on top of Pro.
At 200 members there is no per-user charge on any tier. The honest assessment: Apple and Google sign-in are secure on their own, and MFA is an additional layer of protection primarily worth considering for admin accounts. Whether that is worth $25/month is a leadership decision.
What it would cost on Google Cloud Platform (GCP) ​
GCP offers a nearly identical architecture. Hosting costs would be similar — roughly $35–50/month for the same services.
Google for Nonprofits offers $10,000/year in Google Cloud credits to qualifying nonprofit organizations. That is more than enough to cover Heritage Virginia's hosting costs entirely, with significant credit to spare. To apply, Heritage Virginia would need to register through the Google for Nonprofits portal; verification typically runs through TechSoup or a local equivalent and takes a few business days.
However, Google is one of the major technology providers the community has discussed evaluating for values alignment. That is a leadership decision, not a technical one.
Estimated annual cost with Google nonprofit credits: $0 for hosting. The same non-hosting costs (~$222/year for SMS, Apple Developer, and domain) would still apply.
What it would cost on Amazon Web Services (AWS) ​
AWS offers comparable services at comparable pricing — roughly $35–50/month. AWS pricing tends to be slightly higher for database and storage at scale.
AWS Nonprofit Credit Program offers $1,000–$5,000/year in AWS credits to qualifying nonprofits, applied through TechSoup. The amount is tiered by the organization's annual operating budget — smaller organizations receive $1,000/year, larger ones up to $5,000/year. Credits are renewed annually and are valid for at least one year. Heritage Virginia's hosting costs (~$480/year) would fall within the $1,000 tier, meaning AWS credits would likely cover hosting entirely.
AWS also runs an Imagine Grant Program for nonprofits offering up to $200,000 in cash plus additional AWS credits — though that is oriented toward larger projects with a formal application process.
Estimated annual cost with AWS nonprofit credits: $0 for hosting. The same non-hosting costs (~$222/year) would still apply.
What it would cost to host it ourselves ​
Self-hosting means running the platform on hardware owned and managed by Heritage Virginia — in a home, church building, or rented server rack.
One-time hardware cost: $300–600 for a suitable mini PC or small server, plus external drives for backups.
Ongoing costs:
- Business internet with a static IP address: $50–100/month above residential cost (most home internet providers do not allow running servers)
- Electricity: ~$5–10/month
- Domain and SSL certificates: ~$15/year (SSL is free with Let's Encrypt, but requires setup and renewal management)
- Estimated monthly: $55–110/month ongoing
What it requires: Someone in the community with Linux server administration skills, available to respond to hardware failures, power outages, and security issues at any time. No automatic failover — if the power goes out or the hardware fails, the platform goes offline until someone fixes it. Backups must be managed manually and tested regularly.
The honest assessment: Self-hosting provides complete data ownership and no dependency on outside companies. It is the right long-term direction for a community that values independence. However, it requires a level of on-site technical expertise and infrastructure that Heritage Virginia does not currently have in place. It is worth keeping in mind as a future option as the community grows.
Spiritual and Community Alignment ​
- All platform features are designed to strengthen fellowship and serve our community's shared life — not to replace face-to-face relationship.
- Content and communication guidelines reflect Biblical values. The platform has no open comment sections, no social feeds, and no mechanisms for conflict to spread.
- Privacy and security measures protect family and community information. Member data belongs to Heritage Virginia, not to any technology company.
- Parental authority is built into the design — children cannot create accounts, cannot set their own credentials, and cannot access areas their parents have not approved.
- Technology serves the community. The platform is a tool in the hands of ministry leadership, not an autonomous system making its own decisions.
Next Steps and Ministry Input ​
This platform is in active development. Everything here — features, priorities, cost decisions, role structures, and roadmap order — is subject to change based on the direction of ministry leadership.
Brother Evan, Brother John, Brother Ben, Brother Billy, and Brother Mike Deal are invited to provide feedback on anything in this document. Their input shapes what gets built next, what gets changed, and what gets dropped entirely. No feature is locked in until leadership says it is right for Heritage Virginia.
Immediate questions for leadership:
- Does the membership approval process described here match how leadership wants it to work in practice?
- Is the admin / minister role split the right division, or does it need to be adjusted?
- What is the priority order for the roadmap — does Sermons and Music come before Calendar, or the other way around?
- Are there features on the list that should be removed or reprioritized?
- On the hosting question — does leadership want to pursue the Microsoft Nonprofits grant, or explore GCP or another direction?
- Any interest in pursuing self-hosting as a long-term goal?
Web app: heritageva.appPlatform status: Active development — Phase 1 (Platform Foundation) live as of June 25, 2026 Prepared by: Kristopher Turner, Heritage Community Hub Development Team This document is for ministry leadership only
"Unless the Lord builds the house, the builders labor in vain."— Psalm 127:1