The platform today

What is on the Presence+ Developer Platform today

The Network is a headless system of record: it holds identity, relationships, consent, measures and content, and leaves the front end to you. This page lists everything in it a developer can use now, by category, with a status on each item. Available means you can call it today. Beta means it works inside the Presence+ apps and is being opened to members. Planned means it is on the roadmap.

Updated 2 November 2026. Statuses move as the server team opens routes to outside applications.

Parish app Midst Campus app your code Counseling Mindspirit Formation courses Shell shell.presence.plus Companions Raphael Presence+ Network identity · roles · consent measures · hand-up api.presence.plus one record · many applications · every line is the API

Daily content

A reference library, refreshed every day

17,711 documents in 17 tables, verified, served to any application on the Network from the presenceplus-liturgical project. A ministry or formation app would otherwise have to license and maintain this itself.

  • Available

    Daily offices, modern

    The day's offices in the current form.

  • Available

    Daily offices, 1960

    The same days in the 1960 form.

  • Available

    Divine Office hours

    Each hour of the day, by date. divineoffice.org content, under license.

  • Available

    Daily readings

    The lectionary readings for the day, from the USCCB.

  • Available

    RC meditations

    Regnum Christi daily meditations, with written permission to re-serve the archive.

  • Available

    Saints and saint-day pages

    The saint of the day and a page for each.

  • Available

    Celebrations

    Feasts, solemnities and memorials by date.

  • Available

    Marian antiphons

    The antiphon for the season.

  • Available

    Rosary sets and mysteries

    Sets and mysteries by day.

  • Available

    Virtues

    The virtue reference.

  • Available

    Virtue stories

    Stories illustrating each virtue.

  • Available

    Bible studies

    Study units.

  • Available

    Verse assignments

    Verses assigned by day or by pathway step.

How the library stays current

A manager wakes every day to confirm that each feed imported. It archives what was served, for reuse later in the liturgical cycle, and falls back to the archive when a source cannot supply a day. It checks what is served against the romcal calendar and texts the team when a feed fails.

The Latin Mass propers and the Benedictine, Dominican and Greek Orthodox calendars are planned.

Identity

Sign in with Presence+

The identity server at api.presence.plus is a standard OpenID Connect issuer. It signs people into the shell, and every app on the Network uses it.

  • Available

    Discovery, authorization, token, userinfo, JWKS

    Standard OIDC endpoints. Any OIDC library works.

  • Available

    Authorization code with PKCE

    Confidential clients with a secret, and public clients with PKCE and no secret.

  • Available

    Scopes

    openid, profile, email, offline_access, memberships:read, community:member, courses:read, pathways:walk, home:read, devotions:pray, clinical:client.

  • Available

    Claims

    sub, name, email, email_verified, picture, and memberships: the organizations and the role in each.

  • Beta

    Client registration

    Done by the Presence+ team on request. The self-service console in the shell is being built.

  • Beta

    Sign in on admin tools

    The CMS at cms.presenceplus.org is wired for it, pending its client credentials.

The record

People, relationships, consent

The record is held in the Presence+ data store and reached through the REST API under /api/v1. Routes that touch PHI are open only to clients with a signed BAA. Items marked Beta work inside the Presence+ apps and are being confirmed for outside clients.

  • Beta

    People as records

    One record per person, with memberships in several communities.

  • Beta

    Roles on relationships

    Leads, member of, walks with, attends, married, kinship. The role sits on the edge, with a date.

  • Beta

    Households

    A household as a unit with its own history.

  • Beta

    Consent on the edge

    Visibility follows the relationship a note was written on, enforced on every call.

  • Beta

    Hand-up and step-down

    A hand-up to licensed care through STEP with the person's consent, and the step back down.

  • Beta

    COPPA age attestation and guardian consent

    Handled server-side and inherited by every app.

  • Planned

    The turn

    The first outgoing helping edge on a person who only had incoming ones, recorded as an event.

  • Beta

    Call list and "the lost one first"

    Who leads but is led by no one. Who has no recent note. Whom to call this week.

The data store

Where a ministry's data lives, and who sets the rules

An application may keep a ministry's data in the Presence+ data store instead of its own database. The store is optional. What it changes is who decides what happens with the information: the person being helped, the helper, and the ministry's leadership, each for their own part.

Most parishes run sign-ups, mailing lists and event forms through free online services. Free has a price: the service keeps a copy of the parish's people and sets its own policy for what it may do with them, agreed to in a click by whoever opened the account, and some of those companies exist to sell that data. Later the same parish worries about AI working through everyone's information, without noticing that it handed the information over in a sign-up form.

In the Presence+ data store three parties decide, each for their own part. The person decides how their own information is shared. The helper decides what they record and who may read it. The community's leadership decides how the ministry's information, its rosters, sign-ups, relationships and notes, is shared with other ministries, with applications and with the Network. Nobody else decides. Nothing in the store is sold, mined or used to train anything. It is held by True Presence, Inc., a 501(c)(3), and controlled by Divine Mercy University.

What the data store gives an application

  • Available

    A HIPAA-protected store for ministry data

    Supabase, held by True Presence, Inc. and controlled by Divine Mercy University. The application's data lives under the nonprofit's safeguards.

  • Available

    Person-set sharing

    Each person decides what of their own information is shared, with whom, and for how long. Enforced on every read.

  • Beta

    Helper-set sharing

    A helper decides what they record about a conversation and which of their notes may be read, and by whom. Visibility follows the relationship the note was written on.

  • Beta

    Leadership-set sharing

    The ministry's leadership decides how rosters, sign-ups, relationships and notes are shared with other ministries, with applications, and with the Network.

  • Available

    No secondary use

    The store serves the ministry's purposes only. No advertising, no training, no resale. PHI access is logged.

  • Available

    Optional

    An organization that is already HIPAA and SOC 2 compliant may keep its own store. One that is not keeps client data here as a condition of membership.

  • Planned

    Shared with other ministries by choice

    A ministry can open part of its store to another ministry it works with, on the leadership's terms. The cooperative arrangements are being set up.

