Source evidence¶

Primary/source link ↗

Notice: August 27, 2026 · effective August 28, 2026 · Rechecked 2026-10-19

Claim: GitHub decommissioned Classroom’s website, APIs, and related services on August 28, 2026. Its May 26 announcement had already stopped new sign-ups. Accounts, repositories, and organizations remain; some Classroom-specific metadata is subject to deletion.

Scope: This removes a course-management and automation layer. It does not remove GitHub itself or establish that all free Actions or Codespaces benefits have ended.

Provider announcement; dated change

Primary/source link ↗

Closed to new users by September 21, 2026 (Greg Chism update received October 20); provider FAQ checked October 8, 2026; exact effective date not stated · Rechecked 2026-10-19

Claim: The FAQ says new sign-ups for the free one-year Pro for Education subscription are no longer available. Previously verified users keep the benefit until their one-year mark, unless replaced with a paid personal subscription.

Scope: Google announced a limited number of these subscriptions on July 18, 2025. The current FAQ establishes withdrawal of the offer, not deletion of education accounts or the end of free Colab. The phrase “quietly pulled” is an interpretation of the FAQ-only notice; the absence of a separate announcement cannot be proved. Free Colab still has variable, non-guaranteed resource limits. Greg Chism reports it was already closed to new users by September 21, 2026. This is an attributed upper boundary, not the exact effective closure date.

Provider policy verifies status; user-reported earlier boundary date

Primary/source link ↗

July 18, 2025

Claim: Google offered a limited number of free one-year Colab Pro subscriptions to verified students and faculty at U.S. higher education institutions.

Scope: The original offer was explicitly limited. It was not a permanent entitlement or a commitment to every future cohort.

Provider launch announcement

Primary/source link ↗

New-account boundary: July 15, 2025 · Rechecked 2026-10-19

Claim: For accounts created before July 15, 2025, the documented EC2 Free Tier benefit lasted 12 months with usage limits and possible overage billing. Newer accounts receive a credit-based free plan lasting at most six months, ending sooner if credits run out; usage cannot exceed the free-plan limits.

Scope: This is the general Free Tier used by students, not a verified six-month change to AWS Educate or Academy. The new plan also changes eligible instances, credits, and spending protection. Remaining credits may last up to 12 months if a user upgrades to a paid plan, subject to terms.

Provider documentation with an explicit before/after table

Primary/source link ↗

Current FAQ checked October 8, 2026

Claim: The free plan ends after six months or exhaustion of credits. Free Tier credits generally expire twelve months after account creation and can apply after an eligible upgrade to a paid plan.

Scope: A six-month free plan is not equivalent to a six-month expiry for every credit or every educational program.

Provider FAQ; confirms distinction between credits and free plan

Primary/source link ↗

Announced August 25, 2022 · effective November 28, 2022 · Rechecked 2026-10-19

Claim: Heroku ended its free Dynos, Postgres, and Redis plans and began scaling down free dynos and deleting free databases on November 28, 2022.

Scope: General-purpose hosting and data services used in teaching. This is not evidence that every later Heroku student credit offer ended.

Provider changelog; dated change

Primary/source link ↗

Provider notice December 6, 2023 · removal August 1, 2024

Claim: Users were notified November 14, 2023. New team creation and updates stopped November 15. Replit removed Teams for Education and deleted its data on August 1, 2024 after an export period.

Scope: The original Replit announcement at blog.replit.com/update-on-teams-for-education was readable through Exa’s indexed copy but returned HTTP 404 during direct verification. This link opens Bucknell’s institutional notice with the same staged timeline. Replit’s broader product continued; the 2023 and 2024 milestones are one product withdrawal.

University service record, corroborating the indexed provider announcement

Primary/source link ↗

Announced May 22, 2025 · effective July 8, 2025

Claim: Glitch ended project hosting and user profiles on July 8, 2025. Code downloads remained available through the end of 2025, with a redirect transition.

Scope: General-purpose creative coding and hosting used in teaching; this is a hosting loss, not a withdrawal of GPU notebooks or an education-only account.

Provider announcement; dated change

Primary/source link ↗

Current provider documentation checked October 8, 2026 · effective date not stated

Claim: Studio Lab is closed to new customers. Existing customers may continue using it; AWS plans security and availability work but no new features.

Scope: The existing free notebook service is not fully shut down. An external documentation-change tracker suggests July 30, 2026, but the current primary notice does not date the change; the deck deliberately uses the observation date.

Provider policy; verified status, uncertain change date

Primary/source link ↗

Current policy checked October 8, 2026 · Rechecked 2026-10-19

Claim: Eligible U.S.-based educators may lead allocations. Educational projects align with individual courses or training periods; they are typically not extended. ACCESS accepts educational uses at all scales with suitable justification. Smaller project requests are reviewed continually; Maximize requests use semiannual review and renewal.

Scope: A pooled teaching-service proposal needs program/provider agreement about structure and eligible uses. An award does not guarantee future approval, permanent student accounts, synchronous GPU availability, or local support staffing.

Official program policy

Primary/source link ↗

Current program page checked October 8, 2026

Claim: Explore, Discover, and Accelerate have published credit limits of 400,000, 1,500,000, and 3,000,000 respectively; Maximize requests resource-specific allocations. Discover explicitly includes large classes and training events. Start smaller and upgrade if needed.

Scope: Limits are not guaranteed awards. Current policy awards up to half of the credit limit initially and the remainder through a justified supplement. Credits are not interchangeable with CPU core-hours or GPU-hours without resource-specific conversion. The deck does not prescribe Maximize merely because the user wants a large allocation.

Official program description

Primary/source link ↗

Current classroom call checked October 8, 2026

Claim: U.S.-based instructors can request resources for undergraduate or graduate AI coursework or short training in any discipline with U.S.-based participants. Prepare a course/resource description of at most three pages plus a lead biosketch. Identify software, compute and storage needs, support, readiness, a preferred provider, and an alternate.

Scope: Only selected providers support this call. Resource match and availability are conditional. Instructors or their teams provide primary student technical support. Course development/testing is also eligible. A central program should assist instructors rather than imply that pilot awards are automatic or unrestricted.

Official classroom opportunity and proposal instructions

Primary/source link ↗

Current resource documentation checked October 8, 2026

Claim: Jetstream2 documents classroom workflows including JupyterHub, reproducible environments, AI/ML, virtual desktops, and web hosting.

Scope: This supports the feasibility of the diagram’s software choices. The pictured service is proposed; it is not a verified deployment. A gateway or hub still needs engineering, operating ownership, and the appropriate allocation.

Resource-provider teaching guide

Primary/source link ↗

Current planning guide checked October 8, 2026

Claim: Plan course duration, student count, instance size, GPU needs, active hours, and storage. Account for idle instances and operational overhead when estimating resource use.

Scope: The calculator uses illustrative demand assumptions, not provider benchmarks. CPU and GPU hours must be mapped to the chosen resource’s accounting; shared-service and course quotas require an actual operating design.

Resource-provider sizing guidance

Primary/source link ↗

April 2025, version 2 · current guidance checked October 8, 2026

Claim: Submit a progress report halfway through the course or training and a final report within 30 days of completion. Report resource use, participation, educational outcomes, and issues.

Scope: The proposed program needs to collect enough course evidence to complete these reports; allocation acquisition is only one stage of delivery.

Official reporting guidance; corroborated by April 2026 newsletter

Primary/source link ↗

Checked October 8, 2026

Claim: The current program finder lists nine non-cyber degree awards: five bachelor’s degrees, MS Data Science, MS Information Science, MA Library & Information Science, and PhD Information.

Scope: BAS Cyber Defense, BS Cyber Operations and MS Cyber Operations are excluded. Certificates, minors and accelerated pathways are not additional degree awards. Platform-to-assignment matches are an instructional assessment, not a college endorsement or tested curriculum deployment.

Official provider / program documentation

Primary/source link ↗

Rechecked October 13, 2026 · Rechecked 2026-10-19

Claim: Personal Free includes 120 core-hours and 15 GB-month; Pro includes 180 core-hours and 20 GB-month. On a 2-core machine those amounts mean 60 and 90 active wall-clock hours. Larger machines spend the quota faster.

Scope: Organizations have no included free quota. Stored codespaces consume storage even when stopped. Without a payment method usage stops at the limit; paid overages depend on billing settings. Use personal ownership deliberately; Classroom’s former organization benefit is not assumed.

Official provider / program documentation

Primary/source link ↗

Rechecked October 13, 2026

Claim: Verified students receive up to 180 core-hours per month on personal accounts, with storage equivalent to GitHub Pro.

Scope: Verification and benefit eligibility must be established before teaching. Some documentation still describes the closed Classroom integration; the recommendation uses only the personal-account benefit.

Official provider / program documentation

Primary/source link ↗

Checked October 8, 2026

Claim: GitHub documents notebook-based ML and JupyterLab. Its GPU machine trial is not generally available.

Scope: Installing CUDA software does not confer a GPU. Treat ordinary free Codespaces as CPU compute; a full desktop game / XR workstation is outside this recommendation.

Official provider / program documentation

Primary/source link ↗

Checked October 8, 2026

Claim: Kaggle offers free GPU notebooks subject to availability. Current notebook documentation lists 12-hour CPU/GPU sessions and 20 GB of saved working space, and references T4 and P100 hardware.

Scope: An older official GPU tips page still says 9-hour sessions and 30 hours/week. Plan short checkpointed labs below nine hours and check the live timer, quota and available hardware. Large-model fit depends on actual VRAM; two GPUs do not automatically pool memory. No classroom concurrency reservation is established.

Official provider / program documentation

Primary/source link ↗

Checked October 8, 2026

Claim: The provider describes a weekly floating GPU quota, with the account/editor showing the current allowance; it can vary with demand and resource availability.

Scope: The historical 30-hour figure is not presented as a guaranteed class entitlement. Extra hours linked to a paid Colab promotion are excluded from the free recommendation.

Official provider / program documentation

Primary/source link ↗

Checked October 8, 2026

