The rules of the house
- Noadvertising
- Nostrangers
- Nopublic feed
- Noletting yourself in
What is left is the people you actually know.
OneNect is for family and friends: your people, your plans, your moments. Anyone can sign up for it, and nobody can put themselves in your circle: somebody already inside has to let them in. Corp, Faith and Estate are the same app for a company, a congregation and a household, each joined by invitation from the organisation that runs one, and none of the three is meant to feel like the others.
One app, four ways
Every screen is live markup, rendered from a seeded demonstration tenant. Not a screenshot.
Status
What is built,
and what is not.
One app with three pillars is easy to write and slower to build. Rather than let four sections on this page imply that each one is a separate app in a store, which none of them is, here is the actual state, and it is the state a buyer should be told before a demonstration rather than during one.
OneNect for a company Built
The mobile app, the admin centre and the API exist and run. This is the product a company can be sold today. Both store records exist under the OneNect name, and neither listing has been submitted for review yet.
OneNect for a congregation In build
The engagement half already exists, because it is the same platform. Giving, the sermon library and the chosen vocabulary are the work that remains. No separate app binary yet.
OneNect, for family and friends In build
This is the app itself rather than a pillar on top of it. The feed, plans, contests and Code Red all exist on the platform. What remains is the removal of everything a household or a company needs and nobody else does, and a tally that can never be spent or transferred. No separate app binary yet.
OneNect for an estate In build
Approvals, the knowledge base and the calendar exist. The household shape on top of them is the work that remains, and the approval record is being built natively rather than inside a third party. No separate app binary yet.
Four things it would be easy to overclaim
- Per-tenant colours and logo
- Decided and scheduled, not shipped. The tenant configuration holds the fields and no file in the app reads them yet, so branding is set at build time today.
- The vocabulary
- Written down in the platform plan and used on this page. It is not yet enforced by the apps, so a screen can still say the wrong noun.
- Tenant separation
- Enforced on the write paths and on sign-in. A number of list endpoints are still being brought behind it, and until that finishes we do not claim it as complete.
- Shifts and rotas
- Not built, and not on this page. There is no shift model in the schema, so there is no shift screen to show you.
The vocabulary
Same feature.
Different word.
A church does not have colleagues and a household does not have a congregation. About forty nouns change per product, so a screen reads in the words the organisation already uses. This is the table, and it is documented rather than shipped: the apps do not enforce it yet.
| Concept | OneNect | Corp | Faith | Estate |
|---|---|---|---|---|
| A person | friend | colleague | member | member |
| A group | circle | department | ministry | team |
| A gathering | plans | event | service | engagement |
| A place | place | site | campus | residence |
| The feed | Moments | Engage | Community | Briefing |
| The directory | friends | org chart | congregation | the household |
Source: docs/ONENECT-PLATFORM-PLAN-2026-08-21.md, part 4.3.
Every capability
The whole surface,
in one table.
Each product page walks through four or five capabilities properly. This is all of them, including the ones a product deliberately does not get and why. Read down a column for one product, or across a row to see how one capability changes.
| Capability | OneNect | Corp | Faith | Estate |
|---|---|---|---|---|
| The feedPosts, photos, polls, comments, reporting and blocking | Moments | Engage | Community | Briefing |
| Recognition against a valuePraise filed against what the organisation says it stands for | No scoreboard | The Meridian Mark | Yes | Yes |
| Points and ways to earnA ledger, a streak, and a published list of what earns what | Tally only | Spendable | Spendable | Not used |
| Store and chargebackA catalogue charged back to a cost centre, or priced in points | Off | Meridian Supply | Off | Off |
| Groups and group chatFeed, chat, events and members, per group | One circle | Departments and clubs | Ministries | Teams |
| Gatherings and RSVPGuests, dietary needs, add to device calendar, public listings | Plans | Events | Services | Engagements |
| Move: steps and goalsThree separate consents, day and long-horizon goals, distance | Yes | Yes | Yes | Yes |
| Contests and boardsJoining is what puts a person on a board, leaving takes them off | Pacts | The Plant Challenge | Yes | Not used |
| Code RedHold to alert chosen contacts with a live location, and see who answers | Yes | Yes | Yes | Yes |
| Facility emergency alertSounds through silent and Focus, targeted by list or by radius | Never | Yes | A campus is a facility | Yes |
| Near miss reportingCategories and severities set per site, offline capable | Off | Yes | Yes | Off |
| Ingredient CheckScan a barcode against a person, a pet or a herd | Yes | Yes | Yes | Yes |
| GivingNamed funds, five giving methods, Gift Aid, an annual statement | Off | Volunteering instead | Four funds | Off |
| Volunteering and company matchLog hours, verify an EIN, and match time or a gift | Off | Yes | Yes | Off |
| Service desk ticketsDepartments and forms read from the desk the organisation already runs | Off | Yes | Yes | Household requests |
| Approvals against a thresholdApprove, ask for more information, or decline, with the record kept here | Off | Order approvals | Off | Household spend |
| Knowledge baseDocuments, and a natural-language question put to them | Off | Yes | Yes | Restricted entries |
| DirectoryWho is who, where they sit, and who they report to | Friends, not a chart | Org chart | Congregation | The household |
| Live translationWritten in one language, read in another, in place | Ten languages | Ten languages | Ten languages | Ten languages |
| SSO and provisioningSAML 2.0 against any IdP, SCIM 2.0 joiners and leavers, passkeys | Passkey or email link | Yes | Yes | Yes |
| Admin centreBranding, which modules are on, the home layout, roles and audiences | No admin at all | Yes | Yes | Delegated |
A filled dot: the product has itA grey dot: it is off, and whyScroll the table sideways
Access, and the record of it
Who got in,
and who was told.
Sign in with the identity people already have
SAML 2.0 against any identity provider, with a per-tenant entry point so a company's people land in their own tenant rather than in a shared front door. Passkeys for the device in somebody's hand, and a one-time email link for the people who have no work account at all.
Joiners and leavers come from the directory, not a spreadsheet
SCIM 2.0 provisioning creates the person, places them in a department, and deactivates them the moment the identity provider does. There is no separate offboarding step for somebody to forget on the day it matters.
Support access is a recorded act, not a shared password
An operator can open a support session as a named person, and that session is written down and then explicitly revoked. Nobody logs in as somebody else quietly, and there is no shared administrator account to rotate.
The administrative record is exportable
Every administrative action is written to an audit log that downloads as CSV, alongside a sign-out-everywhere control for the day that is needed. An emergency alert keeps its own delivery and acknowledgement records, so the question of who was reached has an answer.
- GET/auth/saml/meridian/login
the tenant's own front door - POST/auth/saml/meridian/callback
assertion verified, session minted ok - GET/auth/me
the person, and the tenant they are in ok - POST/scim/v2/Users
a joiner, created from the directory ok - PATCH/scim/v2/Users/41
active: false, access ends here ok - POST/admin/impersonate/12
support session opened, and recorded ok - POST/admin/impersonate/revoke
and explicitly ended ok - GET/admin/security/audit.csv
who did what, downloadable ok
Real endpoints, in the order they run. Tenant separation is enforced on the write paths and at sign-in; a number of list endpoints are still being brought behind it, and we do not claim it as finished until they are.
Talk to us
Pick the world
you are in.
Tell us which of the four you are, roughly how many people, and what you use today. We will show you the product with your own vocabulary in it, and tell you plainly which parts of it are finished.