Measures

The PCOMS instruments

Available in every Presence+ tool under license from Better Outcomes Now, and served to applications through the REST API at /api/assessments/prs and /api/assessments/rrs, with the ORS and SRS on the clinical side. The person owns the score and shares it with a helper only by a prompt, each time.

  • Available

    PRS, Progress Rating Scale

    The ORS under Duncan's name for self-service and companion work. Used in Raphael, My Pathway and any Network app.

  • Available

    RRS, Relationship Rating Scale

    The four-question alliance measure for non-professional helping relationships: companion, listener, coach and spiritual direction. Scored after six sessions against the PCOMS norms.

  • Available

    ORS and SRS, clinical

    Used in Mindspirit by licensed clinicians. A signed BAA is required.

  • Planned

    Season-against-season reporting

    Measures read against the liturgical year rather than the quarter.

Pathways, courses and signals

What an app can walk a person along, teach, and post

  • Beta

    Accompaniment Pathways

    A community's ordered way forward with branches, measures and named exits, authored in Pathway Studio. An app walks a person along one with pathways:walk.

  • Beta

    My Pathway to Flourishing

    The accompanied person's own pathway and journal. One journal across apps.

  • Planned

    Hero Within self-guided pathway

    The PRS-guided journey built from Duncan's chapter, paraphrased with permission.

  • Available

    Emmaus course library

    DMU's courses on the LMS, with courses:read. Open to applicants, with a member's completions and certificates.

  • Beta

    Publishing a course

    Any organization publishes to its members, at no charge or for a price through Stripe. Being confirmed for outside apps.

  • Beta

    Signals to the home board

    An app posts what matters next, such as a check-in due or a session at four, and it appears on the person's Presence+ home with the app's name on it. home:read.

  • Available

    Devotions

    The daily content above, surfaced in the shell. devotions:pray.

  • Beta

    Formation RAG

    Retrieval over the newschola library, DMU transcripts and the CCMMP textbook, for an app's AI features. Network apps only for now.

Integrations

Services reached through the Network

Your application gets these through the Network rather than wiring each one itself.

  • Available

    Better Outcomes Now (PCOMS)

    The licensed measures, served to every app.

  • Available

    Stripe

    Course purchases and memberships. The app receives the record, never the card.

  • Available

    Google Calendar and Outlook

    Helpers' availability and sessions, synced both ways.

  • Available

    LiveKit and Deepgram

    Video sessions and transcription, with consent recorded on the relationship.

  • Available

    Twilio and email

    Messages people asked for, sent by a person who knows them.

  • Available

    Anthropic

    AI features that summarise, suggest and prepare, under HIPAA terms that keep data out of training.

  • Available

    Supabase

    The HIPAA-protected data store held by the nonprofit, where the person, the helper and the ministry's leadership decide what is shared. The daily content library is its own project.

  • Available

    Divine Office, USCCB and Regnum Christi

    The sources behind the daily content, licensed or permitted.

  • Planned

    CarePortal

    Verified needs from caseworkers, routed to helpers in the same community.

Developer tooling

How you get in and what you build with

  • Available

    REST API

    The server under /api/v1. Bearer token from Sign in with Presence+, consent applied on every response. The v1 surface is being published.

  • Beta

    Application and review

    Apply in the shell at shell.presence.plus/developers/apply. Reviewed within one business day. The apply flow is being built.

  • Beta

    Sandbox

    A new, empty instance of the Network per application, with its own identity client and seeded data.

  • Beta

    TypeScript and Node SDK

    @presenceplus/sdk, closed source, for members on approval. Next.js, Astro, React, SvelteKit and Remix through it.

  • Planned

    Other languages

    Python, Ruby, PHP, Laravel, Elixir, Go, Flutter, WordPress. The REST API works today; SDKs are planned.

  • Beta

    Documentation

    developer.presence.plus/docs: overview, identity, SDK and API pages. The OpenAPI reference is to come.

  • Available

    Membership

    $25 a month for one developer and one organization. $10 a month per additional developer.

  • Available

    Content management for a partner's pages

    Payload CMS at cms.presenceplus.org with an MCP server, API keys, SEO fields and a media library. By invitation.

  • Beta

    Compliance

    HIPAA safeguards in place. SOC 2 in progress. Organizations that are not compliant keep client data in the Presence+ store.

Research and validation

The platform can act like a university

Presence+ is affiliated with Divine Mercy University, and other universities are joining. That lets the platform do two things a vendor cannot: run research with efficient sampling across the communities on the Network, and put a claim or an application to the test under a university's standards. Both are offered to developers and to the organizations that use their apps.

  • Planned

    University Research: Validate Claims

    If an application claims a result, say that it helps people recover after an affair, the platform can design the study, draw the sample from the Network with the outcome measures already in place, run the analysis, and report whether the claim holds. The research is done under university oversight, so the finding carries a university's name rather than the vendor's.

  • Planned

    CCMMP Lens

    An application's processes are examined through the lens of the Catholic Christian Meta-Model of the Person and given a rating of how closely they are integrated with it. The rating tells a ministry what view of the person an app is built on before it is adopted, and tells a developer where the gaps are.

$ presence apply

Build on what is here

Apply, get a sandbox with these services in it, and tell us which Beta items you need opened first.