Claim: Pages serves HTML, CSS and JavaScript from repositories. GitHub Free supports Pages in public repositories.

Scope: This hosts a browser project; it does not supply server-side application compute or a GPU. Public project hosting is unsuitable for private study records.

Official provider / program documentation

Primary/source link ↗

Checked October 8, 2026

Claim: Published sites may be at most 1 GB, with a soft 100 GB monthly bandwidth limit and deployment / rate limits.

Scope: Large game assets, media archives, persistent databases and multiplayer backends need another service. Free public hosting does not imply private access control.

Official provider / program documentation

Primary/source link ↗

Checked October 8, 2026

Claim: p5.js is a free open-source JavaScript library with a web editor for interactive and audio-visual works, including WebGL.

Scope: Rendering runs on the learner’s device. Device performance, browser capabilities and peripheral access remain course constraints; this is not cloud GPU capacity.

Official provider / program documentation

Primary/source link ↗

Checked October 8, 2026

Claim: Twine supports browser or desktop authoring of nonlinear stories and exports HTML, with optional CSS and JavaScript.

Scope: Suitable for narrative and interaction prototypes, not a replacement for full game-engine or VR labs. Export backups rather than depending on browser storage.

Official provider / program documentation

Primary/source link ↗

Checked October 8, 2026

Claim: The independent provider advertises 15 free execution credits per month, a five-runs-per-15-minute rate limit, and T4 GPUs with 16 GB memory. One credit is one execution.

Scope: Optional tightly bounded CUDA demonstration, not a primary semester GPU environment. This is independent of Codabench, the service the user intended. No classroom concurrency guarantee was verified.

Official provider / program documentation

Primary/source link ↗

Announced March 24, 2022; new groups from December 28, 2022; remaining enforcement August 15, 2026

Claim: GitLab’s staged Free SaaS change limits private top-level groups to five users. Its June 18, 2026 update schedules enforcement on all remaining affected namespaces for August 15, 2026.

Scope: Public groups, self-managed Free and qualifying Education/Open Source programs are exempt. The 2022 and 2026 entries are stages of one restriction, not two vanished services. Earlier proposed rollout dates were revised.

Primary provider / institutional source

Primary/source link ↗

New-account group boundary: January 27, 2026; checked October 10, 2026

Claim: New Free accounts created after January 27, 2026 are limited to three top-level groups. A private Free namespace exceeding five users becomes read-only.

Scope: Groups are organizational containers, not a three-repository limit. The documentation gives June 13, 2023 for older private groups; the announcement separately documents remaining enforcement in 2026. Avoid a universal one-day rollout claim.

Primary provider / institutional source

Primary/source link ↗

Announced January 27, 2025; enforcement delayed to May 29, 2025

Claim: Free workspaces receive a 1 GB aggregate repository storage cap, lose Downloads and Snippets, and have 90-day pipeline-log retention. Over-limit workspaces become read-only.

Scope: The provider update supersedes the original April 28 date. Paid plans are excluded. Inactive free repositories may be archived, with admin restoration; this is not a blanket deletion announcement. Special academic plans must be checked separately.

Primary provider / institutional source

Primary/source link ↗

Checked October 10, 2026

Claim: Current support guidance confirms 1 GB total repository storage across a Free workspace.

Scope: Git storage is distinct from the LFS allowance. Some pricing/billing pages retain per-repository wording; this deck follows the dated change and current support policy, and advises checking the actual workspace quota.

Primary provider / institutional source

Primary/source link ↗

Effective June 17, 2024; checked October 10, 2026

Claim: Cloud Source Repositories is unavailable to new customers. Its free tier included five project-users and 50 GB of storage; organizations already using it before the cutoff are unaffected by the new-access change.

Scope: This is loss of a new free-hosting route, not proof that existing repositories were shut down or deleted. Secure Source Manager is a separate product, not assumed to be a free classroom substitute.

Primary provider / institutional source

Primary/source link ↗

Checked October 10, 2026 · Rechecked 2026-10-19

Claim: GitHub Free still includes unlimited public and private repositories and collaborators for personal accounts and organizations, with limited private-repository features.

Scope: Repository count is not unlimited file storage, build time, premium controls or permanent policy. Classroom shutdown is separate. This counterexample prevents an unsupported claim that free repository hosting universally disappeared.

Primary provider / institutional source

Primary/source link ↗

Checked October 10, 2026

Claim: Qualifying institutions can apply for free Ultimate licenses with unlimited seats, for instruction and non-commercial academic research. Licenses last one year with annual renewal and community support.

Scope: Full-time faculty/staff apply; students do not receive direct institutional licenses. Administrative IT operations are excluded. Eligibility and renewal are conditional; this task verified neither a UArizona license nor an application or deployment.

Primary provider / institutional source

Primary/source link ↗

Checked October 10, 2026

Claim: A Git mirror clone preserves revision history; Git LFS objects must also be fetched. Wikis and selected metadata require additional export paths.

Scope: A Git clone is not a complete course-system backup. Migration archives omit some data and have no documented supported GitHub restore. The proposed service must test its own restore path for LFS, issues, permissions, artifacts and assessment links.

Primary provider / institutional source

Primary/source link ↗

Checked October 10, 2026

Claim: Forgejo documents pull and push mirroring of commits, branches and tags, supporting a proposed managed Git continuity layer.

Scope: A mirror is not an independent backup: deletions can propagate. LFS and non-Git records need separate handling. Hosting, authentication, patching, support and storage cost staff time; no campus installation or capacity has been verified.

Primary provider / institutional source

Primary/source link ↗

Checked October 10, 2026

Claim: Libraries recommend a trusted data repository, such as ReDATA, for citable publicly releasable code/data, while retaining an offline copy. ReDATA integrates with GitHub.

Scope: A curated research deposit is distinct from live Git hosting and private student submissions. Retention, eligibility and storage are purpose-specific; a compute allocation alone is not a durable archive.

Primary provider / institutional source

Primary/source link ↗

Announced in 2026; upcoming November 16, 2026 and after February 19, 2027 · Rechecked 2026-10-19

Claim: OSF will stop creation of new projects and child components starting November 16, 2026. After February 19, 2027, public and private projects become read-only. Existing public projects remain accessible and citable; OSF anticipates eventual removal of private projects with 12 months advance notice.

Scope: Future effective dates fall outside the five-year historical window. OSF Registries and community-run preprint workflows continue. This is withdrawal of an active collaboration/file-storage workspace, not immediate deletion of all OSF content. No private-project deletion date is established.

Primary provider / institutional record

Primary/source link ↗

October 16, 2025 update

Claim: COS made the suspension of new submissions to its generalist preprint server indefinite. Existing preprints remain accessible and can be revised. Community-led services such as SocArXiv and PsyArXiv continue.

Scope: Loss of a generalist submission route, not shutdown of every OSF preprint service or loss of existing papers.

Primary provider / institutional record

Primary/source link ↗

Effective August 25, 2025

Claim: The generalist OSF Preprints server suspended new submissions on August 25, 2025. Existing content and revisions continued; community-run servers were excluded.

Scope: August and October notices are stages of one withdrawal, not two separate lost repositories.

Primary provider / institutional record

Primary/source link ↗

Fee schedule effective May 6, 2025; vouchers no longer accepted from June 2024

Claim: Unsponsored publishing charges are $150 up to 5 GB, $180 up to 10 GB and $520 up to 50 GB. Partner sponsorship covers submissions up to 10 GB; larger submissions incur additional charges under the partner agreement. Any author may request a waiver, but submissions over 10 GB are excluded from waivers.

Scope: A changed funding model and size boundary, not a universal transition from free to paid. Sponsorship and waiver eligibility must be verified for the actual author, journal and institution; no UArizona sponsorship is assumed.

Primary provider / institutional record

Primary/source link ↗

Checked October 10, 2026; no reduction date established

Claim: Free figshare.com accounts provide 20 GB of private storage, a 20 GB individual-file limit and a 500-item account limit. Institutional settings may differ; larger publication needs may require Figshare Plus.

Scope: Current capacity limits, not evidence of a recent cut or closure. Public scholarly publication and private collaboration are different uses.

Primary provider / institutional record

Primary/source link ↗

Checked October 10, 2026; no reduction date established

Claim: Zenodo documents a default 50 GB quota per record and an additional 150 GB allowance distributable across uploads. Its quota page permits multiple records below the default limit.

Scope: An available research-publication route with limits, not evidence of withdrawal. Appropriate research content, record organization, permissions and preservation needs still matter; this is not private course database hosting.

Primary provider / institutional record

Primary/source link ↗

Checked October 10, 2026; no reduction date established

Claim: The free hosted plan includes one site, 500 MB of storage and a limited set of themes and plugins. Larger plans are paid.

Scope: Useful for a small digital-collection or exhibition exercise. Large scans, audio and video can exceed the quota. No recent free-plan reduction was verified; self-hosted Omeka has separate operating costs.

Primary provider / institutional record

Primary/source link ↗

Warning dated January 6, 2026; checked October 10, 2026

Claim: UArizona Libraries warns of intermittent latency and request errors due to high-volume automated traffic, including forced logouts, occasional saving difficulties and temporary restrictions on automated downloads. ReDATA remains the official public research-materials repository with curated deposits and DOIs.

Scope: An availability/automation incident, not a storage-account cut, repository closure or security breach. A current posted warning does not prove uninterrupted failure since January.

Primary provider / institutional record

Primary/source link ↗

Checked October 10, 2026 · Rechecked 2026-10-19

Claim: The Campus Repository is free to campus and provides public access to scholarly publications, presentations, reports, theses, dissertations and related materials. Faculty, researchers and departments can establish collections with Libraries.

Scope: A surviving institutional route. Public deposit requires suitable rights and content; this is not a private assignment-submission system or live application backend. No recent reduction was verified.

Primary provider / institutional record

Primary/source link ↗

Policy effective July 2022

Claim: Google moved education subscriptions to pooled storage in July 2022, with a baseline 100 TB shared across users and accounts, including Drive, Gmail and Photos. Additional capacity and institutional allocation settings depend on the subscription.

