This page aims to keep information public about Sage's infrastructure. Question mark means that the information is not confirmed, please edit if you know more... and note the date of your update so that current and stale information can be distinguished.

Please mark which services still need to find a new home, with the system requirements and the deadline.

Current services


  • registrant: was
  • admin: was, schilly
  • tech contact: was, schilly

  • purpose: webserver where users can get support
  • hosted at: LIPN (CS lab), University Paris North (Villetaneuse)
  • contact: sage-askbot-admin@…
  • url:
  • admin: tmonteil
  • local sage dev: tmonteil
  • technology used: unprivileged LXC, debian, nginx, uwsgi, postgesql, askbot
  • issues : upgrade askbot to further versions is pretty painful (broken database migration scripts)
  • formerly hosted at: Ohio State University (thanks !)
    • resources needed: database on a separate VM, 2GB RAM, 10GB disk
    • admin: niles, tmonteil
    • local tech contact: David Alden, Josh Carroll
    • technology used: ubuntu, nginx, uwsgi, postgesql, askbot
    • there are two machines : ask-sagemath and ask-sagemath-db


  • purpose: keep the data of various services in a separate place
  • hosted at: Mathematics lab, Université Paris Sud (Orsay)
  • technology used: debian, rsync, cron
  • resources needed: 1TB disk
  • admin: tmonteil, slelievre
  • local sage dev: slelievre
  • local tech contact: Mathilde Rousseau
  • currently keeping a daily backup of :,,,,,

  • purpose: development tools, they share the same host
  • hosted at: google ?
  • technology used: ubuntu, apache, git, trac
  • resources needed: ?CPU ?RAM ?DISK
  • admin: people with root access: kclawson, ohanar, vbraun, mderickx, robertwb, wstein, dimpase
  • contact: no real organisation yet, go to sage-devel
  • url:

GitHub organization for SageMath

GitLab organization for SageMath

  • purpose: distribute and gathers automatic binary building on volunteer's machines
  • hosted at: University of Washington
  • technology used: ubuntu, nginx; using using the continuous integration framework of
  • resources needed: ?CPU ?RAM ?DISK
  • admin: ??
  • contact: ??
  • url:

  • purpose: the seed for mirrors, see MirrorNetwork? for more details
  • hosted at: University of Washington
  • technology used: rsync
  • resources needed:
    • CPU 1 core
    • RAM 2-3 GB (mostly for caching when calculating hashes)
    • DISK enough for all sage files (50+ GB)
  • admin: schilly
  • contact: schilly
  • url:

  • purpose: allow embedding sage computations within a webpage
  • hosted at:
  • technology used: production installation requires a dedicated server (either physical or virtual)
  • resources needed:
    • RAM: 32GB recommended for smooth operation, 16GB may become enough in the future
    • CPU: the more the better for handling spikes in load and allowing parallel interacts, but any will do if necessary
    • DISK: must have BTRFS at least for /var/lib/lxc, SSD is preferable, 100GB should be sufficient for the foreseeable future
  • admin: novoselt
  • contact: novoselt
  • available urls:,

  • purpose: the wiki you are reading!
  • #33725: Migrate to
  • hosted at: LIPN (CS lab), University Paris North (Villetaneuse)
  • contact: sagemath-admins@…
  • url:
  • admin: tmonteil
  • local sage dev: tmonteil
  • technology used: unprivileged LXC, debian, nginx, certbot, uwsgi, moinmoin, jsmath, docutils
  • formerly hosted at:
  • possible issue in migration: the database of user accounts is synced from trac when this latter is modified (incron)

DockerHub organization

Defunct services

  • purpose: public notebook,
  • state: end of life; redirects to CoCalc
  • volunteers to provide worksheets back to the users: dimpase, tmonteil, vdelecroix


  • purpose: turn pull requests on GitHub into trac tickets
  • contact: robertwb

Last modified 14 hours ago Last modified on Dec 8, 2022, 5:15:10 PM