Jupyter enterprise out of funds on GitHub and has no credit card

[krassowski]

CI/CD jobs are not running across Jupyter organizations because we have an unpaid bill.

GitHub tried to collect 85 USD and that got declined. There seems to be some 4.90 USD accumulation over past week, with smaller amounts starting on March 2nd.

This is blocking ALL CI and automation in ALL Jupyter-owned repositories and organizations.

Actions

• Identify a person with Enterprise billing access
  • Add @choldgraf as enterprise owner
• Pay for the March bill to unblock CI/CD
  • Add @choldgraf's 2i2c credit card to our enterprise account
  • Pay w/ that card
• Follow up w/ GitHub to see if this was a mistake
• Follow up with LF to understand how to avoid this in the future
  • Can we attach an LF credit card to attach to this enterprise account?
  • Why weren't we notified that our card had been declined? This is the billing contact on file for github:`ap@linuxfoundation.org
  • Who should we message when both of you are out?

Links

#ask-anything > Project Jupyter enterprise out of funds on GitHub?

https://github.com/jupyterlab/jupyterlab/actions/runs/24146604618?pr=18723

https://github.com/enterprises/jupyter/billing/usage

[krassowski]

CC @jupyter/executive-council in case if that helps. There are four things that need to be done, IMO in this order:

• pay the bill from some emergency fund to unblock folks
• setup billing control to prevent it in the future and stop billing for today/tomorrow
• identify which repositories enabled Code Security and Secret Protection and disable it, identify which option causes billing
  • spread awareness to other OSS projects to prevent them from making the same mistake
• ask GitHub why this was allowed to happen (why billing controls were not auto-established for things that were added later) and ask for refund

[krassowski]

I think this is not right, the budgets seem to be setup to prevent any billing:

I downloaded usage report and it has net_amount 0 in every row.

[krassowski]

I think this can be disabled by creating a custom rule forbidding all repos from using this features on https://github.com/enterprises/jupyter/settings/security_analysis

[minrk]

Looks like it has started charging for Code Security and Secret Scanning (on JupyterHub and IPython). Not sure what has changed, since we've been using it for at least a year on JupyterHub and billing only started happening in 2026 with no apparent notice.

They are supposed to be free on public repos, but maybe they started charging for the security advisory private forks (even though they don't run on those repos). JupyterHub has no private repos, IPython has no active ones.

Seems like something to be brought up with GitHub support, because it's still very unclear what is causing this billing.

[krassowski]

Seems like something to be brought up with GitHub support, because it's still very unclear what is causing this billing.

Yeah, but they downgraded us from Enterprise to Free plan and now we do not get to contact the Enterprise support ;)

[krassowski]

Looks like it has started charging for Code Security and Secret Scanning (on JupyterHub and IPython).

I am curious how did you find out it is these two orgs? I could not narrow it down.

[choldgraf]

FYI here is what I see for "usage" in the enterprise dashboard:

[minrk]

https://github.com/enterprises/jupyter/billing/usage?period=3&group=3&customer=1329393 Group by: Organization

[minrk]

It's important to note "Billed Amount" because Gross Amount mostly just counts included free stuff.

[krassowski]

Support ticket:
https://support.github.com/ticket/enterprise/157412/4259765

[minrk]

chris edit

expanded to show code security:

[minrk]

Code Security is the only thing costing anything:

but it's impossible to attribute it to repositories as far as I can tell

[minrk]

Free plan includes Code Security and Secret Scanning on public repos and JupyterHub has zero private or internal repos.

[choldgraf]

Given that:

• All jupyter CI/CD is blocked until this is solved
• It might be a bit of time for github enterprise to get back to us
• These seem to be monthly billing cycles
• The current amount we owe is relatively small

I'd consider this a major jupyter outage for CI/CD, and suggest we do a one-time payment to pay down the bill and get people unblocked.

Do we have a credit card we can use that is linked to Jupyter funds?

If we don't have a credit card, then I will use the 2i2c credit card for this, and I'll consider it an infrastructure donation, similar to us paying for the Hetzner node on mybinder.org . I can't commit to doing this monthly, but as a one time thing it's OK for now.

Can anybody suggest a better set of action?