Scope: A working-storage policy change affecting preparation and collaboration around repositories. It is not a claim that a library repository lost 100 TB or that UArizona currently has this baseline quota.

Primary provider / institutional record

Primary/source link ↗

A1 cap: February 1, 2024; pooled-storage rollout: contract renewal no earlier than August 1, 2024

Claim: Free Office 365 A1 users are capped at 100 GB of OneDrive storage. Education tenants receive 100 TB baseline pooled storage across OneDrive, SharePoint and Exchange, plus capacity for eligible paid licenses and purchased storage. Administrators may assign lower A1 limits.

Scope: The A1 cap does not apply identically to every education license. The institutional pool and any account quota depend on the actual contract. Working storage is not curated long-term repository stewardship.

Primary provider / institutional record

Primary/source link ↗

FAQ updated April 10, 2023; checked October 10, 2026

Claim: DSpace is freely available under an open-source BSD license. It supports institutional digital objects and export/import of content and metadata through documented formats.

Scope: Free software does not supply free hosting, staff or durable storage. No DSpace free-account reduction was verified. Export formats and restores must be tested against the deployed version.

Primary provider / institutional record

Primary/source link ↗

Checked October 10, 2026

Claim: Lyrasis offers managed ArchivesSpace, CollectionSpace, DSpaceDirect and DuraCloud Preserve hosting. Its subscription model funds hosting support and the open-source communities behind these services.

Scope: Evidence of an operating and stewardship cost, not a dated reduction in a previously free hosting entitlement. No campus subscription or service availability was verified.

Primary provider / institutional record

Primary/source link ↗

New Hobby creation stopped March 6, 2024; retirement April 8, 2024

Claim: PlanetScale retired Hobby on April 8, 2024 and put remaining Hobby databases to sleep. Users needed to upgrade or wake their database for a 24-hour export window.

Scope: Loss of the former free database plan, not closure of PlanetScale or all its paid databases. No perpetual ability to recover an old database is promised.

Primary provider / institutional record

Primary/source link ↗

Effective May 20, 2024 for newly created free databases · Rechecked 2026-10-19

Claim: New free Render PostgreSQL databases expire after 30 days, down from 90. Databases created before the change retained their original expiry date. A 14-day upgrade grace period follows expiry before deletion.

Scope: An explicit duration reduction affecting new free databases. A 30-day database cannot cover a normal semester without migration or paid continuation. It does not establish that free web hosting ended.

Primary provider / institutional record

Primary/source link ↗

Checked October 10, 2026

Claim: Free web services spin down after 15 minutes without inbound traffic and share 750 running instance-hours per workspace per month. Their filesystem is ephemeral. Free Postgres has 1 GB storage, one active database per workspace, 30-day expiry and no provider backups. Free Key Value is in-memory and loses data on restart.

Scope: Current limits must be separated from the dated Postgres reduction. Persistent assessment data must not live solely on a web filesystem or free in-memory store. Quota exhaustion can suspend services; bandwidth/build overages depend on payment and spend settings.

Primary provider / institutional record

Primary/source link ↗

No new signups May 1, 2024; EOL January 27, 2025; blackout February 28, 2025

Claim: ElephantSQL stopped new signups, reached EOL January 27, 2025, then entered a staged brownout. Its customer timeline sets February 28, 2025 as final termination and deletion of all data.

Scope: Full service withdrawal affecting free and paid usage. January 27 is not the final deletion date; the staged dates must not be collapsed. PostgreSQL elsewhere remains available.

Primary provider / institutional record

Primary/source link ↗

Effective May 30, 2025, noon Pacific

Claim: Fauna announced shutdown of the managed database service at noon Pacific on May 30, 2025. Customers had to migrate applications and export data; the FAQ stated accounts and associated data would be permanently deleted afterward.

Scope: Historical provider FAQ read through Exa’s indexed copy; its original URL no longer resolves on a direct check. The separate live provider status record confirms shutdown. This was a full managed-service withdrawal, including Free, not merely a plan cut; announced deletion was not independently audited.

Historical provider FAQ read through indexed copy; live status corroborates shutdown

Primary/source link ↗

May 30, 2025, 12:02 Pacific update

Claim: The provider status page confirmed the service was shut down on May 30, 2025. Its preceding notices said unmigrated applications would cease functioning and no extension was available.

Scope: Corroborates the effective shutdown instead of treating an announcement alone as execution.

Primary provider / institutional record

Primary/source link ↗

Plans deprecated October 7, 2024; checked October 10, 2026

Claim: Fly.io discontinued its old plans for new customers and retained their included free allowances for eligible existing organizations. Those allowances included up to three 256 MB shared-CPU VMs and 3 GB persistent volumes. Existing Legacy Free Hobby has no subscription fee, subject to its terms.

Scope: The October date is the documented discontinued-plan boundary, not proof that every new user had free Hobby until that day. Older changes had already introduced paid Hobby. Do not claim all legacy allowances were revoked.

Primary provider / institutional record

Primary/source link ↗

Checked October 10, 2026; current trial effective date not established

Claim: New organizations have no recurring free hosting tier or monthly free compute allowance. A card-free trial lasts at most two hours of Machine runtime or seven days, whichever comes first; continued billable resources require a card. Some ancillary allowances remain free.

Scope: A current trial is not semester infrastructure. Eligible legacy organizations retain documented allowances; this is not a provider shutdown or evidence that every resource is charged.

Primary provider / institutional record

Primary/source link ↗

Announced June 2, 2023; rollout July 3–August 1, 2023

Claim: Railway replaced its former recurring $5 monthly Starter credits with a one-time $5 trial grant and introduced a $5/month Hobby subscription with included usage. Some qualified existing users received subscription-fee waivers.

Scope: Historical change, not the current entire product. Railway now documents a smaller recurring Free plan; do not claim it has no free tier today.

Primary provider / institutional record

Primary/source link ↗

Checked October 10, 2026; reintroduction date not established

Claim: Railway now offers Free at $0/month with $1 monthly usage credit for small apps, alongside a one-time $5 trial and paid Hobby/Pro. Hobby is $5/month even when resource use is lower than its included $5.

Scope: A counterexample to permanent disappearance of all free usage. A dollar of metered usage is not a promised number of class hours, persistent database capacity or guaranteed course availability. Billing and data-retention terms need checking before deployment.

Primary provider / institutional record

Primary/source link ↗

Announced April 26, 2024; free usage shutdown began May 10; all usage May 31, 2024

Claim: Cyclic disabled new signups immediately and announced it would begin turning off free-tier usage May 10, 2024 and all usage May 31. The provider attributed closure to insufficient sales to sustain the service.

Scope: A general application-hosting shutdown, not an education-account policy. The original provider URL now fails certificate verification; the same dated notice remains on its author’s site. Dates describe the announced staged turn-off; no individual student deployment or data-deletion outcome was inspected.

Dated provider notice preserved by its author; original provider URL has a certificate error

Primary/source link ↗

New accounts from September 4, 2025; checked October 10, 2026

Claim: New accounts use credit-based plans. Free receives 300 credits per month with a hard limit; when credits run out, all web projects on the account pause. Existing eligible pre-September 4, 2025 accounts can retain legacy plans.

Scope: A changed quota model, not a universal removal of free hosting or a measured capacity reduction for every workload. Credit consumption depends on deploys, compute and traffic; old allowances must not be compared with credits as interchangeable units.

Primary provider / institutional record

Primary/source link ↗

Announced September 2024; existing-bucket access requirement from February 3, 2026

Claim: Cloud Storage for Firebase requires a Blaze pay-as-you-go project linked to Cloud Billing, including access to legacy default buckets from February 3, 2026. Without upgrade, users lose read/write and console access; existing bucket data remains. No-cost usage still exists on Blaze.

Scope: Object/file storage, not Firestore database or Firebase Hosting shutdown. Loss of a billing-free access path is different from all usage becoming paid. This current FAQ supersedes older documentation carrying earlier planned deadlines.

Primary provider / institutional record

Primary/source link ↗

Checked October 10, 2026

Claim: Free Pages sites can contain up to 20,000 files with a maximum 25 MiB per asset. Pages Functions consume Workers quota and have separate execution constraints.

Scope: A surviving route for static exhibits and course sites; static hosting does not itself supply a database, general persistent server or archival storage. No recent reduction is claimed.

Primary provider / institutional record

Primary/source link ↗

Checked October 10, 2026

Claim: Workers Free provides 100,000 requests per day and a 10 ms CPU-time limit per invocation. Exceeding the daily quota can return an error. Static-asset requests and other product quotas have separate rules.

Scope: Suitable for lightweight APIs and request handling within limits, not long CPU analyses or arbitrary always-on application servers. CPU time is not elapsed request time.

Primary provider / institutional record

Primary/source link ↗

Documentation updated April 21, 2026; checked October 10, 2026

Claim: D1 Free supports ten databases per account, 500 MB per database, 5 GB aggregate storage and seven days of Time Travel recovery.

Scope: Small SQLite-style web databases. SQL dialect, API, per-query limits and platform integration differ from PostgreSQL/MySQL and are not a drop-in replacement for every database course. Recovery windows do not replace independent exports.

Primary provider / institutional record

Primary/source link ↗

Documentation updated April 21, 2026; checked October 10, 2026

Claim: Workers Free includes five million rows read per day and 100,000 rows written per day for D1, with 5 GB total database storage. Rows scanned count even if a query returns fewer rows.

Scope: Allowance units are rows, not SQL requests or students. Full-table scans can exhaust a class budget faster than indexed queries. No recent cut was verified.

Primary provider / institutional record

Primary/source link ↗

Direct live provider page checked October 10, 2026

Claim: The live plan table provides 100 projects, 100 CU-hours per project monthly, 1 GB storage per project and 20 GB aggregate account storage. Free compute scales to zero after five idle minutes; recovery history is limited to six hours and a data-change allowance.

