Frequently asked questions

The OpenAR Collective (legal name: The Open Accounts Receivable Collective Foundation) is a nonprofit organization created to support the accounts receivable and debt collection industry. Its purpose is to provide free, openly available resources to anyone working in or with the industry, including software, educational content, peer community, and compliance reference materials. Everything the Collective produces will be free and available to anyone, with no membership requirement and no commercial agenda.

The most ambitious thing the Collective is building is a free, open-source AR and collections platform: a complete software system that any agency could download and use as an alternative to the expensive commercial platforms that dominate the market today. That platform is the flagship project, but it is one piece of a broader mission to provide neutral, public-interest infrastructure for an industry that has never had it.

Everyone who works in, with, or around the accounts receivable and debt collection industry. That includes:

• Collection agencies of every size, from solo practitioners to large enterprises
• Creditors and AR departments at banks, healthcare systems, utilities, and other originators of debt
• Debt buyers and the firms that work with them
• Collection law firms
• Vendors and service providers
• Compliance professionals and consultants
• Consumer advocates and legal aid attorneys
• Academic researchers studying the industry

The Collective is deliberately broad in its audience because the resources it produces are useful across the industry. A small agency might use the software directly. A creditor might use the educational resources to better understand its vendors. A consumer advocate might use the published compliance materials to evaluate industry practices. A researcher might use anonymized industry data to study consumer outcomes. All of these audiences benefit from a neutral, public-interest organization that does not have a commercial agenda.

No. The Collective has no membership fees and no membership requirement to access anything it produces. The software, the documentation, the educational resources, the webinars, and the community are all free and open to anyone.

The Collective does offer a free membership program that provides access to the verified practitioner areas of its community. Verification confirms only that you work in or with the industry. There is no fee, no application review beyond confirming your professional engagement, and no requirement that you agree with any particular position or affiliate with any particular organization. The point of the verification is to keep peer discussion professional, not to gatekeep access.

Not at all. While the flagship software platform is obviously technical in nature, most of what the Collective offers is not. The peer community is open to anyone. The educational resources are written for practitioners, not engineers. The compliance reference materials are aimed at the people doing compliance work, regardless of technical background. The webinars and workshops cover operational and regulatory topics alongside technical ones. If you are an agency owner or operator, a compliance professional, a vendor, an attorney, a consumer advocate, or a researcher, there are resources and community spaces oriented to your work.

Even on the software side, “using” the platform does not require technical skill any more than using any other AR system does. Collectors, supervisors, and managers will interact with the platform through a normal web interface, just like any other modern software. The technical complexity is what is required to install and maintain the software, and that is exactly the kind of work that certified vendors will offer as a paid service for agencies that do not have in-house IT capacity. The most important thing the Collective offers, and the one that does not require any technical knowledge to engage with, is the peer community itself: practitioners helping each other navigate a complex, regulated industry.

A nonprofit is the right structure for a project that exists to serve the public rather than to generate returns for owners or investors. The Collective has no shareholders, no equity, and no profit motive. Everything it earns goes back into the mission. Its only obligation is to the public benefit it was organized to serve.

This matters for a project meant to be neutral, durable infrastructure for an entire industry. A for-profit company stewarding open-source software has an inherent conflict between what’s best for the software’s users and what’s best for its shareholders. A nonprofit has no such conflict. The Collective is legally bound, through its incorporation documents and its nonprofit charter, to operate exclusively in the public interest. That structural commitment is exactly what makes the Collective trustworthy as a neutral host for shared industry infrastructure.

The Collective is governed by a Board of Directors, not by the founder personally. The Board is responsible for the Foundation’s strategic direction, financial stewardship, and adherence to its mission. Directors are recruited for their expertise, including legal and compliance, financial, consumer advocacy, academic, and fundraising backgrounds, and serve in a fiduciary capacity, meaning they are legally obligated to act in the Foundation’s best interest, not their own or any outside party’s.

The Board’s composition is deliberately weighted toward independent directors, meaning people with no business relationship to the founder and no financial stake in the Foundation’s activities. This independence is what allows the Foundation to credibly claim neutrality. The Board, in turn, answers to the public the Foundation serves, to the IRS (which oversees nonprofit compliance), and to the state of Delaware (where the Foundation is incorporated). All of these oversight mechanisms are standard for charitable organizations and are designed to ensure the Foundation does what it says it will do.

The Collective is funded the same way other successful open-source nonprofits are funded: through a combination of charitable donations, sponsorships from organizations that benefit from the work, grants, and limited revenue from activities that do not compromise the Collective’s neutrality, such as a vendor certification program. The founder is also contributing significant time and personal funding during the early years.

