What Fwozen is, and isn’t.

Limits we chose, and would choose again.

Each of these buys something, and mostly the same thing. Fwozen edits no rule it did not write, deletes none at all, holds no organisation administration, and sends out no green light it has not earned.

• Fwozen never repairs or removes a rule of yours. It can write one rule, and only one: the repository ruleset that makes the fwozen check required, on a branch you enrolled, on an installation that has granted it repository administration. Repair can only ever name a ruleset id its own write ledger holds, so a rule you wrote or your platform team wrote is out of reach by construction, and no endpoint deletes a ruleset at all. Everywhere else — organisation rulesets, classic protection, a repository you have marked as managed as code, and any installation whose owner has not approved that permission — it writes the current fwozen verdict, opens the right native GitHub Rules screen with the exact values, and verifies the ruleset after you save it.
• A frozen target may wait rather than get a false success. Enrol a branch during an active freeze and the honest result is a failing check, which GitHub may decline to offer in its required-check picker. Fwozen keeps that target visibly pending and retries after the thaw instead of posting a synthetic pass to look finished.
• Classic branch protection is guidance only. The effective-rules endpoint Fwozen reads on every branch reports rulesets rather than classic protection, and we have not demonstrated a classic read against a live classic rule. So Fwozen tells you what to configure, then reports the result as unknown rather than green.
• Where a GitHub plan and repository visibility support neither rulesets nor protected branches, Fwozen reports setup as unavailable, with the reason. You do not get a button that cannot work.
• Bypass actors are usually invisible to us. GitHub rarely discloses a ruleset’s bypass list to the app reading it, and holding repository administration has not been measured to change that. Fwozen reports it as unknown, and never turns missing evidence into “nobody can bypass this”.
• gh api and Terraform are advanced alternatives for teams that manage rules as code. They are not the normal setup path, and there is no Fwozen Terraform provider.
• Deploy gating is a required check plus an Action plus an endpoint your pipeline calls. A deploy job that never calls the gate is never gated.

Not built. No date attached.

Anything here that changes gets a changelog entry with a date, the same as a feature does. We do not sell any of it, hint at it in a pricing table, or call it coming. If one of these is a blocker for you, say so. It is useful to know which one.

• No SAML single sign-on and no SCIM directory sync.
• No Enterprise tier. Free, Team at $29/mo, and Business at $99/mo is the whole ladder, and the top of it is self-serve.
• No incident triggers and no policy-as-code. A freeze starts because a person or a schedule started it.
• No Microsoft Teams app, no email or outbound webhooks. Slack only.
• GitHub Cloud only. No GitHub Enterprise Server, GitLab, Bitbucket, or Azure DevOps.
• No Mac menu bar app, and none planned.
• No migration importer. The compatibility API namespace is the migration path today.
• No GitHub Marketplace listing, no Slack Marketplace listing, and no verified-publisher badge. The Slack app is installable by any workspace; you add it from Fwozen rather than from Slack.
• Merge-group freezing is implemented and unit-tested, but has not been demonstrated against a live GitHub merge queue. We claim the mechanism, not the proof.
• No published freeze propagation number. The load harness has run three times, at 300 repositories and 5,000 pull requests, against a GitHub stub rather than live GitHub, and it has not yet passed its target of p95 under 30 seconds. A number goes here when a run against live GitHub meets that target.
• Invitations do not arrive by email. Fwozen sends none. The person inviting copies the join link and passes it on however they already talk to their team, and the teammate joins by opening it and signing in with their own GitHub account.
• Fwozen is in early access. It is live and paid and running in production, but it has months of history rather than years.
• We are not SOC 2 certified and no audit is in progress. We will start a Type I when a paying customer’s procurement requires it, and this line changes the day we sign an engagement.

Why our deploy gate is a check and an Action.

How deploy gating works →