Scope: A viable small PostgreSQL teaching route with a compute and storage ceiling, not guaranteed always-on capacity. An indexed older free-tier URL returned 0.5 GB, but direct live retrieval of both URLs confirmed 1 GB and the 20 GB total. Recheck the actual account before class; a short history window is not semester backup.

Primary provider / institutional record

Primary/source link ↗

Checked October 10, 2026

Claim: Neon lists Free at $0, 100 CU-hours per project and 1 GB database storage per project, with scale to zero. Paid plans meter usage separately.

Scope: Corroborates the current per-project allowance. Use the plan documentation for the 20 GB aggregate account boundary. Do not use a cached older quota as evidence of a new reduction.

Primary provider / institutional record

Primary/source link ↗

Checked October 10, 2026

Claim: Free includes a 500 MB database per project, 1 GB file storage and two active projects. Free projects pause after one week of inactivity; other API, egress, authentication and function limits apply.

Scope: Useful for small course apps that teach PostgreSQL, auth and backend APIs. Shared organization quotas and inactivity pauses constrain full-class provision and between-term continuity. No recent database free-tier removal is established.

Primary provider / institutional record

Primary/source link ↗

Checked October 10, 2026

Claim: Automatic daily backups are documented for Pro, Team and Enterprise. Supabase recommends regular database exports and off-site backups for Free projects. Database backups exclude the actual objects stored through the Storage API.

Scope: A database dump does not preserve uploaded images, documents or media; export objects separately. No hosted backup or restoration was performed in this research.

Primary provider / institutional record

Primary/source link ↗

Checked October 10, 2026

Claim: Atlas Free supports one cluster per project and 0.5 GB of data plus indexes. It has no managed backups, limits operations and connections, and automatically pauses after 30 days with no connections. MongoDB documents manual dump/restore as an alternative.

Scope: Suitable for small document-database exercises, not sharding, full administration, realistic high-load benchmarks or durable records without separate recovery. Free remains available; no recent withdrawal is claimed.

Primary provider / institutional record

Primary/source link ↗

Checked October 10, 2026

Claim: Hobby remains free for personal, non-commercial use. It lacks paid team collaboration and has resource quotas; exceeding most allowances requires waiting up to 30 days. Functions and platform services have execution limits.

Scope: Suitable for eligible personal student demos; an institution-wide course service or team deployment cannot be assumed eligible under personal-use terms. No recent free-plan withdrawal was verified.

Primary provider / institutional record

Primary/source link ↗

Checked October 11, 2026

Claim: The public instance allows free participation and competition hosting. Its current announcement provides a shared default CPU queue for small jobs, typically result submissions, capped at 20 minutes per job. Organizers are expected to supply their own queue for code submissions.

Scope: This is the service intended by the user, correcting the earlier CUDA benchmark-suite identification. It is a benchmark/evaluation service, not a general GPU notebook entitlement. Shared-queue capacity, storage and class concurrency were not reserved or tested. Exa/web extracted unrelated text for the homepage; direct live HTML returned the actual Codabench announcement and is saved locally. No security incident is inferred from that extraction anomaly.

Primary provider / project documentation; current direct verification

Primary/source link ↗

Checked October 11, 2026

Claim: Organizers can attach physical or virtual machines as compute workers. CPU and GPU worker setup is documented; GPU workers require suitable hardware, NVIDIA support and a compatible competition image.

Scope: GPU support is an integration capability, not a free GPU allocation. Hosting, worker operations, data, isolation and resource limits need separately funded/approved compute. An ACCESS-backed queue is a proposed design, subject to resource, networking and container policies.

Primary provider / project documentation; current direct verification

Primary/source link ↗

Checked October 11, 2026

Claim: Queues dispatch submissions between competitions and internal/external workers. Organizers can create queues, control public access and add collaborators; multiple workers can serve a queue.

Scope: A queue does not create CPU/GPU capacity. Class concurrency and deadline bursts require a tested worker pool. Protect broker credentials and use an appropriately isolated submission environment.

Primary provider / project documentation; current direct verification

Primary/source link ↗

Checked October 11, 2026

Claim: Codabench is the maintained successor to CodaLab Competitions. Sign-up is free; old competition bundles are compatible. Migration requires a new account and export/re-upload of the competition bundle. Leaderboard results do not transfer automatically; submissions must be re-submitted.

Scope: Compatible software is not complete preservation of course history. Export submissions, results and grading records independently; do not promise recovery from an already phased-out service.

Primary provider / project documentation; current direct verification

Primary/source link ↗

End of 2025; project retrospective checked October 11, 2026

Claim: The project’s 2025 retrospective states that CodaLab Competitions and its main servers were phased out at the end of 2025 and development/community activity moved to Codabench.

Scope: A confirmed project-reported platform transition, not disappearance of all free benchmarking. No exact final day or deletion of every archive is established. CodaLab Worksheets is a separate service and is not covered by this finding.

Primary provider / project documentation; current direct verification

Primary/source link ↗

Checked October 11, 2026

Claim: Kaggle offers self-service Community Competitions with no cost to hosts or participants, dataset hosting, live leaderboards and automated prediction scoring. Educators are explicitly eligible to host.

Scope: Competition scoring is not an allocation for arbitrary training or sustained GPU work. Participants develop locally or in separately quota-limited notebooks. Community hosting has no hands-on support; featured/managed competitions have different terms.

Primary provider / project documentation; current direct verification

Primary/source link ↗

Checked October 11, 2026

Claim: Prediction competitions score answer files; hackathon competitions use judges for open-ended work. Hosts can select public/private visibility and link or email-based access. Restricted-email competitions disable notebooks by default to prevent data leaks.

Scope: Invite/private settings must be rehearsed. Do not assume a locked class competition also supplies usable notebook GPUs. A leaderboard score is not a complete course assessment; use approved data and follow account rules.

Primary provider / project documentation; current direct verification

Primary/source link ↗

Checked October 11, 2026

Claim: Current hosted plans are monthly subscriptions: Essentials $125, Core $250, Advanced $850, and Remote Evaluation $100 with organizer-supplied compute. Hosted worker plans include one concurrent evaluation; extra workers are billed separately.

Scope: A functional analogue to Codabench, but not a verified free hosted classroom route. Remote evaluation still carries a hosting fee and compute costs. No historical free-tier withdrawal date is established; these are current prices, not a new dated loss.

Primary provider / project documentation; current direct verification

Primary/source link ↗

Checked October 11, 2026

Claim: The official open-source project supports customized challenge evaluation, remote workers and local Docker deployment.

Scope: Open-source availability does not provide free operated hosting or GPUs. A self-hosted pilot needs an operator, service host, storage, worker isolation, backups and actual license/deployment review.

Primary provider / project documentation; current direct verification

Primary/source link ↗

Checked October 11, 2026

Claim: mybinder.org provides at least 1 GB RAM, up to 2 GB; exceeding 2 GB restarts the kernel. Sessions shut down after ten idle minutes and aim for up to six hours or one CPU-hour of intensive work. The default per-repository concurrent-user cap is 100; larger events can request an increase without a guarantee.

Scope: Useful for short reproducible Python/R demonstrations and small-data workshops; not persistent files, reserved capacity, a GPU entitlement, long training or controlled-data teaching. Download work before the session ends. A funded BinderHub/JupyterHub is the capacity route if this is insufficient.

Primary provider / project documentation; current direct verification

Primary/source link ↗

Checked October 11, 2026

Claim: The live rendered Free plan provides one active free Studio with four-hour restarts. The FAQ offers five introductory credits at registration and 25 more after adding a card, expiring after 12 months. GPU-hour marketing varies by machine/rate and is not a fixed recurring monthly allowance.

Scope: A conditional development/pilot route. Do not repeat older indexed claims of 15 monthly credits or promise 80 GPU hours to every student. The pricing UI warns that free Studios become paid after four hours; confirm current stopping/billing behavior and use checkpoints. No paid signup or account provisioning was performed.

Primary provider / project documentation; current direct verification

Primary/source link ↗

Rechecked October 16, 2026

Claim: Eligible free users receive promotional credits, with eligibility, amount and expiration subject to change. One CPU Studio and the first 10 GB of Drive storage are free; other compute and storage can consume credits.

Scope: No fixed recurring GPU allowance is promised by current billing terms. Academic discounts are paid. Check actual account credit expiry and the four-hour CPU session/restart boundary before class.

Primary provider / project documentation; current direct verification

Primary/source link ↗

Checked October 11, 2026

Claim: Existing ZeroGPU Spaces can be used free. Signed-in Free users receive five GPU minutes per daily quota, resetting 24 hours after first use. Free personal accounts with verified email, older than 30 days and in good standing can host up to two ZeroGPU Spaces. Hosting supports Gradio; organization hosting requires a Team or Enterprise plan.

Scope: For short inference/model-behavior demonstrations, not full notebook training, dedicated GPUs or a semester service reservation. Queue priorities vary. Larger GPU sizing consumes quota faster. This current policy supersedes older descriptions that required PRO for every personal host.

Primary provider / project documentation; current direct verification

Primary/source link ↗

Checked October 11, 2026

Claim: Static Spaces are free. Creating ordinary compute-backed Gradio/Docker Spaces now requires PRO for personal accounts or Team/Enterprise for organizations, except eligible personal ZeroGPU Spaces. CPU Basic has no hourly compute cost, but creation can require a paid plan. Default disk is nonpersistent, and idle free hardware sleeps.

Scope: Do not describe every CPU demo host as a free account route merely because its hourly rate is zero. Static pages run on the visitor device; ZeroGPU is a special bounded exception. No effective date of a creation-policy change is established here.

Primary provider / project documentation; current direct verification

Primary/source link ↗

Checked October 11, 2026

Claim: The provider advertises a free tier for courses up to 50 students, without a card or expiration, including a browser code editor, automated grading, inline feedback and plagiarism detection across 175+ languages.

Scope: A teaching/assessment analogue, not a GPU notebook or a proven replacement for all GitHub Classroom automation. Verify actual free-plan account scope, execution quotas, LMS features, data handling and roster growth before adoption. No UArizona integration or deployment was tested.

Primary provider / project documentation; current direct verification

