Software Alternatives & Startups

Ichnos VS git-sizer

Compare Ichnos VS git-sizer and see what are their differences

Ichnos

A survey of where industries the ad platforms refuse can still legitimately be reached, read from each destination's own page and quoted.

Rating
0 reviews
Pricing
Freemium $497 / One-off (https://nexus.knightbyrd.com/ichnos)
git-sizer

Compute various size metrics for a Git repository, flagging those that might cause problems - github/git-sizer

Rating
0 reviews
Note: These products don't have any matching categories. If you think this is a mistake, please edit the details of one of the products and suggest appropriate categories.

Which is more popular?

Based on our record, git-sizer seems to be more popular. It has been mentioned 1 time since March 2021.

social mentions
0 vs 1
Marketing popularity
100% vs 0%

Base details

Website, pricing, platforms and company facts side by side.

Ichnos
git-sizer
Website nexus.knightbyrd.com github.com
Pricing
Freemium $497 / One-off (https://nexus.knightbyrd.com/ichnos) Official pricing
—
Platforms
Web REST API
—
Company Startup from US · 1 - 9 employees · 2026 —
Listed in

About Ichnos and git-sizer

In their own words, as submitted to SaaSHub.

Ichnos
git-sizer

Whole categories cannot buy advertising. The major platforms refuse them outright, or a regulator restricts what may be said and to whom. A licensed dispensary, a bail bondsman, a firearms retailer and a registered investment adviser have nothing in common except that the two channels every other...

Read more about Ichnos

No description of git-sizer yet.

Features and specs

What each product offers, as listed by its team.

Ichnos 8 features
git-sizer 5 features
  • Permission-verified routes
    Every destination's own published policy is read; access is recorded only where the site states it
  • Quoted evidence
    Each route carries the sentence from that site saying what it accepts — judge it yourself
  • Industries covered
    100 categories the ad platforms refuse or restrict
  • Places mapped
    7,178 surveyed, 1,607 confirmed to publish a way in
  • Kinds of access
    Advertising, sponsored content, press releases, directories, events, membership, editorial
  • Updated
    Several times a day — figures move, and the map you bought stays current
  • Free sample
    12 real destinations for any industry. No card, no account
  • Public API
    Machine-readable counts, free and open: kema.knightbyrd.com/api/public/ichnos
  • 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.

Analysis

An editorial look at what each product does well and who it suits.

Ichnos
git-sizer

No analysis of Ichnos yet.

Overall verdict

  • git-sizer is a solid, focused open-source tool that effectively analyzes Git repositories to identify size and structural issues that could cause performance problems or hosting limits, making it a valuable diagnostic utility for repository maintenance.

Why this product is good

  • Quickly identifies large blobs, deep histories, and other repository bloat issues that impact performance
  • Simple command-line tool with no complex setup or dependencies required
  • Provides clear, actionable metrics about repository size and structure
  • Backed by GitHub, ensuring credibility and ongoing relevance to Git ecosystem needs
  • Helps proactively catch issues before they cause problems with hosting platforms or clone/fetch performance
  • Open source and actively maintained with community input

Recommended for

  • Repository administrators managing large or growing codebases
  • Teams migrating repositories to new hosting platforms with size limits
  • Developers troubleshooting slow clone, fetch, or checkout operations
  • DevOps engineers auditing repository health before major infrastructure changes
  • Organizations enforcing repository size policies or best practices
  • Anyone dealing with repositories that have accumulated large binary files or excessive history over time

Category popularity

How often each product is chosen within a category, 0–100% relative to the other.

Score bands 0–20 21–40 41–50 51–60 61–100
Ichnos
git-sizer
100% 100%
0% 0%
0% 0%
Git
100% 100%
100% 100%
0% 0%
0% 0%
100% 100%

Questions & Answers

As answered by people managing Ichnos and git-sizer.

What makes your product unique?

Ichnos's answer

It reads the destinations rather than listing them. Anyone can produce a list of publications for a restricted industry — an AI will do it in seconds, and roughly a quarter of what it returns won't resolve. What nobody else does is fetch each one, read its published advertising or submissions policy, and record whether outside businesses may take part, quoting the sentence that says so.

Of 7,178 places surveyed, 1,607 publish a documented route. The other 78% look identical in a list. Reading them is the product.

The second thing is a finding: almost none of the available access is guest posting. It's advertising pages, press-release wires, business directories, event prospectuses and memberships. Anyone searching for "write for us" opportunities finds nothing and concludes the category is closed. It isn't closed — it's differently shaped, and that single misreading is why nobody else is here.

Why should a person choose your product over its competitors?

Ichnos's answer

The comparison isn't really like for like. Media databases are built for pitching journalists — they assume you're allowed to advertise and just want earned coverage as well. Ichnos assumes the opposite: that the ordinary channels are closed to you entirely, which is the situation for cannabis, firearms, bail bonds, med spas, payday lending and ninety-odd other categories.

Three practical differences. Every route carries the quoted sentence from that site's own page, so you can disagree with a classification rather than take our word for it. Access is sorted by what it actually is — what you can buy today versus what needs a relationship or an application — because those are different budgets and different quarters. And an industry below 18 confirmed-open routes isn't sold at all; below that it's a handful of guesses with a price on it.

Pricing is also different in kind: one payment per industry, $497 to $2,997 by survey depth, with no seat licence and no annual contract.

How would you describe the primary audience of your product?

Ichnos's answer

Marketing leads, practice owners and business-development staff at businesses in categories the major ad platforms refuse or restrict — cannabis and hemp, firearms, bail bonds, medical aesthetics, telehealth, payday lending, gambling, addiction treatment, and about ninety more.

The specific person: someone whose ad account was rejected for what their business is rather than anything it did, who has a quarter to plan anyway, and who has been reading marketing advice written for companies the platforms are happy to take money from.

Secondary: agencies serving those categories, who currently guess at channel and lose accounts when a placement is refused.

What's the story behind your product?

Ichnos's answer

It started from a question with no good answer: where can a licensed dispensary advertise? Every result was an agency blog recycling the same six suggestions, none of which said whether the destination would actually accept anything from an outsider.

The name is Greek — ἴχνος, a track or a trace. Ichnology is the science of reading tracks: establishing where something went from what it left behind, without ever seeing it. That's the method. You can't observe where a locked-out industry's audience gathers, but every industry leaves a trace — the private vocabulary it uses among itself. Follow the language and you find the room.

The refusals came out of building it. It never posts anything, never marks a route open on its own authority, and never sells contact details — a route is a place, not a person. A product sold to people who cannot advertise, which itself worked by spamming, would be ridiculous.

Which are the primary technologies used for building your product?

Ichnos's answer

Next.js and TypeScript on Vercel, Postgres via Supabase, Stripe for payments. Discovery and classification use large language models for the language layer only — never for the permission layer. Whether a destination accepts outside material is always established by fetching the page and reading it, never by asking a model what it thinks. That distinction is the whole product.

User comments

Share your experience with using Ichnos and git-sizer. For example, how are they different and which one is better?

Log in or Post with

Social recommendations and mentions

Recommendations tracked on public social media and blogs since March 2021.

Ichnos 0 mentions
git-sizer 1 mention

Tracking Ichnos since Sep 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: about 5 years ago

Alternatives to Ichnos and git-sizer

When comparing Ichnos and git-sizer, you can also consider the following products.