College of Information ScienceComputing Resources Working Group · Point people: Barney Maccabe and Greg Chism
Detailed platform directory¶
Supplemental reference · Browse supplements · Current report
For college and university routes, start with the working-group inventory. This detailed directory supports comparison and the compute case study. Start with the work you need to do. Availability does not establish eligibility, capacity or classroom readiness.
| Need | Start here | Main limit |
|---|---|---|
| Small CPU notebooks and code | Codespaces / Binder / classroom options | Monthly caps, temporary sessions and no class reservation |
| Preliminary GPU benchmarks | Kaggle or free Colab | Variable hardware, quotas and queues |
| Planned CPU + GPU classroom baseline | ACCESS request | Award, provider match and classroom checks pending |
| Research batches, notebooks or data services | Federal platforms | Project eligibility and operating model differ |
| Serverless jobs or hosted inference | Modal and alternatives | Credits, card requirements and paid conversion |
| Assignments and evaluation | Classroom 50 / Codabench | Workflow tools do not supply an unrestricted compute allocation |
| Repositories, apps and databases | Continuity options | Preservation, always-on hosting and compute are different needs |
Not sure how much? Scope your needs →
How to choose¶
- Define the smallest useful workload, software and outputs.
- Match CPU, memory, GPU/VRAM, storage and interactive or batch use.
- Check eligibility, permitted data, payment requirements and the whole-term access window.
- Measure, test recovery and name support before making it required.
Evidence: the directory reflects dated primary-source reviews, mostly October 8–19, 2026. Check the linked sources before adoption. No signed-in entitlement or provider capacity was tested.