Enrollait VS git-sizer

• Automatic Moodle user creation
  When a learner buys, Enrollait automatically creates a Moodle account (or matches an existing one) so you don’t need manual user setup.
• Automatic enrollment after successful payment
  As soon as the payment succeeds, Enrollait enrolls the learner into the correct course so access is granted instantly.
• Connect your Stripe account for course payments
  You connect your own Stripe account and course payments go through your Stripe (you control payouts, refunds, and payment methods).
• Sync Moodle courses & categories
  Enrollait imports/syncs your Moodle catalog structure (courses and categories) so your storefront stays aligned with Moodle.
• Single course products
  Each product maps to one Moodle course (simple 1 product → 1 course selling flow).
• Enrollait subdomain (tenant.enrollait.com)
  Your store runs on an Enrollait-hosted subdomain, so you don’t need to configure a custom domain.
• Basic email support
  Standard support via email for setup questions and troubleshooting
• Single admin user
  One admin seat to manage settings, product/course mapping, and operations.
• Email alerts
  Admin notifications by email for key events
• Branding & personalization
  Customize brand elements (like name/branding details) so the experience matches your academy identity better
• Multiple courses per product (bundles)
  Sell bundles where one checkout grants access to multiple Moodle courses in a single purchase.
• Custom domain feature
  Use your own domain (e.g., courses.yoursite.com) instead of an Enrollait subdomain.
• Extra data / order exports
  Access enhanced export options for reporting and operations (more data fields and/or more export formats for finance/admin workflows).

• 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.

Tracking Enrollait since Feb 2026.

• 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