About


My name is Al.

I am a developer. I have been building websites and web applications for 30 years, working with CMS's and CRM's that whole time. I built this product because the tools that exist for nonprofits aren't good enough, and I had a clear idea of what a better one would look like.

I have run large systems, managed teams, and worked at Silicon Valley SaaS companies. I have also done a lot of consulting for nonprofits — migrations, integrations, fixing other people's messes. This product comes out of both sides of that experience

How the work gets done

I am the developer of record on this product and the single point of control for product decisions. That's deliberate. It means the roadmap doesn't get hijacked by a sales team chasing one big customer, and it means support comes from someone who actually understands the code.

It does not mean I am alone. I work with a network of designers and subcontractors I trust, and I bring them in when a project calls for it. As the customer base grows, employees follow. The product is open source, the docs are public, and the operational runbook is documented — if I'm unavailable for any reason, the site keeps running and someone else can pick it up.

Not a SaaS company

  1. No venture capital. No board pushing for growth at any cost.
  2. No C Suite writing quarterly mandates.
  3. No sales team writing the roadmap.

That's why I can charge $150/month flat and mean it. The cost of running this product is the cost of running this product, plus a fair living for the people who work on it. There's no hidden math.

What I don't do

  1. I don't super-serve a single customer.
  2. I don't take feature requests from sales and marketing.
  3. I don't report to a C Suite.


Security

I have been in charge of large systems that required regular security audits. The shortest version of good security hygiene is: store as little data as possible, be transparent about what you do store, and put a real wall around it. This product does that.

The full security audit is [here]. The architectural choices that support it are documented [in the docs].

The code

The product is open source. You can read all of it. The repo is public. The docs are public. The management software I use to run my hosting is in a private repo — I have to make a living — but everything that runs on your site is yours to inspect, fork, or extend.

[Repo] · [Docs] · [Contact]


© 2026 My Organization