About the network

Infrastructure for the people already doing the work.

Runwell Network was built because the community behavioral health system doesn't lack capable people or good programs. It lacks the shared infrastructure that lets those programs see each other, coordinate in real time, and measure what's actually working.

A Runwell team member working on the platform at a multi-monitor workstation

What we're building.

A connected network for the everyday work of community behavioral health: crisis teams, recovery housing, employment, and the families searching for help. One platform, four touchpoints, zero fax machines.

Built in Ohio. Designed to scale county by county across the opioid corridor and beyond.

Our principles

How we show up.

Built with communities, not for them.

We design alongside county administrators, clinicians, operators, and the people they serve. The best infrastructure gets out of the way. We build the kind counties actually want to use.

Outcomes over activity.

Dashboards of dashboards don't save lives. We instrument for the outcomes that matter: time to placement, completion rates, stability, and return to community. What we measure is what improves.

Interoperable by default.

No vendor lock-in. No walled gardens. Open data standards, documented APIs, and clean exits. If it doesn't play well with what counties already run, it doesn't belong in the network.

Dignity is a design requirement.

Every surface, every field, every flow is designed with the knowledge that the people using it, and the people affected by it, are in some of the hardest seasons of their lives. The work reflects that.

Our commitments

Serious infrastructure requires serious practice.

Behavioral health data is among the most sensitive information a person can share. We take that responsibility as seriously as the people who entrust us with it.

Accessibility

Every product in the Runwell Network is designed and built to meet WCAG 2.1 Level AA and the 2024 DOJ Title II digital accessibility rule. We test with real assistive technologies, maintain a public accessibility statement, and treat accessibility bugs as first-class work.

Semantic HTML, proper heading structure, and ARIA where it adds clarity
Full keyboard navigation and visible focus indicators
Minimum 4.5:1 text contrast (AAA where feasible)
Captions and transcripts on all video content
Accessibility feedback channel: support@creadio.com

Privacy & Security

Behavioral health data is handled under HIPAA practices with Business Associate Agreements in place for any partner that touches protected health information. We operate on AWS infrastructure with encryption in transit and at rest, least-privilege access controls, and comprehensive audit logging.

TLS 1.2+ everywhere; AES-256 at rest
SOC 2 Type II on our implementation roadmap
Role-based access control and full audit trails
Vulnerability scanning and regular penetration testing
US data residency by default

Data Stewardship

We collect only the data needed to deliver the service. We never sell data. We never use client data to train general-purpose AI models. Counties own their data, can export it on demand, and can terminate with a clean, structured handoff.

Minimum-necessary data collection
Documented retention and deletion policies
Clear sub-processor disclosures
Structured data export on request, no exit fees
Transparency about AI use: where, why, and with what guardrails

Equity & Inclusion

Community behavioral health already serves populations too often failed by the systems around them. We build with that in mind — including in who builds with us.

Mobile-first design, because access to a phone is access to the system
Plain-language content, translated where our counties need it
Culturally responsive content review with local partners
Published vendor diversity commitments on request

Ready to build with us?

The counties already doing this work don't need permission. They need partners who show up the same way they do.

Get In Touch