Comparable models exist and have worked for decades. The Linux Foundation, the Mozilla Foundation (which makes Firefox), the Python Software Foundation, the Apache Software Foundation, and the Eclipse Foundation (which stewards a large family of enterprise development tools) all operate on similar principles. The accounts receivable industry has never had an organization like this, but the funding model is well-established in the broader software world.

No on the first count, and not in the way most industry organizations do it on the second. The Collective will not sell endorsements, featured placements, sponsored content, vendor rankings, or favorable positioning of any kind. This is a structural feature of the Foundation’s nonprofit charter and conflict-of-interest policies, not a policy decision that could change later. Accepting payment in exchange for promotional treatment would be inconsistent with the Foundation’s charitable purpose and would violate its fiduciary obligations to the public. Charitable donations and sponsorships may be accepted, and donors may be acknowledged publicly the same way universities and museums acknowledge their supporters, but acknowledgment is not endorsement and donor relationships will not influence the Collective’s content or programs.

The Collective will also not rank or endorse vendors as a general matter, even without payment involved. The moment the Foundation starts picking commercial winners and losers, it becomes an influence broker, and every vendor in the industry has reason to lobby or pressure it in ways that are corrosive to its mission. Beyond that, vendor fit is contextual: a vendor that is excellent for one agency may be wrong for another, and a neutral organization is not in a position to make that call. What the Collective will do is run a vendor certification program that confirms specific competencies, such as demonstrated competence with the open-source platform, and publish neutral factual information about what vendors offer. The hiring decision belongs to the agency.

This is exactly the risk that the open-source model and the nonprofit structure are designed to address. Because the source code is public, no single person can take it away. If the founder disappears tomorrow, every agency running the platform keeps running it, every developer with a copy of the code keeps having it, and the community can continue developing it independently if the original organization fails.

The nonprofit structure adds another layer. The Collective is governed by an independent Board of Directors, not the founder personally. Assets are owned by the Foundation, not by any individual. If the founder steps away, the Board continues. If the Foundation itself were to dissolve, the software would still exist and could be picked up by another nonprofit or community group. This is fundamentally different from a commercial vendor that goes bankrupt and takes its proprietary software, your data formats, and your support relationship with it.

Discord started as a gaming platform but has evolved into one of the most widely used real-time community platforms on the internet. It is now the platform of choice for countless professional, technical, and special-interest communities, including major open-source software projects, academic research groups, financial services communities, and developer organizations of every kind. The reason is straightforward: Discord does what a community platform needs to do, does it well, and does it free of charge.

The alternatives have meaningful drawbacks. Slack is excellent but charges per user at scale, which is a problem for a free, open community. LinkedIn is structurally a sales-pitch environment. Email lists have terrible discoverability and onboarding. Web forums require constant moderation infrastructure. Reddit puts the platform in control, not the community. Discord lets the Collective host an open, structured, free, real-time community without taking a dependency on a paid platform or accepting a venue that’s hostile to focused professional discussion.

Anyone can join, and there is no cost. The community has two tiers. The public tier is open to anyone in the world with no qualification required; it serves as an entry point for people exploring the Collective’s resources. The verified practitioner tier is where substantive professional discussion happens, and it is open to anyone with a professional engagement with the AR industry: agency staff, creditors, vendors, attorneys, regulators, academics, advocates, and so on. Verification confirms that engagement; there is no fee, no financial commitment, and no requirement to affiliate with any organization.

The two-tier structure exists to keep peer discussion professional. Practitioners need a venue where they can speak frankly about operational and compliance issues without having to assume the audience may include the general public. The verified tier provides that. The public tier provides a friendly front door for everyone else.

Through clear community standards, active moderation, and a structural commitment to non-commercial discussion. Vendors are welcome as participants, but commercial solicitation between members is prohibited. There are no sponsored channels, no paid placements, and no opportunities for vendors to buy visibility. Moderators are empowered to enforce these standards, and because the Foundation has no commercial constituency to placate and no revenue stream tied to vendor participation, the standards can be enforced rather than quietly bent.

Open-source software is software whose source code, the human-readable instructions that tell the computer what to do, is published publicly for anyone to read, copy, modify, and use. There is no licensing fee, no per-seat cost, and no vendor relationship required. You can download it, run it, and change it to fit your needs.

Most people use open-source software every day without realizing it. The Linux operating system that powers the majority of the internet’s servers is open-source. The Firefox web browser is open-source. Most modern programming languages are open-source. WordPress, which runs roughly 40 percent of the world’s websites, is open-source. The model is mature, well-understood, and proven across decades of use in nearly every industry.

The commercial market works for some agencies and not for others. The AR software market has essentially split into two tiers: older platforms struggling to keep up with modern compliance, integration, and interface standards, and newer platforms whose per-seat or transaction-based pricing cuts deeply into profit margins. The middle ground, capable software at a price any agency can absorb, has been hollowed out.

