The State of Docs Report 2025 is live! Dive in and see why docs matter more than ever:
Read the report
LogoLogo
ProductPricingLog inSign up
  • Documentation
  • Developers
  • Guides
  • Changelog
  • Help Center
  • Getting Started
    • GitBook Documentation
    • Quickstart
    • Importing content
    • GitHub & GitLab Sync
      • Enabling GitHub Sync
      • Enabling GitLab Sync
      • Content configuration
      • GitHub pull request preview
      • Commit messages & Autolink
      • Monorepos
      • Troubleshooting
  • Creating Content
    • Formatting your content
      • Inline content
      • Markdown
    • Content structure
      • Spaces
      • Pages
      • Collections
    • Blocks
      • Paragraphs
      • Headings
      • Unordered lists
      • Ordered lists
      • Task lists
      • Hints
      • Quotes
      • Code blocks
      • Files
      • Images
      • Embedded URLs
      • Tables
      • Cards
      • Tabs
      • Expandable
      • Stepper
      • Drawings
      • Math & TeX
      • Page links
    • Reusable content
    • Broken links
    • Searching content
      • Search & Quick find
      • GitBook AI
    • Writing with GitBook AI
    • Version control
  • API References
    • OpenAPI
      • Add an OpenAPI specification
      • Insert API reference in your docs
    • Guides
      • Structuring your API reference
      • Adding custom code samples
      • Managing API operations
      • Describing enums
      • Integrating with CI/CD
  • Extensions reference
  • Publishing Documentation
    • Publish a docs site
      • Public publishing
      • Private publishing with share links
    • Site structure
      • Content variants
      • Site sections
    • Site customization
      • Icons, colors, and themes
      • Layout and structure
      • Extra configuration
    • Set a custom domain
    • Setting a custom subdirectory
      • Configuring a subdirectory with Cloudflare
      • Configuring a subdirectory with Vercel
    • Site settings
    • Site insights
    • Site redirects
    • Visitor authentication
      • Enabling visitor authentication
      • Setting up Auth0
      • Setting up Azure AD
      • Setting up AWS Cognito
      • Setting up Okta
      • Setting up OIDC
      • Setting up a custom backend
  • LLM-ready docs
  • Collaboration
    • Live edits
    • Change requests
    • PDF export
    • Inviting your team
    • Comments
    • Notifications
  • Integrations
    • Install and manage integrations
    • GitHub Copilot
  • Account management
    • Plans
      • Legacy pricing
      • Sponsored site plan
      • Non-profit plan
      • Billing policy
    • Subscription cancellations
    • Personal settings
    • Organization settings
    • Member management
      • Invite or remove members
      • Roles
      • Teams
      • Permissions and inheritance
    • SSO & SAML
      • SSO Members vs non-SSO
  • Resources
    • GitBook UI
    • Keyboard shortcuts
    • Glossary
Powered by GitBook
LogoLogo

Resources

  • Showcase
  • Enterprise
  • Status

Company

  • Careers
  • Blog
  • Community

Policies

  • Subprocessors
  • Terms of Service

LoadingFor you

Basing on your context...

Was this helpful?

Edit on GitHub

Last updated 3 months ago

Was this helpful?

We welcome applications for our non-profit plan from organizations that meet certain criteria. Broadly, these fall into one of three categories:

  1. Non-profit organizations

  2. Open source organizations

  3. Education-related groups

If you won’t need to collaborate with others and/or can use to collaborate via GitHub and GitLab then your needs should be covered by our Free plan!

If you want to publish a docs site for free too, you can choose from either a Basic site with limited features, or which has more features and earns you funding through small, relevant ads. See for more details on these plans.

If you will need to collaborate with others, then please continue reading.

Our criteria

For all

We apologize in advance if we reject your application. We don’t have the resources to share details. We’ll do our best to give you some context if possible, but please check our criteria below to figure out what might be wrong. Please note you can reapply at any time if you are able to adjust and meet our criteria.

Your organization should not:

  • be a church, affiliated with one, or promote any specific religion.

  • be a school, college, university, etc. (but it can be a student group, lab group, course group, etc.).

  • be a government office, ministry, or function (but can be a small municipality local office).

  • be a private foundation.

  • have political affiliations.

  • promote a dogma.

  • promote a religious position as part of its activity.

  • promote discrimination of any kind, on the basis of gender (identity or expression), race, ethnicity, political or religious opinion, sexual orientation, or anything else.

  • be a crypto currency related project

Criteria for non-profit organizations

Your organization needs to:

  • Be a company with an official non-profit status.

  • Share a valid charitable status (501(c) or equivalent for your country).

Criteria for open source projects

Your Git repository must:

  • Exist publicly on GitHub or GitLab.

  • Be a truly open source project that is not associated with a for-profit or venture-backed company.

  • Not be an empty repository.

  • Not be a fork with no activity of its own.

  • Have a README.md file that clearly explains what the software is about.

  • Have a CONTRIBUTING.md file that explains how to contribute to the project.

  • Have a CODE_OF_CONDUCT.md file.

Criteria for education-related groups

  • The organization must not represent a school, college, or university as a whole.

  • The organization may represent a small group related to a school, college, or university.

  • You may be a small student group or a teacher organizing a course for a small group of students.

Individual students who want to keep their personal and course notes should use our Free plan. This plan provides unlimited private spaces at no cost, without needing to apply for the Community plan, and if you want to publish docs sites you can select a Basic or Sponsored site for free.

How to apply

Submitting your application via email

Depending on which type of organization you are applying for, please follow the relevant steps listed below.

  • Briefly describe the purpose of your non-profit organization.

  • Share a link to your organization’s public website.

  • Attach your non-profit organization’s valid 501(c) or equivalent documentation for your country.

  • Include the link to your organization. Finding this link is described in step 3 of the section above.

  • Briefly describe the purpose of your open source project.

  • Share a link to your public Git repository on GitHub or GitLab.

  • Include the link to your organization. Finding this link is described in step 3 of the section above.

  • Ask each member of the group to create their own GitBook account using their school email address, and invite them to the organization. Please only send your application once this has been done.

  • Briefly describe your group and its purpose.

  • Share a link to a public website associated with your education group, if you have one.

  • Include the link to your organization. Finding this link is described in step 3 of the section above.

If you have any questions, feel free to contact our support team.

Have a LICENSE file with .

Make it easy for others to .

Sign up or sign in Start by for a GitBook account if you don’t have one yet, or if you do.

Choose an organization Decide which organization you would like the Community plan to be applied to. This could be one that you’ve already created, or you might want to create a new organization. (To create a new organization, click the switch organization toggle near the top of the , then click create an organization, and follow the prompts.)

Get the organization’s URL In the , click on the name of the organization you chose in step 2. Copy or make a note of the URL in your browser. It will be in the format app.gitbook.com/o/[string]/home, where [string] will be a unique string of letters and numbers used to identify that organization.

Contact us via our messenger on Select ’Contact Support’ and then ’I have a question about pricing’ then ’I want to apply to the Community plan’, or alternatively send us an email with the required info to support@gitbook.com

  1. Account management
  2. Plans

Non-profit plan

On this page
  • Our criteria
  • For all
  • Criteria for non-profit organizations
  • Criteria for open source projects
  • Criteria for education-related groups
  • How to apply
  • Submitting your application via email
Git Sync
a Sponsored site
our open source page
a valid OSS license
contribute
signing up
signing in
sidebar
sidebar
our website