olmOCR
Toolkit that turns PDF pages into clean, readable text using a language model.
Low activity: no changes for over six months. Check that the project is still maintained before choosing it.
Building on it: what may you do?
Short answers based on the licence, for the version in the catalog.
- B1 Change the code for internal use in your company Yes Yes. Keep the licence notices.
- B2 Build your own product or service on top and offer it to customers as SaaS Yes Yes. You don't have to share your code.
- B3 Make a closed-source derivative and sell or distribute it Yes Yes, even closed. The licence and copyright notices must ship with it.
- B4 Use the project's name and trademark No No, not without permission. The licence covers the code, not the name or logo.
This is guidance, not legal advice. Check with a lawyer before deciding.
The licence in brief
Apache License 2.0 (Apache-2.0)
Permissive licence with a patent grant. Keep the licence and NOTICE files and mark changed files when redistributing.
This is guidance, not legal advice (inte juridisk rådgivning). Check with a lawyer before deciding.
Facts
- Licence
- Apache-2.0
- Licence type
- Permissive
- Maturity
- Low activity
- Open core
- No
- GitHub stars
- 19.7k
- Latest activity
- Deployment
- Library
- Login/SSO
- Unknown
- API
- Unknown
- Multi-tenant
- Unknown
- EU vendor
- Unknown
- Source code
- github.com/allenai/olmocr
- Source
- GitHub API, fetched 2026-10-03
Licence analysis per use case
Sign in to see what the licence means for eight use cases – from internal self-hosting to offering the tool as a service.
Sign in