What is Engammo and how does it work?

Engammo is an AI tool that turns GitHub pull requests into clear, grouped release notes. Install the GitHub App, and every time a PR merges Engammo writes a plain-language note and publishes it to your changelog page, widget and RSS feed, so the whole team can read what shipped.

How does Engammo generate release notes?

Install the Engammo GitHub App on your repositories. When a pull request is merged, Engammo reads the PR title, description, labels, and changed files, then uses AI to write a clear summary grouped by category from your PR labels (features, fixes, breaking changes, and more).

Is there a free trial?

Yes. Starter and Team come with a 14-day free trial. You add a card when you sign up and are billed when the trial ends ($29/month for Starter, $79/month for Team), unless you cancel first.

Can I share release notes with non-technical stakeholders?

Absolutely. Engammo provides a public changelog page and an embeddable widget you can add to any website. Release notes are written in plain language so product managers, marketers, and customers can all understand them.

How is Engammo different from a release notes generator?

Both start from merged pull requests and group changes by label. A release notes generator lists PR titles in GitHub Releases or a CHANGELOG.md file. Engammo also rewrites each PR in plain language with AI and publishes it to a changelog page, a widget, an RSS feed and JSON endpoints, with no workflow file to maintain.

Which languages are supported?

Engammo generates release notes in English by default and can translate them into Italian and Spanish. More languages are on the roadmap.

Security

Security and Data Protection

Engammo is built with security as a foundational requirement, not an afterthought. We protect your data with encryption and limited access permissions. Here is exactly how we handle your data.

Security Principles

Limited Access

Engammo only accesses the repositories you select when installing the GitHub App. It reads merged pull requests and their changes, and its only write action is an optional version tag (for example V1.2.3) on merge commits, which is off unless you turn it on for a repository. You can review the permissions during installation and revoke access at any time.

No Source Code Storage

Engammo does not clone or index your repositories, and raw diffs are not stored. When AI summaries are on, selected diff excerpts (up to about 4,000 characters per pull request) are sent to our AI provider to write the summary. We store the generated release note, PR metadata, and the GitHub webhook events we receive.

Encryption

Data is encrypted in transit with TLS and encrypted at rest by our database provider. Integration credentials, such as Kommander API keys, are additionally encrypted with AES-256-GCM.

Authentication and Access Control

Sign-in uses GitHub OAuth or an email magic link, so Engammo never stores a password. Workspace roles (Owner, Admin, Member) control who can manage billing, repository settings, and team members.

Data Handling Practices

What Data We Collect

Pull request titles, descriptions, labels, authors, and timestamps
Commit metadata for merged pull requests
Diff excerpts of merged pull requests (processed in memory, sent to our AI provider, not stored as raw diffs)
GitHub webhook events for your installation
GitHub user profile information (name, email, avatar)
Repository metadata (name, owner, default branch)
Generated release note content

What Data We Do Not Collect

Full source files or clones of your repositories
Data from repositories not selected during installation
CI/CD pipeline data or deployment artifacts

GitHub Access Scope

The GitHub permissions Engammo uses and why each is needed.

Pull requests: read

Read pull request data including titles, descriptions, labels, commits, changed files, and merge status. This is the core permission that enables release note generation.

Contents: read and write

Read commits, tags, and comparisons between versions. Write access is used only to create version tags on merge commits, if you enable that option for a repository.

Metadata: read

Read repository metadata such as name, owner, and default branch.

Webhook events

Receive pull request, push, tag creation, release, installation, and repository events so notes are generated as soon as a pull request merges.

Infrastructure Security

Application Hosting

Engammo runs on Vercel's serverless platform. Each deployment is an immutable build.

Database Security

The database is encrypted at rest by our database provider. Database credentials are stored as encrypted environment variables in our hosting provider.

Monitoring and Incident Response

We check service health every five minutes, publish it on our status page, and capture application errors automatically. We will notify affected customers of security incidents that affect their data.

Network Security

All external traffic is encrypted with TLS. GitHub webhook payloads are verified with their signature before processing. DDoS mitigation is provided by our hosting provider.

Compliance

GDPR

Workspace owners can delete a workspace and its data from Settings. To request a copy of your data or deletion of your account, email [email protected]. We do not sell personal data.

Vulnerability Disclosure

Security researchers can report vulnerabilities to [email protected]. We aim to acknowledge reports promptly and keep you updated until the issue is resolved.

About Us →Documentation →Support →Features →

Frequently Asked Questions

Does Engammo store my source code?

No. Raw diffs are not stored. We store generated release note content, PR metadata (title, description, labels, authors, timestamps), and GitHub webhook payloads. When AI summaries are on, diff excerpts are sent to our AI provider to write the summary.

What GitHub permissions does Engammo require?

Engammo requires read access to pull requests and metadata, and read and write access to contents. Write access is used only to create version tags on merge commits, and only for repositories where you enable that option. You can review the exact permissions during GitHub App installation.

How can I report a security vulnerability?

Send vulnerability reports to [email protected]. We aim to acknowledge reports promptly and keep you updated during the resolution process. We follow a coordinated disclosure model and appreciate the work of security researchers.

Can I use Engammo with private repositories?

Yes. Engammo works with both public and private repositories. The GitHub App installation controls which repositories Engammo can access. We apply the same security practices regardless of repository visibility.

How is data encrypted?

Data is encrypted in transit with TLS and at rest by our database provider. Integration credentials are encrypted with AES-256-GCM.

Does Engammo support SSO?

Engammo uses GitHub sign-in or an email magic link, so no separate password is stored. SAML single sign-on is not currently available.

Can I request deletion of my data?

Yes. Workspace owners can delete a workspace from Settings. To delete your account and all associated data, including stored webhook payloads, email [email protected] and we will complete the request within 30 days.

Does Engammo share data with third parties?

We do not sell your data or share it for marketing. We use these sub-processors: Vercel (hosting), MongoDB (database), OpenAI and Anthropic (AI generation), Resend (email), Stripe (payments), Umami and DataFast (analytics), Kommander.ai (chat widget), and Bananaloop (error monitoring). See the Privacy Policy for details.

How do I revoke Engammo's access to my GitHub repositories?

You can revoke access at any time from your GitHub organization settings. Navigate to Settings > Installed GitHub Apps, find Engammo, and click "Configure" to remove repository access or uninstall the app entirely.

Secure release notes for your team

Start generating automated release notes from your GitHub pull requests, with a 14-day free trial.

Start free trial Talk to Sales