Built From a Historic Society's Real Work

Memml is the tool I wished I had while running Longwood Historic Society. I built it for my own very real mess first, and now other organizations can benefit from that work too.

Meet the Creator

Hi, I'm Jason Byrne. I'm the President of the Longwood Historic Society and have been the race director for local 5Ks for many years. That work spans member records, sponsorships, public events, volunteers, payments, files, and follow-up that can easily get scattered across too many tools.

For years, I was doing a lot of heavy lifting in spreadsheets, email threads, payment tools, shared drives, and memory. I looked for better software, but most options felt too broad, too expensive, or too staff-oriented for a small volunteer-led organization.

So I'm building Memml around the work Longwood actually needs first, then generalizing carefully for other historic societies, heritage nonprofits, and friendly partner organizations. It is meant to be practical operations software, not a generic enterprise CRM and not a museum collections system.

The business angle is real, but it is not the point that started this. Memml is a passion project before it is a product: I built it for me, because I needed it, and if it helps your organization spend less time untangling admin work, even better.

Jason Byrne, President of Longwood Historic Society

Jason Byrne

President, Longwood Historic Society

Race Director & Community Organizer

Our Mission

Memml exists to reduce the operational scatter that makes volunteer-led organizations hard to run. Historic societies should be able to preserve institutional memory, invite helpers, track money, and know what needs attention without rebuilding the truth from spreadsheets and inboxes.

Source of Truth

Members, partners, sponsors, projects, tasks, payments, files, and activity history stay connected in one workspace.

Relationship-First Work

Sponsor and partner outreach stays personal while Memml helps organize context, drafts, reminders, and follow-up.

Next Actions

Leaders and helpers can see what needs attention next, from overdue tasks to sponsor payment gaps.

Why Memml?

Longwood-First, Then Generalized

Memml is shaped by actual Longwood Historic Society workflows before being generalized. That keeps the product grounded in lived work instead of imagined feature lists.

Calm for Volunteers

The full app can be powerful for owners and project leads, but helper workspaces should be obvious, action-first, and respectful of non-technical users.

Accessible by Design

Memml should not punish organizations for inviting volunteers. The product and pricing philosophy are built around small groups with real budgets and shared responsibility.

For Fellow Developers

Curious about the technology behind Memml? Here's what I used to build this platform:

Frontend

  • SvelteKit - Full-stack web framework with Svelte 5
  • TypeScript - Type-safe JavaScript with strict mode
  • SCSS - Advanced CSS with variables and mixins

Backend & Database

  • Drizzle ORM - Type-safe database queries
  • PostgreSQL - Robust, scalable database via Neon
  • Custom Authentication - Built-in auth system
  • Netlify Functions - Serverless backend runtime

Development & Deployment

  • Vite - Fast build tool and dev server
  • Playwright - End-to-end testing
  • Netlify - Hosting and deployment
  • GitHub - Version control and collaboration

Why this stack? I chose technologies that prioritize developer experience, type safety, and simplicity. SvelteKit provides an excellent full-stack experience, while Drizzle ORM makes database operations both safe and enjoyable. The entire stack is modern, well-documented, and has a vibrant community.

Get in Touch

Have questions about Memml or want to share your experience? I'd love to hear from you!