The infrastructure layer for behavioral health

The operating system
behavioral health
never had.

Beacon OS runs Beacon Integrated Support Services today — built running a real peer support agency, not designed in a boardroom.

Request Demo Become a Design Partner
The problem

Behavioral health runs mission-critical work on systems never built for it.

Compliance lives in binders and memory, not in the system doing the work.

Billing leaks through expired credentials no one caught in time.

Consent is a signed PDF, not an enforced safeguard.

Reporting gets assembled under deadline pressure, not maintained continuously.

Why Beacon

Not adapted. Built for this.

Built for behavioral health

Peer support workflows from the ground up — not a hospital EHR adapted downward.

Compliance by design

42 CFR Part 2 and credentialing enforced at the system level, not left to memory.

One system of record

Consent, planning, credentialing, incidents, and funding — one system, not five.

See it in action

This already exists.

A preview of the actual workflows Beacon Core runs today.

Product previews shown use synthetic data and illustrative workflows only — fictional organization, fictional participants, fictional staff, and a clearly-marked sample Medicaid identifier. No real participant information is displayed.
app.beaconos.com/participants/timeline
Participants
Recovery Plans
Consent
Reporting
J. Alvarez — Harbor Point Peer Recovery (sample)
Participant since Mar 2026
Encounter — Weekly check-inLogged
Recovery plan reviewedCurrent
ROI consent signedActive

Participant timeline

Every encounter and status change, one chronological view.

app.beaconos.com/consent
Participants
Recovery Plans
Consent
Reporting
Consent & ROI — 42 CFR Part 2
Enforcement, not warnings
J. Alvarez — Treatment ConsentActive
L. Brooks — ROI, Harbor GeneralExpired
D. Okafor — Treatment ConsentRevoked

Consent management

Expired or revoked consent blocks disclosure outright.

See all 8 workflows →
Outcomes, not features

What running on Beacon Core changes.

Reduced
Compliance risk
Reduced
Billing leakage
Faster
Audits
Less
Spreadsheet dependency

Illustrative targets based on Beacon Core's current automation — not yet independently benchmarked.

O
"We built Beacon because the software we needed to run our own agency simply didn't exist. Beacon Core runs Beacon Integrated Support Services today — every module started as something we needed ourselves, first."

Founder & CEO · Beacon Integrated Support Services

Let's talk.

Request Demo Become a Design Partner Talk with the Founder
Product

Every workflow Beacon Core runs, in detail.

Eight modules, one system of record. What follows are illustrative product previews — the real thing, shown with synthetic data.

Product previews shown use synthetic data and illustrative workflows only — fictional organization, fictional participants, fictional staff, and a clearly-marked sample Medicaid identifier. No real participant information is displayed.
app.beaconos.com/participants/timeline
Participants
Referrals
Recovery Plans
Consent
Credentialing
Incidents
Reporting
J. Alvarez — Harbor Point Peer Recovery (sample)
Participant since Mar 2026 · Program: Peer Recovery Support
Encounter — Weekly check-inJul 14, 2026 Logged
SDOH re-screen completedJul 08, 2026 Routed
Recovery plan reviewedJun 30, 2026 Current
ROI consent signed — Harbor GeneralJun 12, 2026 Active

Participant timeline

Every encounter, note, and status change in one chronological view — no cross-referencing binders or spreadsheets to reconstruct a case history.

app.beaconos.com/recovery-plans
Participants
Referrals
Recovery Plans
Consent
Credentialing
Incidents
Reporting
Recovery Plans — Harbor Point Peer Recovery (sample)
IPSP · WRAP · Crisis/Safety Plan
M. Whitfield — Crisis/Safety PlanCrisis flag active
D. Okafor — IPSPReviewed Jul 02 Current
P. Nair — WRAPCreated Jul 06 Review due

Recovery planning

IPSP, WRAP, and Crisis/Safety Plans in one workflow. An active crisis flag forces escalation — it doesn't wait on a staff member remembering to check.

app.beaconos.com/consent
Participants
Referrals
Recovery Plans
Consent
Credentialing
Incidents
Reporting
Consent & ROI — 42 CFR Part 2
Enforcement, not warnings
J. Alvarez — Treatment ConsentActive
L. Brooks — ROI to Harbor GeneralExpired — disclosure blocked
D. Okafor — Treatment ConsentRevoked — all disclosure blocked

Consent management

Expired or revoked consent blocks disclosure at the point of action — not a warning banner a staff member can click past.

app.beaconos.com/credentialing
Participants
Referrals
Recovery Plans
Consent
Credentialing
Incidents
Reporting
Staff Credentialing
Tied directly to billing
A. Ruiz, CPRSExpires Feb 2027 Current
R. Chen, CPRSExpired 5 days ago Billing blocked
M. Baptiste, CSAC-SExpires in 25 days Renewal due

Credential monitoring

90/60/30/0-day alerts on staff certifications — and billing is blocked automatically the moment a credential lapses, not discovered at audit.

app.beaconos.com/incidents
Participants
Referrals
Recovery Plans
Consent
Credentialing
Incidents
Reporting
Incidents & Grievances
Severity-routed, nothing lost
Missed appointment complaintFollow-up overdue
Minor grievance — resolvedClosed
Unauthorized record accessCritical — breach protocol

