Repository navigation
Solidify Digital Ocean Partnership #4499
Description
Got a very disappointing email yesterday:
We’re reaching out to share an important update regarding the DigitalOcean Open Source Credits Program.
DigitalOcean has decided to sunset the Open Source Credits Program. As part of this change, we are no longer accepting new credit applications or approving credit renewals, extensions, or additional credit requests.
If you currently have Open Source Credits that have already been granted, those credits will continue to be honored according to their existing terms and conditions. No action is required for your existing credit allocation.
Additionally, the dedicated inbox for the Open Source Credits Program will stop being monitored as part of this transition. For any further questions or assistance, please submit your inquiries through our standard support channel: https://www.digitalocean.com/company/contact/support
We appreciate your participation in the DigitalOcean Open Source Credits Program and the work you do to support the open source community. Thank you for being part of the program.
So, we're going to have to figure out what we need to do to transition off of the 21 Digital Ocean droplets we have.
Additionally there are some volumes, snapshots, and backups we'll need to address.
Opening this as a placeholder, I'll edit with more details.
UPDATE: Digital Ocean is going to help us work this out. See below: #4499 (comment)
Activity
rvagg commentedon Oct 2, 2026
Sad, end of an era. This support from DO dates from when they hired Mikeal and he got us a free account during very io.js days; in fact I'm pretty sure it was even before io.js when we were calling it "nodejs-forward" trying to cajole Joyent into allowing the community to contribute to moving things forward before we gave up and pressed the fork button. DO continued to be the backbone of our infra, through the merge with Node v4 and to today.
🍹 thanks for all the compute and support DO.
targos commentedon Oct 2, 2026
Do we know how much time we have left with the existing credits?
sxa commentedon Oct 2, 2026
@targos As I understand it probably about a month at current usage. I was wondering yesterday if we could get a bit more leaway by downsizing some of them if that's an option (The www server isn't heavily loaded nowadays and so is probably overspecced for example)
sxa commentedon Oct 2, 2026
Copying @richardlau's list from #4498 for ease of access since it's important for this issue and shows the scale of what we're going to need to look at handling:
Infra:
Release:
Test:
MikeMcC399 commentedon Oct 2, 2026
Is the description in https://github.com/nodejs/build#tier-1-providers still accurate, referring to hosting nodejs.org?
richardlau commentedon Oct 2, 2026
Until the credits actually run out and we lose the machines, yes.
sxa commentedon Oct 2, 2026
@ryanaslett A question that needs to be asked - is there any budget around that we could use to pay for a subset of the machines to be retained once the program ends?
Of the critical infra ones,
wwwwould have to be replaced by /something/ although it could be smaller than the current machine (I wonder if we could resize it down now to save some credits in the meantime?). The CI one is of course the other system that is critical to the functioning of the project.sxa commentedon Oct 2, 2026
I'd propose we remove some of the "DO exclusive" distributions from the test matrices and consider shutting them down now. I'm not sure we currently have capacity elsewhere to immediately get those working again. Based on the findings in the other table that would be:
We also have one ubuntu2404-x64 (although that has capacity elsewhere so removing it shouldn't impact things too much) and two
ubuntu2204_docker-x64systems (Only one elsewhere so we might need to keep that for now - it runs some of the Alpine containers)richardlau commentedon Oct 2, 2026
Not just capacity. The last time I looked we don't have the ability to either provision those or upload our own images to be able to provision those in the other existing providers we have.
We'd need a serious rethink of our container testing strategy if we were to go down to the single machine as the IBM Cloud one is already lesser specced than the two DO ones. Or a rethink regardless.
sxa commentedon Oct 2, 2026
(Noting also that reducing the number of linux/x64 variants would help with #4447 which currently means that all linux/x64 variants have to be re-run if an error occurs on any one of them)
richardlau commentedon Oct 2, 2026
I've asked about gzemnid in #4501 and in the OpenJS Foundation
#nodejs-coreSlack channel.richardlau commentedon Oct 2, 2026
FWIW, in numbers this is 21 out of 132 (just over 15%) of our Ansible inventory.
sxa commentedon Oct 2, 2026
We have now removed
rhel10-x64,debian13``fedora-last-latest-x64andfedora-latest-x64` from node-test-commit-linux and announced in the #build slack channel.sxa commentedon Oct 2, 2026
Deleted the following from DO:
Will leave it a day or so (Monday at the latest) to see if anyone objects to removing that from the test job so we can bring one back if needed
richardlau commentedon Oct 2, 2026
Deleted
ansible: remove DigitalOcean RHEL 10 x64 machines (#4502)
ovflowd commentedon Oct 2, 2026
@MikeMcC399 is DigitalOcean mentioned on nodejs.org?
addidotlol commentedon Oct 3, 2026
hey! would love to help here in any way we (https://fyrastack.com) could, is there anyone i should specifically reach out to for this?
MattIPv4 commentedon Oct 3, 2026
Yes, we list them as a partner in the README, on the homepage, on the partners page, and on the downloads page. I have opened nodejs/nodejs.org#9201 to remove those references.
kvangundy commentedon Oct 3, 2026
Hey guys— can you shoot me your DO team?
Would love to keep ya’ll on DO while we figure out what version 2.0 of the program looks like.
Or if you open a ticket, I can find it and drop in more credits.
GN commentedon Oct 3, 2026
Sad to see 😔
ryanaslett commentedon Oct 3, 2026
Hi @kvangundy , thats amazing, thank you!
The OpenJS Foundation has two teams that we manage, NodeJS (TeamID: 9e687738e57c8108a51f80ce5e879c7a8284dda3) and our OpenJS foundation one (Jquery, and several smaller projects: TeamID: 6ded9d85fae8340acaa82812f5b34857c86f7557)
We'd love to be able to stay.
[-]Transition off of Digital Ocean[/-][+]Solidify Digital Ocean Partnership[/+]rginn commentedon Oct 3, 2026
Thanks, @kvangundy! We've been super grateful for Digital Ocean's support over the years and would love transition time or a new plan for our accounts with both Node.js and jQuery. Let's find a time to meet next week with my team (@ryanaslett & @bensternthal). Please shoot me an email at rginn@linuxfoundation.org and I'll work with you on scheduling a call.
sxa commentedon Oct 3, 2026
Thanks @kvangundy - thanks for reaching out - it's great news that you're keen to find a way to help us stay on DigitalOcean :-)
abctaylor commentedon Oct 5, 2026
Looks like Big Corp has been a little humiliated and is now trying to work this back :) it's a shame how so many large hosting companies like DO, AWS etc have built their fortunes on FOSS and cannot even allocate a few threads of compute to the community until it gets called out and PR takes a hit.
jacobsmith928 commentedon Oct 5, 2026
Glad to see this thread resolving in a positive way @ryanaslett!
Holler if something doesn't work out here (or you know other OSS projects looking for infra resources). I'm just starting up a new open source program at Datum.net (after donating a ~$5M million per year at Packet.net to the CNCF and about 150 other open source projects). Happy to have ideas from the community.