Primary/source link ↗

Checked October 11, 2026

Claim: The project’s live page offers class creation and grading attached to challenges, individual/team homework and questions beyond challenge performance. It labels the service Work In Progress, version 0.1, and links its open-source project.

Scope: A relevant adjacent workflow to inspect, not a verified production-ready free entitlement. Current support, terms, quotas and Codabench integration were not established; public signup buttons do not prove those properties. Do not promise it as the college grading baseline.

Primary provider / project documentation; current direct verification

Primary/source link ↗

Checked October 12, 2026

Claim: NSF-supported ACCESS connects researchers and educators to compute, cloud, storage, gateways and support. Resource providers supply the underlying systems; access is governed by allocation and provider policies.

Scope: ACCESS is an access/support program, not a single machine. Do not add provider capacity twice when counting ACCESS and Jetstream2 or other participating systems. Grants, account approval and scheduling remain separate.

Primary federal agency / provider documentation

Primary/source link ↗

Checked October 12, 2026

Claim: US-based instructors can request selected NAIRR Classroom resources for AI coursework or training with US-based participants, including any discipline that incorporates AI. Requests specify hardware, storage, dates and support.

Scope: NSF-led cross-agency/partner ecosystem, including in-kind contributions; not every donated service is federally purchased. Instructor/TA technical support is expected. Selected resource availability and approval govern access; this is not an awarded college pilot.

Primary federal agency / provider documentation

Primary/source link ↗

Checked October 12, 2026

Claim: OSG operates distributed computing/data services across contributing institutions. Its funding page names NSF PATh and IRIS-HEP support and in-kind contributions including DOE laboratories.

Scope: Open Science Grid is the consortium/ecosystem. The general-access compute pool is OSPool; OSDF is a data-delivery federation. These are distinct services, not three independent pools of the same capacity. Funding acknowledgments include dated historical context.

Primary federal agency / provider documentation

Primary/source link ↗

Checked October 12, 2026

Claim: US-affiliated academic, nonprofit and government research projects can request OSG access-point accounts. OSPool supports many independent CPU/GPU jobs under fair share; jobs should complete or checkpoint within 20 hours.

Scope: Contributed capacity can interrupt jobs and does not reserve a whole class or finish any job at a promised time. Consult facilitators for educational projects. It is not the natural environment for interactive notebooks or tightly coupled MPI workloads.

Primary federal agency / provider documentation

Primary/source link ↗

Checked October 12, 2026

Claim: The NSF-supported PATh Facility provides dedicated credit-based HTC capacity for NSF-funded research, including larger CPU/GPU, memory, disk and longer jobs than opportunistic OSPool work.

Scope: Separate eligibility/credit process from OSPool. User-facing guarantees in the comparison concern provisioned job resources, not unlimited credits, instant start times, classroom reservations or perpetual storage. MESA funding makes consultation relevant, not automatic approval.

Primary federal agency / provider documentation

Primary/source link ↗

Checked October 12, 2026

Claim: NSF-funded NRP offers eligible US nonprofit research and education shared GPUs/CPUs, hosted notebooks, model APIs, storage and Kubernetes-hosted services. Nautilus is its underlying cluster.

Scope: NRP and Nautilus are two names for one platform layer, not independent capacities. Shared scheduling, account onboarding, quotas and operations still apply. Hosted services can help teaching but are not a preservation or availability guarantee.

Primary federal agency / provider documentation

Primary/source link ↗

Checked October 12, 2026

Claim: NRP documents hosted browser chat and an OpenAI-compatible API for a changing catalog of open-weight language models.

Scope: Model/API access is a distinct product from a GPU training allocation. Models can be added or retired; verify current quotas, supported use and prompt/data handling before class. No account token or API call was tested.

Primary federal agency / provider documentation

Primary/source link ↗

Checked October 12, 2026

Claim: Jetstream2 provides documented course/workshop workflows for virtual machines, standardized environments, virtual GPUs and web applications. Its classroom guidance links instructors to ACCESS allocations.

Scope: An ACCESS resource provider, not a second federal allocation program. Instance runtime has no notebook-style session cap, but allocation duration, credits, GPU availability, support and backups still bound use. Operators must size always-on services explicitly.

Primary federal agency / provider documentation

Primary/source link ↗

Checked October 12, 2026

Claim: Jetstream2 is described as NSF science and engineering cloud infrastructure with CPU, GPU, memory and storage resources.

Scope: Funding provenance establishes public infrastructure, not an approved allocation or a promise of a dedicated GPU per student.

Primary federal agency / provider documentation

Primary/source link ↗

Checked October 12, 2026

Claim: NSF-supported CloudBank Classroom offers browser-based Python/R/C++ tools, persistent student storage and university login. US educators request it through NAIRR Classroom; the page describes one-year allocations with renewal.

Scope: CloudBank brokers commercial cloud resources; it is not a vendor free tier. Approval, provider capacity, awarded budget and configuration govern access. GPU availability is not assumed. The page mixes ACCESS/NAIRR terminology; confirm the actual onboarding route with the provider.

Primary federal agency / provider documentation

Primary/source link ↗

Checked October 12, 2026

Claim: NSF-funded Chameleon supports computer-science research and education using reconfigurable bare metal, VMs and specialized hardware. Approved projects receive time-limited service-unit allocations and make reservations.

Scope: A systems/ML-systems experimentation route, not unrestricted production hosting. Leases, units and renewal differ by resource; current docs distinguish short GPU/bare-metal leases from longer non-GPU VM leases. Student access normally needs an eligible PI/project.

Primary federal agency / provider documentation

Primary/source link ↗

Checked October 12, 2026

Claim: CloudLab supports class projects with isolated root-access environments and resource reservations. Nodes should be held only during active experiments; data on experiment nodes is ephemeral.

Scope: Useful for systems, distributed application and network classes. Large deadline bursts can exhaust shared nodes; backups and reservations must be planned. An experiment reservation is not permission to run a semester-long production service.

Primary federal agency / provider documentation

Primary/source link ↗

Checked October 12, 2026

Claim: CloudLab identifies itself as NSF-supported infrastructure for research into the future of cloud computing.

Scope: Research testbed purpose and project approval distinguish this from ordinary unlimited cloud hosting. Funding and teaching suitability do not establish resource availability on a course date.

Primary federal agency / provider documentation

Primary/source link ↗

Checked October 12, 2026

Claim: FABRIC lists NSF grants supporting distributed compute/storage connected by programmable high-speed networks for networking, distributed computing, machine learning and science experimentation.

Scope: Network/edge experiments, data movement and distributed AI are its defining purpose; it is not just a generic GPU pool. Projects, resource slices and policies must fit the experiment. No course slice was reserved. The former about-page path returned 404 on the direct check; its indexed provider content was reviewed and the live portal is linked.

Primary provider portal and indexed provider about-page content

Primary/source link ↗

Checked October 12, 2026

Claim: NSF NCAR offers no-cost eligible Earth-system science research/instruction, including classroom/workshop allocations for US two- and four-year institutions. It documents individual accounts, compute reservations and setup lead time.

Scope: A domain-specific route for environmental/geospatial data coursework, not a general all-college compute entitlement. Eligible classes need not have a separate external research award. Allocation resource limits and proportional CPU/GPU requests remain provider-specific.

Primary federal agency / provider documentation

Primary/source link ↗

Checked October 12, 2026

Claim: DOE ALCC awards computing at NERSC, ALCF and OLCF through scientific/computational merit review. Universities, industry and agencies may apply; DOE sponsorship is not required for ALCC.

Scope: Mission-aligned research capacity, not a routine classroom account offer. INCITE and other facility routes have different scale/eligibility. Do not treat a past cycle deadline as an open call or combine node-hours with CPU/GPU-hours without conversion.

Primary federal agency / provider documentation

Primary/source link ↗

Checked October 12, 2026

Claim: NASA-supported mission research can request HEC computing through its request-management process; mission-directorate sponsorship and capacity review govern awards.

Scope: Not an open general classroom pool. An allocation is computing time rather than a direct cash grant; some categories are considered case by case without a guarantee. Current request windows and eligibility must be checked.

Primary federal agency / provider documentation

Primary/source link ↗

Checked October 12, 2026

Claim: NHGRI AnVIL combines genomic data access, cloud analysis, notebooks, workflow tools and data-sharing components such as Terra, Dockstore, Bioconductor and Galaxy.

Scope: NIH AnVIL is distinct from Purdue’s ACCESS Anvil supercomputer. Biomedical/domain and controlled-data access policies apply; the federal-funded platform does not make all execution free.

Primary federal agency / provider documentation

Primary/source link ↗

Checked October 12, 2026

Claim: Browsing AnVIL components is free, while notebooks, workflows, storage and egress can incur commercial cloud charges.

Scope: NIH STRIDES discounts, awarded credits or funded training can cover costs only under their actual terms. Historical 2021/22 credit calls are not counted as currently open free offers. Budget ownership and approved data access remain necessary.

Primary federal agency / provider documentation

Primary/source link ↗

Checked October 12, 2026

Claim: NSF announced $83 million in IDSS awards on July 22, 2026. Named projects are FabAID and NDP in Category I; iDLab, BRIDGE, NSDF and MESA in Category II.

Scope: These are data-system investments with computing integration, not six interchangeable free GPU pools. Grant category and announced scope do not establish a user quota, production service level or open access portal. Planning awards are separate.

Primary federal agency / provider documentation

Primary/source link ↗

Checked October 12, 2026

Claim: Integrated Data Systems and Services funds national-scale data infrastructure: new systems, transitions/expansions to operations, and planning. It emphasizes transdisciplinary data integration with existing compute, instruments and repositories.

Scope: A grant program funding service operators, not a direct end-user allocation. Operational and planning stages must stay distinct. It complements ACCESS/NAIRR rather than replacing their resource requests.

Primary federal agency / provider documentation

Primary/source link ↗

Checked October 12, 2026

Claim: MESA identifies NSF IDSS award 2632685 and presents metadata/agent tools, a DuckLake/iRODS stack, and portal applications such as JupyterLab, RStudio, VS Code and a remote desktop over national infrastructure.

