Notifuse VS git-sizer

• Self-Hosted & Open Source
  AGPL-licensed and self-hostable: one Docker image plus PostgreSQL 17, with your contacts, templates and analytics staying on your own servers.
• Bring Your Own ESP
  Connect Amazon SES, Postmark, SendGrid, Mailgun, Mailjet, SparkPost or any SMTP server — Notifuse never charges per email sent.
• Visual Email Builder
  Drag-and-drop MJML editor with live preview and Liquid templating, so emails stay responsive and personalized per contact.
• Broadcast Campaigns
  Send newsletters to a list or a segment, schedule them in your workspace timezone, and track opens and clicks per link.
• A/B Testing
  Test subject lines or content on a sample of your audience, pick the winner automatically on open or click rate, then send it to the rest.
• Marketing Automation
  Visual multi-step journeys built from trigger, delay, email, filter, A/B split, list and webhook nodes, with entry conditions on the trigger.
• Transactional Email API
  REST API for receipts, password resets and alerts, sharing the same templates, tracking and contact timeline as your campaigns.
• Real-Time Segmentation
  Dynamic segments from contact properties, list status, engagement and custom events, with nested rules and relative dates — membership updates itself.
• Contact Profiles & Timeline
  Every contact carries custom fields and a full history: emails, opens, clicks, list changes, web sessions, custom events and webhook events.
• Cookieless Web Analytics
  First-party site analytics with no cookie and no consent banner, ranking pages by TimeScore — the active time visitors really spend.
• Notification Center
  An embeddable widget that lets contacts manage their own subscriptions and preferences without leaving your site.
• AI Assistant
  Bring your own Anthropic, OpenAI or Gemini key to write emails, draft blog posts, and ask your web analytics which campaigns worked.
• Custom Events & Data Feeds
  Send your own events over the API to trigger automations and feed segments, and pull external JSON into templates at send time.
• S3 File Manager
  Upload images and attachments to any S3-compatible bucket and serve them over your own CDN.
• Blog CMS
  Publish a blog from the same workspace with Liquid theming, so your newsletter and your site share one content pipeline.

• Comprehensive Repository Analysis
  git-sizer analyzes many different dimensions of a Git repository including commit count, tree size, blob size, history depth, and reference counts, providing a holistic view of repository health and potential scaling issues.
• Easy to Use
  The tool is simple to run with minimal setup—just execute it within a git repository—and it produces clear, human-readable output that highlights potential problem areas without requiring complex configuration.
• Identifies Performance Bottlenecks
  It helps identify specific issues that could degrade Git performance, such as excessively large blobs, deep history, large trees, or too many references, which is valuable before migrating or scaling repositories.
• Open Source and Maintained by GitHub
  Being an official GitHub project, it benefits from credibility, community trust, and ongoing maintenance, and it is well documented with clear explanations of what each metric means.
• Useful for Pre-Migration Checks
  It's particularly helpful for teams migrating repositories to new platforms or consolidating repos, as it flags potential issues that could cause problems during migration or with hosting providers' limits.

Possible disadvantages

• No Automatic Remediation
  git-sizer only identifies and reports issues but does not offer any built-in tools or automated processes to fix problems like large blobs or excessive history depth—users must use separate tools like BFG Repo-Cleaner or git-filter-repo.
• Output Can Be Overwhelming for Beginners
  While detailed, the output includes many metrics and threshold levels that may be confusing for users unfamiliar with Git internals, requiring some learning curve to fully interpret results.
• Limited to Local Analysis
  The tool analyzes a local clone of the repository, so it requires users to have a full local copy of the repo (or at least enough history) to get accurate results, which can be time-consuming for very large repositories.
• No Real-Time Monitoring
  It functions as a one-time analysis tool rather than providing continuous or real-time monitoring of repository health, requiring manual reruns to track changes over time.
• Command-Line Only Interface
  The tool lacks a graphical user interface, which may be less accessible for users who prefer visual dashboards or are less comfortable with command-line tools.

No analysis of Notifuse yet.

Tracking Notifuse since Mar 2021.

• how to keep github repos small?

  Also there’s a cool project from GitHub you can use to help understand the size of git’s objects in your git repo https://github.com/github/git-sizer. This might help you determine what the best cloning strategy could be. Source: almost 5 years ago