Incident management

Incidents route by severity automatically, with any data-breach flag overriding to critical regardless of how it was first logged.

app.beaconos.com/sdoh
Participants
Referrals
Recovery Plans
Consent
Credentialing
Incidents
Reporting
SDOH Screening
Routes directly into funding & referrals
Housing instabilityFlagged → referral routed
Food insecurityFlagged → referral routed
Transportation barrierNot present

SDOH screening

Screening results route directly into funding and referral workflows — not a form that gets filed and never revisited.

app.beaconos.com/funding
Participants
Referrals
Recovery Plans
Consent
Credentialing
Incidents
Reporting
Funding Routing Dashboard
Medicaid ID: MCD-SAMPLE-04471
Medicaid claims queue12 ready
Grant deliverable trackingSAMHSA block grant
Private payExcluded from claims queue

Funding routing dashboard

Medicaid, grant, and private-pay handled as one routed system — not three disconnected processes reconciled by hand at month-end.

app.beaconos.com/reporting
Participants
Referrals
Recovery Plans
Consent
Credentialing
Incidents
Reporting
Executive Reporting
Gated behind human approval
Active participants42 (sample)
Open incidents1 critical, 2 standard
Pending funder report — Q3Awaiting approval
Credential alerts1 blocked, 1 due

Executive reporting

Funder-ready reports gated behind human approval before anything goes out the door — no report ships unreviewed.

Want to see this on your own data?

Request a Demo
Compliance

Built for scrutiny, not just for use.

42 CFR Part 2, credentialing, incident routing, and outcome tracking — enforced at the system level, because peer support agencies operate under real regulatory and funder scrutiny.

Category, not competition

Why existing systems fail peer support.

Traditional behavioral health EHRs were built for hospitals and clinical facilities, then adapted downward for peer support. Beacon OS started from peer support workflows and never had to unlearn a hospital's assumptions.

Traditional EHRBeacon OS
Built for hospitalsBuilt for peer support
Consent warningsConsent enforcement
Credential remindersAutomatic billing blocks
Static care plansDynamic recovery planning with crisis escalation
Generic clinical workflowsPeer-led workflows, natively

This reflects design intent and current Beacon Core functionality — not a claim about any specific competitor's product.

Built for accountability

Every consent, every credential, every dollar — traceable.

Beacon Core was built assuming every workflow may one day be audited — by a funder, a regulator, or the people it serves.

Consent framework
42 CFR Part 2
Outcome tracking
Recovery Capital
Funder reporting
Human-approved
Credential checks
Real-time
Note for site editor: Reserved for actual accreditation status (e.g. CARF) once confirmed. Until then, this describes policies built to align with accreditation-grade standards — not a credential currently held.
RC RECOVERY CAPITAL

Recovery Capital is the outcome measure tracked in every Beacon Core case — the personal, social, and community resources a participant is building, not just service checkboxes.

Questions about a specific compliance requirement?

Talk with the Founder
The long arc

From Beacon Core to Beacon OS.

We're building infrastructure, not a feature list — and we're candid about which stage we're actually in.

Live today

Agency operations

Beacon Core running Beacon Integrated Support Services daily.

In development

Multi-agency platform

Beacon Platform, opening the same system to other organizations.

Vision

AI-powered workflows

Assistive automation across intake, screening, and documentation.

Vision

Population insights

Cross-agency patterns in need, capacity, and funding gaps.

Vision

Recovery intelligence

Recovery Capital signals informing what actually helps.

Vision

Outcome optimization

Closing the loop from data back into better-informed care.

Help shape what's next →
About

We built this because we lived the problem.

O
"I didn't set out to build software. I set out to run a peer support program well — and kept hitting the same wall: no system built for what we actually do. Consent tracked on paper, credentials in a binder, crisis plans held together by memory."

Founder & CEO · Beacon Integrated Support Services

That's not a knock on anyone who ran it that way before — it's what happens when the tools were built for hospitals, not for people doing recovery work in the community.

Beacon started as the system we wished existed for our own team. Beacon Core is what runs Beacon Integrated Support Services today — built one real workflow at a time, and never shipped until we'd actually used it ourselves.

Beacon Platform is us opening that same system to other organizations, because the work deserves better than a spreadsheet.

Beacon Integrated Support Services

A peer-led behavioral health organization operating in North Carolina — the agency Beacon Core runs today.

Beacon OS

The operating system built from that agency's real operational needs, now opening to other organizations.

Talk with the Founder
Built with operators, not consultants

Help shape Beacon Platform before general availability.

We're intentionally onboarding a small number of organizations to shape the future of behavioral health operations — not a broad early-access waitlist.

Open seats

Four kinds of partners we're looking for.

Design Partner

Reserved

Early Adopter

Reserved

Pilot Organization

Reserved

Referral Partner

Reserved

01

Discovery call

A structured conversation mapping your current workflows against what Beacon OS automates today.

02

Fit assessment

We're honest about whether Beacon OS is ready for your specific use case right now — including if it isn't yet.

03

Shape the build

Design partners get direct input into what gets built next, before it ships broadly.

Apply as a Design Partner