Scope: Public project documentation, not a hands-on acceptance test. GPU application builds do not guarantee GPU entitlement. CyVerse/TACC/ACCESS/NAIRR resources retain their own policies. No private proposal, staff plan or internal milestone is used as public service evidence.

Primary federal agency / provider documentation

Primary/source link ↗

Checked October 12, 2026

Claim: The National Data Platform describes a federated data ecosystem, educational activities and compute-ready data/AI services; its page also labels some capabilities as forthcoming.

Scope: Separate the existing catalog/education activity from the funded national expansion and forthcoming features. Provider consultation is needed to establish workspace capacity, course onboarding and actual quotas; no unlimited classroom capacity is claimed.

Primary federal agency / provider documentation

Primary/source link ↗

Checked October 12, 2026

Claim: FabAID describes an NSF-funded open service layer for federated storage, caching, discovery, transformation and workflows supporting data-intensive and AI science.

Scope: Data services complement resource pools; they are not additional allocated GPU-hours or a permanent archive. Current service-specific onboarding, storage responsibility and production guarantees require confirmation.

Primary federal agency / provider documentation

Primary/source link ↗

Checked October 12, 2026

Claim: iDLab describes a browser layer for interactive applications, data access and workflows across ACCESS/NAIRR sites and clouds. Participating sites retain control over their systems.

Scope: An interactive integration layer, not a replacement for site allocations or a long-term archive. Public architecture describes connected and planned services; validate onboarding and course readiness rather than assuming universal immediate access.

Primary federal agency / provider documentation

Primary/source link ↗

Checked October 12, 2026

Claim: BRIDGE describes an NSF-funded national effort built on Apache Texera for reusable datasets, workflows and models, deployable on a community’s own infrastructure or cloud.

Scope: A shareable workflow platform and funded expansion, not a verified no-cost general compute subscription. Labs may need to supply deployment infrastructure, operations and allocations. Prototype and production maturity must be checked.

Primary federal agency / provider documentation

Primary/source link ↗

Checked October 12, 2026

Claim: The 2018 project announcement identifies NSF support for development of OSN as distributed scientific storage/data management infrastructure.

Scope: Historical federal seed funding, not proof that all ongoing pods and operations are wholly federally financed. Storage supports active data movement and sharing, not automatic archival preservation.

Primary federal agency / provider documentation

Primary/source link ↗

Checked October 12, 2026

Claim: OSN documents independent bucket allocations through ACCESS, with a stated 10–50 TB request range, subject to location and available capacity.

Scope: Storage is distinct from CPU/GPU time. Verify actual current quotas and permitted data before applying; a large bucket is not an institutional backup or perpetual preservation agreement.

Primary federal agency / provider documentation

Primary/source link ↗

Checked October 12, 2026

Claim: OSN policy focuses on data in active use for research/education and data transfer/sharing across scientific infrastructure, explicitly distinguishing active data from archives.

Scope: Long-term preservation, retention and recovery require a different stewardship agreement. Treating allocated object storage as archival permanence would overstate this service.

Primary federal agency / provider documentation

Primary/source link ↗

Checked October 12, 2026

Claim: OSDF, an OSG service powered by Pelican, connects data origins and caches to computing. Eligible institutions can connect stores; OSPool access points provide connected working storage and OSN allocations can be linked.

Scope: A delivery/federation layer, not a second storage allocation or GPU pool. Origin policies apply; documentation says it is not appropriate for highly regulated or sensitive data such as PII/HIPAA. Backing storage and preservation must be separately supplied.

Primary federal agency / provider documentation

Primary/source link ↗

Checked October 12, 2026

Claim: Open OnDemand provides browser-based access to remote computing and applications, reducing local installation and command-line barriers.

Scope: A software/gateway product installed by operators, not free computing by itself. Users still need accounts and allocations on the backing system; desktop/visualization apps depend on site configuration.

Primary federal agency / provider documentation

Primary/source link ↗

Checked October 12, 2026

Claim: The project-authored paper describes Open OnDemand and acknowledges NSF grant 1835725.

Scope: Documents federal development support. This historical award is not a claim of perpetual operating funding for every campus installation.

Primary federal agency / provider documentation

Primary/source link ↗

Checked October 12, 2026

Claim: ACCESS Pegasus supports workflow construction/monitoring in notebooks, with HTCondor Annex provisioning jobs against a user’s allocated resources. Active ACCESS allocation holders have a hosted Pegasus account.

Scope: Workflow and scheduling products make capacity usable but do not supply a new independent allocation. Data transfer, containers, site setup and underlying allocation expiry remain requirements; HTCondor’s broader federal-supported work is described by OSG/PATh.

Primary federal agency / provider documentation

Primary/source link ↗

Checked October 12, 2026

Claim: CILogon says NSF/DOE supported its development from 2009–2018; it transitioned to subscription-funded operations in 2019. Basic authentication remains no-charge for academic research projects, while advanced support/IAM uses paid tiers.

Scope: Federally developed identity infrastructure is not wholly federally financed current operations. Login alone does not confer compute entitlement; operators may require paid service support.

Primary federal agency / provider documentation

Primary/source link ↗

Checked October 12, 2026

Claim: Globus provides free file transfer for nonprofit researchers, with subscriptions supporting operations and additional sharing/administrative features.

Scope: Globus connects storage and remote workflows; it does not supply a storage allotment or universal free execution. Federal-supported ecosystem integration and historical development should not be conflated with current subscription funding.

Primary federal agency / provider documentation

Primary/source link ↗

Checked October 12, 2026

Claim: NSF-funded SGX3 (award 2231406) provides limited gateway planning, UX, training and community services. More comprehensive development, hosting and operations are client-funded SGCI engagements.

Scope: Science gateway support is an enabling service, not a universal free hosted application service. Check scope/cost of the proposed engagement and budget the backing resource separately.

Primary federal agency / provider documentation

Primary/source link ↗

Checked October 12, 2026

Claim: CC* describes campus/regional networking, computing, storage/digital archives and strategy awards. Its page currently lists no upcoming due dates and says guidelines await a new publication.

Scope: A funding pathway for infrastructure owners, not an open account pool or a currently verified open proposal window. Resulting campus systems have local access rules; sharing commitments and operating costs matter.

Primary federal agency / provider documentation

Primary/source link ↗

Checked October 12, 2026

Claim: MRI supports acquisition/development of multi-user research instrumentation. Its page describes updates toward a future FY2027 opportunity after review of earlier proposals.

Scope: Campus hardware/equipment funding, not instant national allocations. Computing must meet the actual instrument/solicitation criteria; university proposal limits and a current published call must be checked. No grant application is implied.

Primary federal agency / provider documentation

Primary/source link ↗

Checked October 12, 2026

Claim: NSF’s State and Regional AI Infrastructure Hubs solicitation funds coordination, infrastructure workforce and educator/course development. Consortia must finance acquisition and operation of compute/data/AI infrastructure through their partners.

Scope: A mixed-funding partnership, not NSF-provided hardware or a currently awarded regional pool. It may integrate NRP/PATh resources, but that does not remove consortium funding responsibilities.

Primary federal agency / provider documentation

Primary/source link ↗

Checked October 12, 2026

Claim: SCIPE supports the integration, development and recognition of cyberinfrastructure professionals who help research communities use computational resources and services.

Scope: Workforce capacity rather than end-user compute. A program page is not a confirmed open call or a staffed support promise for this college; inspect current guidelines and awarded local/regional services.

Primary federal agency / provider documentation

Primary/source link ↗

Checked October 12, 2026

Claim: NSF CyberTraining supports adoption of advanced computing/data infrastructure and integration of appropriate skills into undergraduate/graduate teaching and researcher training.

Scope: Funds curriculum, skills and training rather than automatically purchasing all course computing. Current competition status and grant fit need checking; no training award or educator cohort is claimed here.

Primary federal agency / provider documentation

Primary/source link ↗

Checked October 12, 2026

Claim: CyVerse states that core NSF award support ended in 2024. Basic offers 200 normalized compute units/year, 5 GB storage and one concurrent job; free sharing/public links ended June 3, 2025. UArizona users can receive Pro through state TRIF support.

Scope: CyVerse is federally developed and used by federally funded projects, but current account subsidies are mixed; TRIF is state, not federal funding. Pro lists 25,000 units/year, 4 TB and four concurrent jobs, with GPU access by consultation. Published eligibility is not an account or whole-class provisioning test.

Primary federal agency / provider documentation

Primary/source link ↗

Checked October 12, 2026

Claim: U.S. educators can request a managed CPU classroom through Explore ACCESS with a syllabus, roster count and course dates. The provider configures institutional login, persistent student workspaces, Python/R/C++ and notebook/RStudio/VSCode tools.

Scope: This route does not state an AI-course requirement. It is distinct from AI-focused NAIRR Classroom and from general commercial-cloud dollar allocations. Per-student limits and 80-seat capacity are not published here. Its one-year renewal description needs reconciliation with ACCESS education-period policy.

Primary provider/program documentation

Primary/source link ↗

Checked October 12, 2026

Claim: The resource registry updated September 28, 2026 states that the fall 2026 GPU pilot is at capacity and additional requests will be considered beginning in 2027.

Scope: Production status is not an available seat. Consideration in 2027 is not approval or guaranteed GPU availability. The registry rendered an as-of October 4 timestamp when checked; this is a documented capacity notice, not an independent real-time utilization measurement.

Primary provider/program documentation

Primary/source link ↗

Checked October 12, 2026

Claim: The opening sections describe managed Classroom without batch queues; later storage/account sections describe user-created commercial-cloud storage and dollar awards.

Scope: The page contains mixed service scopes. Use the dedicated provider Classroom guide for the pilot design; confirm budget, storage, account and support mechanics for the actual requested service. Do not apply all broker billing terms to the managed hub.

Primary provider/program documentation

Primary/source link ↗

Checked October 12, 2026

