Our take
Archivedarchived by its owners on GitHub, read-only- Activity
- 19
- Community
- no data
- Issues
- 21
- Pull requests
- no data
-1 stars in the last 30 days
Panora's unified CRM integration focus may be useful to study, but its archived status and sunset notice make it a poor choice for a new production dependency.
Good fit if
- You are reviewing an existing Panora deployment or evaluating its integration-engine approach.
- Your team can assess and maintain an archived TypeScript project under the AGPL-3.0 license.
Look elsewhere if
- You need an actively maintained integration platform, since the repository is archived with no recent commits or releases.
- You need current setup guidance, because the README only announces the OSS product's sunset.
All health signals
| Last commit | 2025-10-26 (12 months ago) |
|---|---|
| Commits, last 90 days | 0 |
| Releases, last 12 months | 0 (latest @panora/frontend-sdk@1.2.0, 2024-07-27) |
| Issues closed, last 90 days | 0 |
| Project age | 3 years |
Checked on 2026-10-14 with the GitHub API.
Project history
Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.
Stars
1,033Forks
197Change since Nov 19, 2026: -1 stars·0 forks
Overview
Panora is an integration engine for connecting applications to CRM services through a unified API. It is aimed at teams that want a common integration layer instead of building each CRM connection directly into their product.
The project is archived, and its README says the OSS product was sunset. Its GitHub repository and Panora website remain useful starting points, but the repository does not provide current setup or usage instructions in its README.
Key Features
- Integration-engine focus for connecting applications with external services.
- Unified API positioning for CRM integrations.
- OAuth is among the repository's stated topics.
- TypeScript implementation.
- TypeScript SDK is indicated by the repository's release history.
- Self-hosted deployment is among the repository's stated topics.
- Docker Compose configuration is indicated by repository requirements.
Use Cases
- Product teams evaluating a unified CRM integration layer before committing to building their own connectors.
- Developers maintaining an existing Panora deployment who need to understand its TypeScript-based stack.
- Teams researching self-hosted integration approaches that include CRM APIs and OAuth.
- Engineers comparing integration-engine designs, with the caveat that this repository's OSS product has been sunset.
What you need
Detected in the repository
- Node.js 20.9.0 or newer (from package.json)
- A Compose file to run it with its related services
- Automated checks on GitHub Actions
License in plain words
AGPL-3.0network copyleft
- Commercial use: yes
- Modify and redistribute: yes
- You must keep: the license notice
- Share your changes: yes, the full source, also when people only use it over a network (e.g. as a hosted service)
- Includes an explicit patent grant from the contributors:
A summary, not legal advice: the LICENSE file is what applies.
Getting Started
The README does not provide installation steps. Start with the repository and its README for any available project materials; the README points to Panora for what's new.
Considerations
The repository is archived and read-only, with no recent commit activity or releases in over a year. The README states that the OSS product was sunset, so verify that the code and any required services still meet your needs before planning a deployment. The repository's AGPL-3.0 license also requires review for your intended use and distribution.
Found this useful?
Share it with someone who would like Panora.