diff --git a/develop-docs/backend/application-domains/feature-flags/index.mdx b/develop-docs/backend/application-domains/feature-flags/index.mdx
index 21d9a58c7c185..d38cba12e4643 100644
--- a/develop-docs/backend/application-domains/feature-flags/index.mdx
+++ b/develop-docs/backend/application-domains/feature-flags/index.mdx
@@ -21,9 +21,6 @@ manager.add("organizations:onboarding", OrganizationFeature, FeatureHandlerStrat
 
 # pass FeatureHandlerStrategy.INTERNAL if you don't plan to use options automator:
 manager.add("organizations:onboarding", OrganizationFeature, FeatureHandlerStrategy.INTERNAL)
-
-# [DEPRECATED] pass FeatureHandlerStrategy.OPTIONS to use options automator:
-manager.add("organizations:onboarding", OrganizationFeature, FeatureHandlerStrategy.OPTIONS)
 ```
 
 The feature can be enabled with the following in your `sentry.conf.py`, usually located at `~/.sentry/`:
@@ -194,14 +191,9 @@ flags are then configured via `sentry.conf.py`. For Sentry's SaaS deployment,
 you have the choice of using an option backed rollout via Options Automator with Flagpole,
 or by writing a custom feature flag handler.
 
-- [Flagpole](/backend/feature-flags/flagpole/) is Sentry's internal feature flagging library, allowing a feature
-  with multiple target segments and condition filters to be defined in YAML within Options Automator.
-
-- [Options based features](options-backed-features/) [DEPRECATED] allow a feature
-  to be rolled out to a specific subset of LA orgs, a percentage of EA orgs,
-  and/or a percentage of all orgs. These can be used in high scale situations, and are generally
-  preferred over customer feature handlers. This strategy predates Flagpole, which is the new standard
-  way to define an option-backed feature flag.
+[Flagpole](/backend/feature-flags/flagpole/) is Sentry's internal feature
+flagging library, allowing a feature with multiple target segments and
+condition filters to be defined in YAML within Options Automator.
 
 ## After launch (Graduation)
 
diff --git a/develop-docs/backend/application-domains/feature-flags/options-backed-features.mdx b/develop-docs/backend/application-domains/feature-flags/options-backed-features.mdx
deleted file mode 100644
index 6f4279f3638b8..0000000000000
--- a/develop-docs/backend/application-domains/feature-flags/options-backed-features.mdx
+++ /dev/null
@@ -1,52 +0,0 @@
----
-title: Options Backed Features [DEPRECATED]
----
-
-Options backed features using the `OPTIONS` strategy enum were a temporary stopgap
-that was used to formalize options-backed feature flags. These have since been
-replaced by [Flagpole](/backend/feature-flags/flagpole/), which is Sentry's preferred
-means of setting feature flags now.
-
-
-## Building your options based feature
-Declare your feature in sentry/features/temporary.py or
-sentry/features/permanent.py like so:
-```python
-manager.add("organizations:your-new-flag", OrganizationFeature, FeatureHandlerStrategy.OPTIONS)
-```
-
-This automatically registers a feature handler for you in getsentry, and also
-auto registers the relevant options.
-
-To roll out your feature, you'll want to set the rollout options via options
-automator. To figure out the options you need to configure, you can run the
-following script in getsentry:
-```python
-./bin/generate_automator_feature_options.py --flag organizations:your-new-flag
-```
-
-It will then produce output like
-
-```python
-Generating automator options for feature flag `organizations:your-new-flag`
-Add these to the appropriate file in options automator to roll out your feature
-For example, to roll out in the US, you can add them to https://github.com/getsentry/sentry-options-automator/blob/main/options/regions/us/app.yaml
-To roll out to all production regions, you can add them to https://github.com/getsentry/sentry-options-automator/blob/main/options/default/app.yaml
-Options:
-  organizations.your-new-flag.la-rollout: 0.0
-  organizations.your-new-flag.ea-rollout: 0.0
-  organizations.your-new-flag.ga-rollout: 0.0
-  organizations.your-new-flag.la-orgs: [
-    "codecov",
-    "sentry",
-    "sentry-sdks",
-    "sentry-test",
-    "sentry-st",
-    "sentry-emerging-tech",
-    "specto-dev",
-  ]
-```
-
-Open a pr in https://github.com/getsentry/sentry-options-automator to set
-these options and you can roll out your feature flag. You can also customize
-which orgs will be in your la rollout by modifying `la-orgs`
diff --git a/src/middleware.ts b/src/middleware.ts
index 7d6eec70b247b..118c82762ed3e 100644
--- a/src/middleware.ts
+++ b/src/middleware.ts
@@ -3574,10 +3574,6 @@ const DEVELOPER_DOCS_REDIRECTS: Redirect[] = [
     from: '/feedback-architecture/',
     to: '/application/feedback-architecture/',
   },
-  {
-    from: '/feature-flags/options-backed-features/',
-    to: '/application/feature-flags/options-backed-features/',
-  },
   {
     from: '/options/',
     to: '/backend/options/',
@@ -3788,14 +3784,6 @@ const DEVELOPER_DOCS_REDIRECTS: Redirect[] = [
     from: '/api-server/application-domains/feature-flags/flagpole/',
     to: '/develop/application-domains/feature-flags/flagpole/',
   },
-  {
-    from: '/backend/feature-flags/options-backed-features/',
-    to: '/backend/application-domains/feature-flags/options-backed-features/',
-  },
-  {
-    from: '/api-server/application-domains/feature-flags/options-backed-features/',
-    to: '/develop/application-domains/feature-flags/options-backed-features/',
-  },
   {
     from: '/backend/options/',
     to: '/backend/application-domains/options/',