Claim: CPU m3.small has 2 vCPU, 6 GB RAM, 20 GB local root disk and costs 2 SU/hour; m3.quad has 4 vCPU/15 GB and costs 4 SU/hour; m3.2xl has 64 vCPU/250 GB and costs 64 SU/hour. GPU g3.medium has 8 vCPU/30 GB, 25% of an A100, 10 GB VRAM and costs 16 SU/hour.

Scope: Published flavor rates underlie this illustrative model. Partial-GPU instance-hours are not full-GPU hours; GPU/CPU exchanges are separate. Larger/newer GPU flavors have different rates and availability. Application fit requires rehearsal.

Primary provider/program documentation

Primary/source link ↗

Checked October 12, 2026

Claim: One ACCESS credit exchanges for one Jetstream2 service unit. Resource use is charged at the chosen flavor rate; CPU, large-memory and GPU resources are distinct.

Scope: This conversion is provider-specific. Do not transfer these rates to CloudBank, NRP, CyVerse or OSPool. Usage reporting can lag; monitor local consumption and maintain headroom.

Primary provider/program documentation

Primary/source link ↗

Checked October 12, 2026

Claim: Default CPU quota is 150 vCPU, 585 GB RAM and ten floating IPs; the GPU resource default is 64 vCPU, 250 GB RAM and four floating IPs. Quotas scale above resource-specific allocation thresholds and justified increases can be requested.

Scope: Total credits do not guarantee concurrency. The 80-seat dedicated model needs 164 CPU vCPU with its controller; the shared-worker model needs 196. The eight fractional GPU slots use 64 GPU-resource vCPU. Verify awarded quotas, flavor availability and private networking rather than assuming eight public GPU addresses.

Primary provider/program documentation

Primary/source link ↗

Checked October 12, 2026

Claim: Jetstream2 offers attached volumes, shared filesystems and object storage; replicated storage and provider snapshots do not replace independent offsite backups.

Scope: Some multi-instance shared filesystem workflows, particularly metadata-heavy/locking applications, require policy and architecture review. Independent restore, retention and deletion controls need a college owner. Persistent working storage is not archival preservation.

Primary provider/program documentation

Primary/source link ↗

Checked October 12, 2026

Claim: The default Jetstream2 storage cap is 1 TB (1,000 GB); request and justify additional storage through the appropriate storage resource.

Scope: The modeled student homes and shared data total 2 TB, excluding root disks, images, logs and snapshots. Credits alone do not automatically increase that storage limit.

Primary provider/program documentation

Primary/source link ↗

Checked October 12, 2026

Claim: Expired or overdrawn allocations lose access; instances are shelved after ten days and unresolved resources are destroyed after thirty days.

Scope: The grace period is a recovery window, not a funded continuation service. Schedule export, backup and renewal decisions before expiry. Do not promise permanent course servers or recoverability after destruction.

Primary provider/program documentation

Primary/source link ↗

Checked October 12, 2026

Claim: NRP explicitly offers educators hosted or private JupyterHub, GPU resources, hosted language-model services and Coder IDEs.

Scope: These are different products with different permissions, quotas and operating duties. Education availability is not a reserved GPU for each learner or a campus production service level.

Primary provider/program documentation

Primary/source link ↗

Checked October 12, 2026

Claim: The hosted hub uses institutional CILogon login and selectable hardware; persistent home folders initially have 5 GB, with enlargement by request.

Scope: The 20 GB/student model needs an approved increase or a smaller assignment footprint. Institutional login documentation is not a verified UArizona roster/provisioning flow. This page lists NSF funding acknowledgments.

Primary provider/program documentation

Primary/source link ↗

Checked October 12, 2026

Claim: Ordinary interactive pods have a six-hour maximum unless a namespace exception is approved; long-lived services need approved exceptions. NRP is not archival storage and unused volumes may be purged after six months without notification.

Scope: Do not impose ordinary-pod limits on every hosted hub without confirming its exceptions. Shared GPUs have utilization requirements; idle GPU deployments are not a classroom reservation strategy. Confirm class quota, persistence, hub-specific lifecycle and data terms.

Primary provider/program documentation

Primary/source link ↗

Checked October 12, 2026

Claim: OSPool supports instructor-led events with guest notebooks or facilitated full accounts. Guest sessions time out after four hours and may lose files; full accounts fit multi-day/semester workflows and known rosters. An event includes a short OSG-policy introduction.

Scope: Full accounts are normally disabled several days after the event; continuation needs agreement. Instructors rehearse materials first. Free throughput jobs are not reserved synchronous notebook/GPU capacity; licensed, long or multi-core workflows may be poor fits.

Primary provider/program documentation

Primary/source link ↗

Checked October 12, 2026

Claim: OSG working filesystems are not backed up; users retain essential copies elsewhere. Privacy-sensitive/proprietary data may not be stored or computed on OSG-managed resources. Persistent/intensive computation belongs in submitted jobs, not access points.

Scope: Use public or synthetic teaching inputs. Independent/checkpointable jobs have fair-share latency and may be interrupted. Required class deadlines need a local or other tested fallback.

Primary provider/program documentation

Primary/source link ↗

Checked October 12, 2026

Claim: PATh eligibility is tied to an accepted/active or planned/pending NSF award in listed affiliated programs; staff can provide startup credits for workflow prototyping.

Scope: IDSS is not explicitly listed on the checked page. MESA funding alone does not establish eligibility; seek provider/program-officer confirmation before building a course dependency. Absence from the list is not proof of permanent exclusion.

Primary provider/program documentation

Primary/source link ↗

Checked October 12, 2026

Claim: After prototyping, full PATh credits are requested through the relevant NSF program officer using an award reference and a short technical justification of jobs, cores, memory, runtime and I/O.

Scope: This is separate from general OSPool education access. No request was sent and no startup or full credits were obtained. An instructor course is not automatically covered by an existing research award.

Primary provider/program documentation

Primary/source link ↗

Checked October 12, 2026

Claim: MESA describes an alternative portal over the user’s CyVerse data, applications and analyses; sign-in reads the existing teams and resource quotas.

Scope: The portal does not create a duplicate compute allowance. Public documentation is not a signed-in entitlement or load test. Distinguish federally funded IDSS development from underlying state-funded or subscription-funded CyVerse accounts.

Primary provider/program documentation

Primary/source link ↗

Checked October 12, 2026

Claim: The portal documents CPU/GPU application variants, launch options and linked Discovery Environment/OSG/Tapis workflows. Its GPU application description names Nvidia A16 nodes.

Scope: A GPU launch option does not prove permission, quota, class-wide capacity or access to the Jetstream2 A100 flavor modeled separately. Confirm the selected app, runtime, image and data-save behavior.

Primary provider/program documentation

Primary/source link ↗

Checked October 12, 2026

Claim: Interactive applications have a time limit that can be extended; files intended for retention belong under ~/data-store. Save & Exit retains outputs; Terminate can discard unsaved session data.

Scope: Rehearse the exact app save/exit/restart/export path. The portal and Data Store are workflow/working-data services, not an independent campus backup or approved archival deposit.

Primary provider/program documentation

Primary/source link ↗

Checked October 12, 2026

Claim: Instructors can request class/workshop resources, select services, assign organizers and enroll/approve student accounts with institutional addresses. Typical first-Tuesday maintenance should be considered.

Scope: The subscription page requires Pro/Commercial instructor access for workshops and mentions enrollment limits without giving a numeric limit in its current FAQ. Confirm student tiers, class limits and scheduled service windows. One instructor Pro account does not create 80 simultaneous student jobs.

Primary provider/program documentation

Primary/source link ↗

Checked October 12, 2026

Claim: Explore requests need a work summary, PI/co-PI CV or résumé PDFs and project metadata. CloudBank’s provider guide additionally asks for course syllabi, enrollments and dates.

Scope: Use the current Explore/provider checklist, not the separate Maximize document requirements. The generated request PDF does not substitute for final syllabus or CV attachments.

Official program / institutional documentation

Primary/source link ↗

Checked October 12, 2026

Claim: Campus HPC documents Puma class groups, shared faculty research/class time allocations, unpredictable queues and instructor-led student help. Consultants can assist instructors but do not provide individual support to all students.

Scope: A documented local alternative, not confirmed account/time quota or reserved classroom capacity. Assess local access honestly before requesting national resources; GPU and deadline priorities are not guaranteed.

Official program / institutional documentation

Primary/source link ↗

Checked October 12, 2026

Claim: Rental storage lists $47.35/TB/year, billed for the fiscal-year maximum without proration. It is not backed up, though nightly snapshots may allow recent-file recovery. Controlled data is excluded.

Scope: The 3 TB/$142.05 example is capacity rent only, not an approved classroom backup service. Verify eligibility, billing and classification; student work/grades are not authorized for this destination by this report.

Official program / institutional documentation

Primary/source link ↗

Checked October 12, 2026

Claim: R-DAS provides up to 5 TB per PI group for open research data, with campus/VPN access and PI/group setup. It is separate from HPC-mounted filesystems.

Scope: Potential no-cost location to verify, not a student-by-student entitlement, regulated/private-record destination or independent backup strategy. The site does not request an allocation or approve data placement.

Official program / institutional documentation

Primary/source link ↗

Checked October 12, 2026

Claim: Tier 2 lists a subsidized first TB of active data, $23/TB/month above that, subsidized transfer, and cold storage/restore stages after inactivity. It excludes controlled data and requires a PI/billing account.

Scope: The $220.80 six-month comparison assumes 1.6 TB of billed active overage; actual object tiers/charges vary. Cold restores may delay access, so keep a warm independent copy. No classroom data authorization or billing setup is verified.

Official program / institutional documentation

Primary/source link ↗

Checked October 12, 2026

Claim: Libraries distinguishes general working storage from preservation and recommends multiple copies, independent media/location, integrity checks and restore tests. Research storage destinations have data-classification limits.

Scope: The pilot needs its own approved data map and retention schedule. Institutional documentation is not evidence that any pilot backup, grade export or repository deposit has succeeded.

Official program / institutional documentation

Primary/source link ↗

