Teable
Spreadsheet-like no-code database built on PostgreSQL, for building business apps.
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, with conditions Probably, but read the licence.
- B2 Build your own product or service on top and offer it to customers as SaaS Yes, with conditions Check the terms for hosting and branding.
- B3 Make a closed-source derivative and sell or distribute it Unclear – verify Unclear: custom licence. Verify with a lawyer.
- B4 Use the project's name and trademark No No, not without permission. The licence covers the code, not the name or logo.
Keep in mind
- Dual licensing: the vendor also sells a commercial licence if the terms above don't suit you.
This is guidance, not legal advice. Check with a lawyer before deciding.
The licence in brief
Teable licensing (AGPL-3.0 + brand terms, MIT packages) (LicenseRef-Teable)
The core applications are AGPL-3.0 with additional terms under AGPL §7 protecting the Teable brand: the logo and name must not be removed or replaced. Packages under packages/ are MIT. The combination is not a plain OSI licence.
What does LicenseRef-Teable mean?
This is guidance, not legal advice (inte juridisk rådgivning). Check with a lawyer before deciding.
Facts
- Licence
- LicenseRef-Teable
- Licence type
- Custom licence
- Open core
- No
- GitHub stars
- 21.9k
- Latest activity
- Deployment
- Docker
- Login/SSO
- Unknown
- API
- Unknown
- Multi-tenant
- Unknown
- EU vendor
- Unknown
- Source code
- github.com/teableio/teable
- 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