Amor Et Cura

Built with love and care, so nonprofits can focus on the people they serve.

Comment

Inspiration

We came into this hackathon and picked the Client Case Management challenge because it felt like a real problem we could solve. When we spoke with Chandler CARE Center, a family resource center that has been helping Chandler families since 1995, we found out they still manage everything through spreadsheets and paper forms. When we looked into why, the answer was pretty simple. The software that already exists for this costs between $50 and $150 per user every month. For a small nonprofit, that is just not realistic. We also realized this was not only a Chandler CARE Center problem. Across 7 Opportunity Hack events from 2016 to 2024, more than 9 nonprofits had asked for almost the exact same thing: a way to register clients, track services, and report on their impact. That was enough for us. We wanted to build something Chandler CARE Center, and honestly any small nonprofit, could actually use after we left on Sunday.

What it does

Amor et Cura is an open-source client and case management platform built for small nonprofits. The core workflow is simple. A nonprofit can register a client, log what services were provided, schedule follow-ups, and generate reports showing their impact. We built role-based access so Admins, Case Workers, and Viewers only see what they need. Intake forms are fully configurable without code, so different organizations can adapt the system to their own process. We also added CSV import and export, a reporting dashboard with charts, an appointment calendar, document uploads, and an audit log. We also built a few AI features because so many nonprofits still rely on paper forms and handwritten notes: Photo-to-Intake: take a picture of a paper intake form and automatically fill in the client registration fields Voice-to-Case Notes: record spoken notes and turn them into structured case notes Multilingual Intake: upload a form in another language and automatically translate it into English The whole platform can be self-hosted for under $20 to $30 a month and can be deployed with one click.

How we built it

We built the frontend with Next.js 16, TypeScript, Tailwind CSS, and shadcn/ui. For the backend, we used Supabase with PostgreSQL, authentication, storage, and Row Level Security. That let us securely support our three-role system without having to build custom authentication ourselves. We built the AI features using FastAPI and connected them to Gemini, Whisper, and Llama models. The photo intake feature extracts information from paper forms, the voice feature turns recordings into organized case notes, and the multilingual feature translates forms into English before importing them. We hosted the frontend on Vercel and the AI backend on Render. To stay organized during the weekend, we used a project board and labeled everything by priority. That helped us stay focused on what absolutely needed to ship and what could wait.

Challenges we ran into

One of the hardest parts was making sure the project could work for more than just Chandler CARE Center. The judging criteria asked whether the solution could support multiple nonprofits, so we could not hardcode their intake form or workflow. Instead, we had to build configurable fields so every organization could customize the system without changing the code. That ended up taking much more design work than we expected. Security was another challenge we took seriously. We knew nonprofits would be storing sensitive information, so we made sure all secrets stayed in environment variables, nothing sensitive was committed to GitHub, and all authentication was handled securely through Supabase. We also had to make some difficult decisions about scope. There were so many features we wanted to build, but we knew we would be better off shipping a smaller product that worked really well than a larger one that felt unfinished.

Accomplishments that we're proud of

We are proud that we built something that feels real and usable, not just a prototype. A nonprofit could realistically take our project, deploy it, and start using it right away. The app is open source, inexpensive to run, and includes setup instructions, demo data, and one-click deployment. We are also proud that we built a system that can work across many different nonprofits without changing the database structure. A food bank, family resource center, or animal rescue could all use the same platform and customize it to fit their needs. The AI features are another thing we are proud of. Being able to take a photo of a paper intake form or speak case notes out loud makes the product much more useful for organizations that are still relying on paper. But honestly, the thing we are most proud of is shipping something complete. By the end of the weekend, we had a working end-to-end product that Chandler CARE Center could realistically use on Monday morning.

What we learned

We came into the hackathon with very different strengths, and that ended up making the project better. One of us kept asking, "Would someone actually use this?" and the other kept asking, "Can we realistically build this by Sunday?" That balance helped us make better decisions throughout the weekend. We also learned how important it is to read the judging criteria early. Because we looked at things like accessibility, security, generalizability, and deployment from the start, we were able to build them into the project instead of rushing them at the end.

What's next for Amor Et Cura

We want to keep building Amor et Cura after the hackathon. The next step is improving the AI features and adding an AI reporting layer that can answer questions like, "How many families did we serve last month?" or "Which services are being used the most?" We also want to add better multilingual support, especially for Spanish-speaking communities in Arizona, and eventually launch a hosted version so nonprofits can use the platform without needing to set anything up themselves. Long term, we want Amor et Cura to become an open-source tool that any nonprofit can use, improve, and build on.

Built With

Share this project:

Updates