Public institutional description checked October 12, 2026

Claim: The institutional course description identifies INFO 521: Introduction to Machine Learning as a three-unit course in machine-learning methods and their application.

Scope: Supports the public course title and conceptual fit only. It does not establish a future offering, enrollment, assigned instructor, syllabus approval or consent to the computing pilot. No private syllabus or intranet content is reproduced.

Institutional course description (indexed primary page)

Primary/source link ↗

Public institutional description checked October 12, 2026

Claim: The institutional course description identifies LIS 671: Digital Curation and Digital Preservation as a three-unit course addressing digital-information work in libraries, archives and records management.

Scope: Supports the public course title and conceptual fit only. It does not establish a future offering, enrollment, assigned instructor, syllabus approval or consent to the computing pilot. No private syllabus or intranet content is reproduced.

Institutional course description (indexed primary page)

Primary/source link ↗

Checked October 13, 2026

Claim: Free, open-source assignment distribution and grading alternative to GitHub Classroom, supported by the Fifty Foundation; project license is GPL-3.0.

Scope: An independently maintained successor, not a GitHub-operated replacement or an institution-owned hosted service. Documentation fit does not establish classroom adoption.

Primary project documentation

Primary/source link ↗

Checked October 13, 2026

Claim: Hosted static web app or local CLI coordinates GitHub organization teams, repositories, rosters, assignments and scores; grading runs through GitHub Actions.

Scope: Course state can live in our institution-controlled GitHub organization. Hosted app stewardship, GitHub service availability and local staffing remain dependencies; ACCESS integration is not demonstrated.

Primary project documentation

Primary/source link ↗

Checked October 13, 2026

Claim: Requires a GitHub Team or Enterprise organization. Verified teachers can request an education upgrade for their specific organization.

Scope: Personal teacher verification does not automatically upgrade the organization. Confirm plan, enterprise OAuth policies and actual organization ownership before adoption; no paid upgrade is authorized.

Primary project documentation

Primary/source link ↗

Checked October 13, 2026

Claim: Open-source web app can be self-hosted. Default OAuth exchange and archive proxies use a Fifty Foundation Cloudflare Worker; deployments can configure their own proxy.

Scope: Self-hosting is an option, not an existing UArizona service. Authentication, proxy traffic, browser token handling, maintenance and recovery need review and available operator time.

Primary project documentation

Primary/source link ↗

Checked October 13, 2026

Claim: Autograding consumes GitHub Actions resources, with controls needed for workflow usage and spending.

Scope: Actions quotas and charges are separate from Codespaces workspace compute; Classroom 50 adds no Codespaces entitlement. Verify actual billing ownership and spend controls before required use.

Primary project documentation

Primary/source link ↗

Checked October 16, 2026 · Rechecked 2026-10-19

Claim: $30 of compute per workspace per month on Starter; up to three seats and ten concurrent GPUs. Functions, Sandboxes and Notebooks use CPU/memory/GPU billing; Shared Endpoints tokens are excluded from included compute, effective September 1, 2026.

Scope: Free subscription does not mean unlimited compute. GPU, CPU and memory share the allowance; startup/warm time, region/execution multipliers and other charges matter. Workspace concurrency is not reserved capacity or a class roster.

Primary provider documentation; direct pricing/terms where available

Primary/source link ↗

Checked October 16, 2026 · Rechecked 2026-10-19

Claim: A payment method is required to use Modal. Usage above applicable credits and subscription fees can be automatically charged.

Scope: Not a no-card classroom default for this zero-cash program. An approved institutional payment arrangement or confirmed grant exception must precede any canary; no personal or student card requirement is proposed.

Primary provider documentation; direct pricing/terms where available

Primary/source link ↗

Checked October 16, 2026

Claim: Workspace budgets cap usage before credits; a separate workspace spend limit caps net charges after credits. Without a custom spend limit, the default is the usage limit less credits. Environment budgets require Team/Enterprise.

Scope: Explicitly review both limits and excluded services. A default usage limit is not a zero-out-of-pocket setting. Verify actual stop behavior and billing attribution in an authorized synthetic canary; documentation is not a tested billing guarantee.

Primary provider documentation; direct pricing/terms where available

Primary/source link ↗

Checked October 16, 2026

Claim: Modal offers an academic application route; its pricing page advertises up to $10,000 in credits for graduate students, labs and researchers.

Scope: Application-based credits, not an ACCESS award, received funding, or a promised class-wide entitlement. Confirm course eligibility, seats, duration, payment requirements and allowed products in writing before counting any grant.

Primary provider documentation; direct pricing/terms where available

Primary/source link ↗

Checked October 16, 2026

Claim: Direct current plan table lists Developer at $20/month with $20 in credits each month and one seat; Team is $89/month plus usage. Monthly included credits expire at renewal.

Scope: This is a paid subscription, not free $20 compute. The extracted page omitted the plan table; the direct HTML was checked. Earlier free-credit blog language does not establish current eligibility.

Primary provider documentation; direct pricing/terms where available

Primary/source link ↗

Checked October 16, 2026

Claim: Prepaid workspaces require credits to build/deploy. Active container execution, initialization and configured warm time are billed; reserved machines bill until released.

Scope: Free included storage does not provide free GPU execution. Open-source Beta9/BYOC still needs a funded host and operator; no ACCESS integration or no-cost campus deployment has been demonstrated.

Primary provider documentation; direct pricing/terms where available

Primary/source link ↗

Checked October 16, 2026

Claim: The June 27, 2026 provider comparison described a free Developer plan and $30/month of credits.

Scope: Historical marketing conflicts with the current $20/month Developer plan table checked October 16. Current direct pricing takes precedence; effective change date and account grandfathering are unknown. Do not use competitor price judgments as independent evidence.

Primary provider documentation; direct pricing/terms where available

Primary/source link ↗

Checked October 16, 2026

Claim: Hobby has a free subscription with three seats and three deployed apps; GPU/CPU/memory remain metered. Current pricing includes the first 100 GB of storage.

Scope: No recurring free GPU compute allowance was established. Earlier $30 promotional-credit copy is not a current monthly grant. No subscription fee is different from no usage charge.

Primary provider documentation; direct pricing/terms where available

Primary/source link ↗

Checked October 16, 2026

Claim: Trials are discretionary, time-limited and may require billing details; subscription billing can start at trial end if not cancelled.

Scope: Do not count a possible trial as semester capacity. Confirm the actual offer, expiration and payment transition before use; no trial was activated.

Primary provider documentation; direct pricing/terms where available

Primary/source link ↗

Checked October 16, 2026

Claim: Runpod uses prepaid credits; a new Pod needs at least an hour of credit for its configuration. Stopped Pod storage still costs money, and depleted balances can lead to deletion.

Scope: Paid comparison only; no generally available recurring free allocation was verified. Storage supports active workloads, not archival preservation. Optional promotions are not an institutional award.

Primary provider documentation; direct pricing/terms where available

Primary/source link ↗

Checked October 16, 2026

Claim: Select models can be tried without payment for a limited amount before billing is required. Public model inference is distinct from private models/deployments, whose setup, active and idle time can be billed.

Scope: A short model demonstration is not a fixed monthly grant or arbitrary GPU notebook/training entitlement. No stable free allowance was established for required class work.

Primary provider documentation; direct pricing/terms where available

Primary/source link ↗

Checked October 16, 2026

Claim: Current pricing lists no monthly Inference Providers credits for Free users; purchased credits or a paid subscription are required. Paid Pro/Team/Enterprise plans include separate credits.

Scope: This is the routed inference API, not the ZeroGPU/Spaces daily allowance. Do not infer a historical withdrawal date or universal closure from this current quota. General marketing and older snippets still describe free-tier access.

Primary provider documentation; direct pricing/terms where available

Primary/source link ↗

Checked October 16, 2026

Claim: The accessible landing page advertises 150 hours/month with GPU access and no credit card.

Scope: Do not interpret this as 150 dedicated GPU-hours. Device split, current new-account access, storage, retention and concurrency were not confirmed. The current pricing route emphasizes metered hosted resources; this remains an unverified lead.

Primary provider documentation; direct pricing/terms where available

Primary/source link ↗

Checked October 16, 2026

Claim: Current hosted pricing lists hourly CPU/GPU resources and storage charges, alongside contract enterprise/operator offerings.

Scope: Reconcile the separate 150-hour landing claim before recommending a free class route. No signup, current free entitlement or provider reservation was tested.

Primary provider documentation; direct pricing/terms where available

Primary/source link ↗

Checked October 16, 2026

Claim: Free CPU and M4000 Free GPU machines are listed for the Free Gradient plan, with 5 GB included storage. Paid GPU machine types and higher subscription tiers are separate.

Scope: Only explicitly free machine types qualify. Shared availability, old GPU/software compatibility, storage overages and actual account/payment setup need checking; no free seat or private class service is reserved.

Primary provider documentation; direct pricing/terms where available

Primary/source link ↗

Checked October 16, 2026

Claim: Free-machine notebooks have a maximum six-hour auto-shutdown timeout.

Scope: Do not apply the marketing page generic 12-hour timer to free GPUs. Work must checkpoint/export within the free machine limit; availability is not guaranteed.

Primary provider documentation; direct pricing/terms where available

Primary/source link ↗

Checked October 16, 2026

Claim: Provider documentation says free-plan free-machine notebooks are public, one free notebook can run at a time, and a one-hour idle interval can shut it down.

Scope: Use only approved public/synthetic teaching content. A private workspace account label does not mean the notebook is private. New-account provisioning and payment requirements remain untested.

Primary provider documentation; direct pricing/terms where available

Primary/source link ↗

Checked October 16, 2026

Claim: Students can start with a CPU Studio; free CPU sessions have a four-hour restart boundary. Eligible academic discounts are paid, not an unlimited free GPU grant.

Scope: Read promotional GPU hours and signup-credit examples alongside billing terms: eligibility, grants and expiration can change. No new-account GPU allowance was tested; avoid promising a fixed monthly credit value.

Primary provider documentation; direct pricing/terms where available