Larger agencies are not exempt. Commercial pricing scales with size, so being big does not make the problem go away. Some larger agencies, frustrated with the cost and constraints of off-the-shelf systems, have invested in building their own. That may satisfy their needs, but the agency ends up operating, in effect, as a software company without the intent or infrastructure to do so, maintaining homegrown code that becomes expensive to support, hard to staff around, and difficult to modernize. Others stay on legacy commercial platforms whose vendors treat them as long-term revenue rather than partners, and dedicate significant internal engineering effort to working around the system rather than with it.

The result is an industry in which very few agencies, of any size, are well served by the status quo. An open-source alternative is built for that whole picture, not one slice of it. It puts modern software within reach of smaller agencies, offers mid-sized ones a path that does not require a leap to enterprise pricing, and gives larger agencies a shared, professionally stewarded codebase they can extend and contribute to instead of building their own from scratch or paying premium prices for a system they end up working around.

Yes, really. The software will be available under a standard open-source license that permits anyone to download it, run it, modify it, and use it commercially, with no fee owed to the Collective ever. This is not a trial, not a starter tier, and not a feature-limited version. It is the actual platform.

The closest thing to a catch is that open-source software has no built-in support contract. If you download it and run it yourself with no help, you are responsible for installation, configuration, maintenance, and troubleshooting. This is exactly how most open-source software works. The Collective will publish documentation, host a community where users can help each other, and, over time, maintain a list of certified vendors who provide paid implementation and support services for organizations that want them. The software itself remains free; paid help is optional.

Free trials and freemium products are commercial offerings designed to convert you into a paying customer. They typically have time limits, feature limits, user limits, or all three. The vendor’s goal is to give you enough to get hooked and then charge you when you outgrow the free version. “Community editions” of commercial software are similar: usually a stripped-down version of a paid product, controlled by a company whose primary business is selling the full version.

Open-source software is structurally different. There is no paid version. There is no upsell. The Collective has no commercial product to sell you, and the Collective’s nonprofit charter legally prohibits it from operating one. The Foundation exists, in part, as the legal steward of the software’s permanently free nature: its incorporation documents, its nonprofit charter, and its governing board are the mechanisms that ensure the software remains free, in perpetuity, regardless of who is running the Foundation in the future. The software is the same software whether you are a one-person agency or a thousand-seat enterprise, and no one, including the founder, has the authority to suddenly start charging for it later. That permanence is the entire point.

Some of it, sure. Most successful open-source projects, however, are built by a mix of paid professionals, part-time contractors, volunteer contributors who donate their time, and increasingly, developers using AI-assisted tools to accelerate routine work. The OpenAR Collective follows this pattern. The founder contributes significant time and personal funding, part-time contractors handle specialized work, and volunteer contributors from the community will participate as the project matures.

A direct word on AI-assisted development: the platform is not being written by AI in any unsupervised sense. Every line of code, whether drafted by a human or by an AI tool with a human at the keyboard, is reviewed, tested, and approved by qualified human developers before it becomes part of the software. Architecture, security, and compliance decisions are set by humans under formal governance. AI is a productivity tool here; the judgment and accountability stay with the people responsible.

This is one of the most important questions, and the honest answer has two parts.

The Collective itself does not provide 24/7 emergency support for individual users. That is not a service a small nonprofit can responsibly promise, and it is not the Collective’s role. The Collective maintains the software, fixes bugs, publishes updates, and runs a community where users can ask questions and get answers from peers and contributors. Agencies that need formal support, including emergency response, integration help, and customization, will be able to engage certified vendors who provide those services commercially. The Collective will run a vendor certification program to identify firms that have demonstrated competence with the platform. This is the same model that has worked for decades in the broader open-source world: the software is free, and a competitive ecosystem of service providers offers paid help to organizations that want it. You get the cost benefits of free software and the operational reliability of professional support, with the added benefit of being able to switch service providers without switching software.

Yes, and many do. The financial services industry runs an enormous amount of mission-critical infrastructure on open-source software. Banks run on Linux. Trading systems are built on PostgreSQL. The encryption that protects nearly all online financial transactions is implemented in open-source libraries. The notion that “free” implies “amateur” is a misconception left over from open source’s earliest days.

What makes software trustworthy for regulated use is not whether you paid for it, but whether it is well-engineered, well-tested, well-documented, and well-maintained. The OpenAR Collective platform is being designed from the start with regulatory requirements in mind: cryptographically sealed audit trails, fine-grained access controls, configurable compliance workflows, and the kind of operational safeguards that regulators expect to see. The platform’s compliance posture is a core design priority, not an afterthought.

