Permit.io and The New GitBook compete for similar users in Development. One pulled more initial interest. The other generated deeper discussions. Which metric matters more depends on what you're optimizing for.
Side-by-side comparison of Permit.io and The New GitBook based on community engagement data.
Never build permissions again
Your team's go-to for technical knowledge management
Permit.io and The New GitBook compete for similar users in Development. One pulled more initial interest. The other generated deeper discussions. Which metric matters more depends on what you're optimizing for.
| Category | Permit.io | The New GitBook |
|---|---|---|
| API | Yes | - |
| Artificial Intelligence | - | Yes |
| Developer Tools | Yes | Yes |
| Development | Yes | Yes |
| Open Source | Yes | - |
| SaaS | Yes | - |
| Security | Yes | - |
Permit.io leads on raw interest score. The New GitBook leads on engagement ratio. That split is worth paying attention to. Permit.io attracted more initial eyeballs, but The New GitBook's audience engaged deeper. For most buyers, engagement ratio is the better signal.
These products share 2 categories: Developer Tools, Development. Moderate overlap suggests they target related but distinct use cases.
Permit.io is also tagged in API, Open Source, SaaS, which The New GitBook isn't. That suggests Permit.io positions itself more broadly or targets an adjacent audience.
The New GitBook has unique category tags in Artificial Intelligence. Different positioning can mean a different buyer profile, even within the same space.
Permit.io launched Sep 2023. The New GitBook launched Nov 2023. Both launched the same year, meaning they faced similar market conditions and competition levels.
Pick Permit.io if you want the product with the larger community behind it; you need something that also covers Open Source.
Pick The New GitBook if community size matters less to you than engagement depth; sustained discussion and active users are your priority; you need something that also covers Artificial Intelligence.
Permit.io: Every application requires managing permissions, and complexity is constantly on the rise. Permit.io provides permissions as a service (ReBAC, Policy as Code, APIs, and customer-facing UI), so developers can check this as done and focus on their core product.
The New GitBook: GitBook combines powerful docs with AI-powered search and insights to give technical teams a single source of truth for their knowledge. Effortlessly create, surface and improve documentation in the tools you use every day — such as Slack, GitHub and VS Code.
How directly these products compete. Three or more shared categories means they're going after the same user. One shared category means they approach the space from different angles. Zero overlap and they probably shouldn't be compared.
Comparisons are generated automatically when two products have enough data overlap. If the pair you want isn't here, the products might be in different categories or too far apart in engagement.
Either the product didn't meet our engagement threshold, or it doesn't share enough category tags with the other product to generate a meaningful comparison. We'd rather show no comparison than a misleading one.
Each product's data reflects its launch period. The comparison shows both products' engagement metrics from when they launched. The build date at the bottom of the page shows when the index was last refreshed.
Not yet. Current comparisons use launch-period data only. Post-launch tracking is on our roadmap.
Generally, yes. Engagement ratio is hard to fake. A product can generate artificial interest, but sustained discussion threads require people who actually used the product and had something to say about it.