Frequently Asked Questions

re-entry.ai is an operational control layer for engineering teams. It scores pull request risk, automates incident response, enforces merge guards, and governs AI coding agents — all under human-defined governance. We sit above your existing CI/CD pipeline and intervene only when risk, incidents, or guard violations occur.

re-entry.ai connects to GitHub, Jira, Slack, and other tools via OAuth. It continuously analyzes pull requests for risk signals — code diffs, file sensitivity, historical incident patterns, and guard thresholds. When risk is elevated, it can block merges, require additional reviews, create tickets, or escalate to stakeholders. All actions are logged in an immutable audit trail.

We currently support GitHub, Jira, Slack, Sentry, and PagerDuty, each connected via secure OAuth 2.0 authentication. More integrations are actively being added. Each integration can be connected in under 2 minutes during onboarding.

Yes. We use enterprise-grade encryption (TLS 1.3 in transit, AES-256 at rest), comply with GDPR and BDSG, and never sell your data. All credentials are encrypted, and you can revoke access at any time. We're based in Germany and follow strict European data protection standards.

We offer three tiers: Free (core PR risk scoring and basic guards), Pro (advanced risk analysis, unlimited guards, priority support), and Enterprise (SSO, custom onboarding, dedicated support, and advanced compliance features). Annual billing is available with savings on Pro and Enterprise plans.

Yes, you can cancel your subscription at any time. Cancellation takes effect at the end of your current billing period. We don't believe in lock-in — if re-entry.ai isn't reducing your incident frequency, you're free to leave.

Yes. During onboarding, you select which GitHub repositories to monitor. re-entry.ai analyzes pull requests across all connected repos and applies your guards consistently. You can add or remove repositories at any time from your settings.

Yes. When you authorize re-entry.ai via OAuth, you choose which repositories to grant access to. We only analyze pull requests and events from repositories you explicitly allow. You can revoke access at any time from your GitHub settings.

Guard actions are automated interventions that modify state: blocking a merge, requiring additional review, creating a ticket, notifying stakeholders, or applying labels. Read-only operations like risk scoring and analysis do not count toward action limits.

All guard actions and risk assessments are stored in an immutable audit trail with configurable retention periods. By default, audit logs are retained for 1 year. You can request GDPR-compliant deletion of your data at any time from your settings.

Yes. Human override is always available. If a guard blocks a merge, an authorized reviewer can manually unblock it with a justification that is recorded in the audit log. re-entry.ai enforces governance, but humans always have the final say.

Yes. re-entry.ai supports team-based guards, role-based access control, and shared incident views. Teams can define guards that apply to specific repositories, file paths, or risk thresholds. Enterprise plans include SSO and advanced team management.