Open-source projects use formal change-control processes that, in many ways, offer better security than closed commercial software. Every proposed change to the platform is submitted as a public “pull request” that other contributors review before it can be accepted. Nothing makes it into the released software without passing review. The review history is public and permanent, so anyone can audit what changed, who proposed it, and who approved it.

This is the opposite of how proprietary software works, where you have no idea what is in the code you are running and no ability to verify that it does what the vendor claims. Closed-source platforms have a long, well-documented history of containing hidden problems their vendors did not disclose, including hardcoded administrator accounts with static passwords known internally to the vendor’s staff, undocumented “support” backdoors that bypass normal authentication, and similar shortcuts that would be caught immediately in a public code review. With proprietary software you find out about these things only when a researcher reverse-engineers the product or when a breach forces disclosure. Open-source software gets reviewed by far more eyes than any single commercial vendor’s internal team, and major vulnerabilities are caught and fixed publicly, often within hours of discovery. The Collective will follow established open-source security practices, including signed releases, dependency scanning, and a published process for reporting and addressing security issues responsibly.

The source code will be published on the Foundation’s GitHub organization, under the Apache License, Version 2.0. Nothing is available to download yet. The platform is in its initial architecture and design phase, and there is no release today.

Development happens in the open rather than behind a curtain, so repositories become public as they are established rather than at a later unveiling. Watching the GitHub organization is the most direct way to follow the work as it lands, and the Foundation will announce releases through its own channels.

The platform is built in two layers, and the two names reflect the two layers. Wax is a general-purpose application framework: the foundation that handles things every business application needs, like user accounts, audit trails, workflow automation, and the structural plumbing that nothing visible could work without. HiveAR is the AR-specific platform built on top of Wax: the accounts, payments, compliance workflows, and other features that make it useful for collections work.

Splitting the platform this way has practical benefits. Wax can stabilize early and stay stable, because the kinds of things it does don’t change much. HiveAR can evolve more freely as the AR domain matures, without disturbing the foundation underneath it. Other organizations could even use Wax as a foundation for entirely different applications, contributing improvements that benefit HiveAR alongside their own work. For most users, the distinction won’t matter day-to-day; you just run the platform. The split is mostly relevant to developers and to long-term technical sustainability.

No, not in the way that term is typically used. The platform is designed to be self-hosted, meaning each agency installs and runs its own copy on infrastructure it controls. That infrastructure can be cloud-based (AWS, Azure, Google Cloud, or any other cloud provider), on-premises servers in your own data center, or hosted by a third-party vendor of your choosing. The choice is yours. What the Collective will not do is run a shared, centralized hosted service where every agency’s data lives on Foundation-controlled servers.

This is a deliberate design choice. Operating a hosted service for an entire industry would require the Foundation to handle other agencies’ consumer data at massive scale, with all the regulatory liability, security obligations, and ongoing operational cost that entails. That is not the Foundation’s mission. By keeping the software self-hosted, agencies maintain direct control of their data, their infrastructure, and their compliance posture, which is what most regulated organizations want anyway. Agencies that prefer not to operate the software themselves will be able to engage certified vendors who offer hosted deployments as a commercial service.

That is the goal, and the platform is being designed from the start to make integration straightforward. The platform exposes a documented, versioned API, a defined set of technical entry points that other systems can connect to, which means any vendor with the technical capability can build an integration. Common AR industry integrations (credit reporting, skip tracing, payment processing, letter vendors, dialer systems, scoring services, and so on) are exactly the kinds of connections the platform’s module system is built to support.

In the early days, the available integrations will be limited to what the Foundation, its contributors, and early-adopting vendors have built. Over time, as the platform’s user base grows, vendors will have a commercial incentive to build and maintain their own integrations the same way they do for the major commercial AR platforms today. The Foundation will publish integration standards and certification criteria, so agencies can have confidence that an integration meets quality and security expectations. The model is the same one that has produced rich integration ecosystems around every major open-source platform: open standards, public documentation, and a competitive vendor ecosystem.

Yes, and arguably safer than in proprietary software. This is a common misconception worth addressing directly. Publishing source code does not expose your data; it exposes the rules the software follows. Your actual data, the consumer information, the account history, the financial records, lives in a database that you control, on infrastructure that you control, behind security measures that you implement. Nothing about the source code being public changes that.

What public source code does is allow security researchers, contributors, and your own technical staff to inspect how the software protects data. They can verify that encryption is correctly implemented, that access controls work as documented, that audit trails cannot be tampered with, and that no hidden behaviors exist. This is the opposite of proprietary software, where you have to trust the vendor’s claims because you cannot inspect the code yourself. Decades of experience across the broader software industry have shown that security through transparency produces more trustworthy software than security through obscurity. Banks, hospitals, governments, and the entire backbone of the internet run on open-source software for exactly this reason.