Skip to content

docs: deprecate Heroku and DigitalOcean marketplace integrations #699

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
sertugkaya merged 2 commits into from
May 12, 2026
Merged

docs: deprecate Heroku and DigitalOcean marketplace integrations #699

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
410eec5
docs: deprecate marketplace integrations
sertugkaya May 12, 2026
d7cb178
docs: update Redis cloud provider FAQ wording
sertugkaya May 12, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion _snippets/faq-snippet.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ Yes, Upstash is compatible Redis client protocol.

## Which cloud providers do you support?

Initially we have AWS and GCP. Digital Ocean is planned.
Upstash Redis is available on AWS, GCP and Fly.io.

## Which regions do you support in AWS?

Expand Down
2 changes: 1 addition & 1 deletion llms-full.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14933,7 +14933,7 @@ Yes, Upstash is compatible Redis client protocol.

## Which cloud providers do you support?

Initially we have AWS and GCP. Digital Ocean is planned.
Upstash Redis is available on AWS, GCP and Fly.io.

## Which regions do you support in AWS?

Expand Down
2 changes: 1 addition & 1 deletion redis/help/faq.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ Yes, Upstash is compatible Redis client protocol.

## Which cloud providers do you support?

Initially we have AWS and GCP. Digital Ocean is planned.
Upstash Redis is available on AWS, GCP and Fly.io.

## Which regions do you support in AWS?

Expand Down
14 changes: 10 additions & 4 deletions redis/quickstarts/digitalocean.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,10 +6,16 @@ title: "DigitalOcean"
file="redis/start-redis-snippet.mdx"
/>

<Info>
Upstash has native integration with [DigitalOcean Add-On
Marketplace](https://marketplace.digitalocean.com/add-ons/upstash-redis).
</Info>
<Warning>
Upstash Redis on DigitalOcean is deprecated and will be permanently shut down
on **August 31, 2026**. After this date, DigitalOcean-created Upstash Redis
databases will no longer be available or supported.

To continue operating without interruption, migrate to a standard Upstash
Redis database before the shutdown date. Migration is based on RDB
export/import, and billing will move from DigitalOcean to Upstash after you
create and use the new database.
</Warning>

This quickstart shows how to create an Upstash for Redis® Database from
DigitalOcean Add-On Marketplace.
Expand Down
2 changes: 1 addition & 1 deletion workflow/quickstarts/astro.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -166,7 +166,7 @@ When deploying your Astro app with Upstash Workflow to production, there are a f

2. **Remove Local Development Settings**: In your production code, you can remove or conditionally exclude any local development settings. For example, if you used [local tunnel for local development](/workflow/howto/local-development#local-tunnel-with-ngrok)

3. **Deployment**: Deploy your Astro app to production as you normally would, for example to Vercel, Heroku, or AWS.
3. **Deployment**: Deploy your Astro app to production as you normally would, for example to Vercel or AWS.

4. **Verify Workflow Endpoint**: After deployment, verify that your workflow endpoint is accessible by making a POST request to your production URL:

Expand Down
2 changes: 1 addition & 1 deletion workflow/quickstarts/express.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -171,7 +171,7 @@ When deploying your Hono app with Upstash Workflow to production, there are a fe

2. **Remove Local Development Settings**: In your production code, you can remove or conditionally exclude any local development settings. For example, if you used [local tunnel for local development](/workflow/howto/local-development#local-tunnel-with-ngrok)

3. **Deployment**: Deploy your Express.js app to production as you normally would, for example to fly.io, Heroku, or AWS.
3. **Deployment**: Deploy your Express.js app to production as you normally would, for example to fly.io or AWS.

4. **Verify Workflow Endpoint**: After deployment, verify that your workflow endpoint is accessible by making a POST request to your production URL:

Expand Down
Loading