CareTogether CMS

Overview

CareTogether CMS is a case-management platform for community nonprofits supporting families and children. It is strongest for organizations that want to coordinate case intake, staff, and volunteers in one system. Its open-source license offers flexibility, but hosted derivatives carry source-sharing and naming conditions that matter before deployment.

Key features

Casework and shared access

Case intake forms and workflow automation give organizations a way to structure how people enter a service and how cases move forward. Clients, volunteers, and staff can use the same platform, while organizations can tailor volunteer roles and permissions. That shared environment can support coordinated work; it also makes role and record access decisions central to a sound setup.

Volunteer communications

Bulk SMS can reach opted-in volunteers either as a whole group or by segment. This is useful for organizations coordinating volunteer activity, but it is a focused volunteer tool rather than a general messaging channel for clients or staff.

Security and data handling

In the multitenant hosted environment, organizational data is held in isolated containers, and record access is filtered through the authorization model. Storage uses Azure immutability guarantees, edits leave a permanent version history, and Azure RA-GZRS keeps at least six copies across primary and secondary regions. These measures address isolation, tamper protection, and redundancy, but organizations remain responsible for determining how information about the people they serve is used; CareTogether acts as their service provider or processor.

Open-source terms and branding

CareTogether is licensed under AGPL-3.0. A hosted derivative must make its source code and modifications available to users under that license. The CareTogether name and logo are not covered by the license, and using the CareTogether CMS name for a hosted version requires written permission from Coept LLC. This is a meaningful constraint for organizations that want to adapt and publicly brand a hosted service.

Pricing

CareTogether is paid, with custom pricing. Organizations should request a quote to assess its fit; no plan tiers or seat and usage allowances are available to compare. The pricing model therefore offers no published free option for testing the platform before a purchase decision.

Platforms

CareTogether is available as a web application, with API, Linux, macOS, Windows, and self-hosted platforms indicated. Its development instructions describe a React client and an API project, and the maker says it can be built and run on operating systems supported by Node.js and .NET, including Windows, macOS, and Linux. Hybrid deployment makes it relevant to organizations weighing hosted and self-managed operation, though the AGPL-3.0 and naming terms apply to hosted derivatives.

Who it's for

CareTogether is aimed at organizations delivering local human services to support healthy families and children. It is a stronger fit for nonprofits that need case intake, workflow automation, and volunteer coordination together than for teams seeking a general-purpose case tool or broad communications suite. Organizations planning to run a hosted derivative should be comfortable sharing source code and modifications under AGPL-3.0 and securing written permission to use the product name.

Pros and cons

Pros

• Shared casework environment: clients, volunteers, and staff can use one platform, with volunteer roles and permissions customized by the organization.
• Practical volunteer outreach: bulk texts can target opted-in volunteers as a group or by segment.
• Documented data safeguards: isolated containers, permanent edit history, and at least six Azure RA-GZRS copies address access separation, tamper protection, and redundancy.
• Open-source licensing: organizations can work with the software under AGPL-3.0, subject to its requirements for hosted derivatives.

Cons

• Hosted adaptation has obligations: hosted derivatives must share source code and modifications under AGPL-3.0, and use of the CareTogether CMS name requires written permission.
• Pricing requires a request: custom pricing makes cost comparison harder before speaking with the maker.
• Volunteer SMS is limited in scope: messages are for opted-in volunteers, not a general channel for all platform users.

Alternatives

Consider Primero if a self-managed open-source deployment with a free DIY tier and community support better suits your budget and operating model. Collaborate may suit organizations that want custom pricing based on organization size, user count, and modules, without per-seat licensing fees. In-Form is another freemium option, developed by Homeless Link for organizations working with people who become homeless in England. SKAS is a paid alternative with pricing available on request. Bonterra Penelope is a paid option with unpublished pricing. CaseLight is worth considering for teams seeking an AGPL-3.0, self-hosted case-management option with public code and welcomed contributions. CaseWorthy and Bonterra ETO are also paid alternatives.

For a broader comparison, browse Nonprofit Case Management Software or Case Management Software.

Verdict

CareTogether is a considered choice for family- and child-serving nonprofits that need case intake, workflows, and volunteer coordination in one system. Its strongest reason to choose it is that shared operational focus, reinforced by documented isolation and data-integrity measures. Look elsewhere if hosted branding freedom or a transparent price is essential, since its AGPL-3.0 obligations, permission requirement, and custom pricing complicate those decisions.