Intel
intel.com · Compute · 3 records · JSON
- Intel Tiber Developer Computetrialemailno cardphoneDretention-clamped
- Intel Liftoff Computefails: identityinstitutionno cardDwrite-gated
- Intel Developer Cloud Computefails: quotaemail?card?phoneRwrite-gated
Intel Tiber Developer Compute
trialemailno cardphoneDretention-clamped
| Free tier | Free sandbox for oneAPI work: 120 days of access with extensions available, 192 GB RAM, 220 GB of file storage, remote desktop for the oneAPI Rendering Toolkit, VS Code integration and a Linux terminal, across Intel Xeon Scalable CPUs, Intel Iris Xe MAX GPUs and Stratix 10 / Arria 10 FPGAs. unit GiB; metered on wall-clock; time-boxed-access |
|---|---|
| Price | none stated |
| Per-object cap | not applicable |
| Retention | the account expires after 120 days and the hardware is pre-production or retired silicon, so the access is a portability test rather than a machine to hold a workload on; the separate Intel Developer Cloud console lane has no free instances at all. |
| Egress | not stated |
| Identity | email no payment is taken for the JupyterHub batch lane: Intel staff state 'there are currently no free instances available for the Standard tier in the Intel Developer Cloud Console' while JupyterHub batch instances remain accessible without payment. The account form's fields are not described in any evidence row, so whether an email, phone number or ID document is required is unknown, and no card requirement or hold is stated: unknown. |
| Limits |
the account expires after 120 days and the hardware is pre-production or retired silicon, so the access is a portability test rather than a machine to hold a workload on; the separate Intel Developer Cloud console lane has no free instances at all. |
| Binding | retention-clamped the account expires after 120 days and the hardware is pre-production or retired silicon, so the access is a portability test rather than a machine to hold a workload on; the separate Intel Developer Cloud console lane has no free instances at all. |
| Interface | rest inferred from the tooling the provider documents; not probed |
| Tooling | not stated |
| Composes with | the 120-day clock and the retired GPU generation are what cap it. |
| Reliability | no reliability event recorded |
| Notes | This is a refutation-shaped pair and must be recorded as both halves. Absent from dossier/compute/ before this record. The page's announcement feed is stale (last entry 2023-02-03), which is a warning that the 120-day claim may not be honoured on signup; a probe with a real account would settle it. |
| Evidence rung | documented |
| Checked | 2026-10-22 (live); stale on 2026-11-21 |
Evidence (3)
| date | source | what it proved |
|---|---|---|
| 2026-10-22 | devcloud.intel.com/oneapi/home/ | '120 days of access (extensions available)', '192 GB RAM', '220 GB of file storage', and CPU/GPU/FPGA hardware list, quoted |
| 2026-10-22 | github.com/intel/vscode-oneapi-devcloud-connector | End-of-Life notice: the DevCloud connector for oneAPI is discontinued in the 2025.0.0 release and points at Intel Tiber Developer Cloud as the alternative |
| 2026-10-22 | community.intel.com/t5/Intel-Tiber-Developer-Cloud/Standard- | Intel staff reply: 'there are currently no free instances available for the Standard tier in the Intel Developer Cloud Console'; JupyterHub batch instances remain accessible without payment |
More fields (1)
{
"wave2": {
"class": "refutation",
"free_tier_kind": "time-boxed-access",
"shape": {
"vcpu": null,
"ram_gib": 192,
"gpu_class": "Intel Iris Xe MAX",
"gpu_count": 1
}
}
}Unknown or withheld values (9)
$.chainingpartly-held$.egress.meteredegress-unknown$.egress.termsnot-stated$.notespartly-held$.per_object_cap.notesprocess$.per_object_cap.statednot-applicable$.reliability_notenone-observed$.retention.notesprocess$.toolingnot-stated
Intel Liftoff Compute
fails: identityinstitutionno cardDwrite-gated
| Free tier | The programme promises 'Free cloud credits for the Intel Tiber AI Cloud' and 'Credits from cloud service providers', with 'No Fees, No Equity Requirements, No Technology Restrictions', but the population is companies: 'Intel Liftoff for startups is open to early-stage AI and machine learning startups.' No credit amount, no expiry and no hardware quota is published anywhere on the page. The live URL now redirects to the generic Intel Developer Zone overview, so the terms are quoted from the 2025-06-12 capture. unit none; metered on wall-clock; unpublished-credit |
|---|---|
| Price | none stated |
| Per-object cap | not applicable |
| Retention | not applicable |
| Egress | not stated |
| Identity | institution not published |
| Limits |
the application is reviewed and the unit is a startup, so the gate is a company identity and an approval, not a quota. |
| Binding | write-gated the application is reviewed and the unit is a startup, so the gate is a company identity and an approval, not a quota. |
| Interface | unknown inferred from the tooling the provider documents; not probed |
| Tooling | not stated |
| Composes with | It would chain with the free Intel Developer Cloud allowance if the client had a company, since both spend one Tiber account. It does not chain for an individual. |
| Reliability | no reliability event recorded |
| Notes | The number is null because Intel publishes none, and that absence is the finding. An individual is not excluded by a sentence; the programme is addressed to startups and reviewed. What would settle individual eligibility: the application form's entity field, which returned 403 or a redirect on every route tried. |
| Evidence rung | documented |
| Checked | 2026-10-22 (live); stale on 2026-11-21 |
Evidence (4)
| date | source | what it proved |
|---|---|---|
| 2026-10-22 | web.archive.org/web/20250612171913/https://www.intel.com/con | archived 2025-06-12 capture: 'Intel Liftoff for startups is open to early-stage AI and machine learning startups' and 'Free cloud credits for the Intel Tiber AI Cloud', both quoted |
| 2026-10-22 | www.intel.com/content/www/us/en/developer/tools/oneapi/lifto | read today the URL resolves to the Developer Zone overview, which carries no programme terms |
| 2026-10-22 | ai.cloud.intel.com/solutions/startups/ | the Tiber AI Cloud startups page returned HTTP 530 to the broker, so current terms could not be read |
| 2026-10-22 | community.intel.com/t5/Blogs/Tech-Innovation/Artificial-Inte | Intel's blog names two startup tracks, Catalyst and Community, and states credits go to startups |
More fields (1)
{
"wave2": {
"class": "hardware-vendor-programme",
"free_tier_kind": "unpublished-credit",
"shape": {
"vcpu": null,
"ram_gib": null,
"gpu_class": "Intel Gaudi / Xeon",
"gpu_count": null
}
}
}Unknown or withheld values (10)
$.egress.meteredegress-unknown$.egress.termsnot-stated$.identity_cost.detailprocess$.interfaceinterface-unknown$.per_object_cap.notesprocess$.per_object_cap.statednot-applicable$.reliability_notenone-observed$.retention.notesprocess$.retention.statednot-applicable$.toolingnot-stated
Intel Developer Cloud Compute
fails: quotaemail?card?phoneRwrite-gated
| Free tier | No free instances. Intel staff state the Standard tier has no free instances since the migration to the Intel Developer Cloud console, and instances are reservable only on Premium and Enterprise; free access that remains is limited to JupyterHub batch-processing training notebooks. unit none; metered on wall-clock; none |
|---|---|
| Price | none stated |
| Per-object cap | not applicable |
| Retention | not applicable |
| Egress | not stated |
| Identity | email (placeholder) unverified: no page stating the signup requirement was read; the record's evidence covers the absence of free instances, the account tier that blocks a reservation, and the decommissioning of the service, and names no email, phone, card, ID document or institution — the gate it does establish is a paid service tier, not an identity check |
| Limits |
reserving an instance requires the Premium or Enterprise service tier, so the free lane stops before a machine is allocated. |
| Binding | write-gated reserving an instance requires the Premium or Enterprise service tier, so the free lane stops before a machine is allocated. |
| Interface | rest inferred from the tooling the provider documents; not probed |
| Tooling | not stated |
| Composes with | nothing composes here: the free lane is a JupyterHub training notebook, not a reservable machine. |
| Reliability | no reliability event recorded |
| Notes | Recorded separately from the oneAPI sandbox because they are different products with different answers, and the corpus would mislead a reader if it merged them. The console documentation page (console.cloud.intel.com/docs/tutorials/plans.html) returned broker 530 twice, so the vendor-side planning page could not be read; the community replies are the evidence. This is a refutation of the 'Intel gives free Gaudi time' belief. |
| Evidence rung | reported |
| Checked | 2026-10-22 (live); stale on 2026-11-05 |
Evidence (3)
| date | source | what it proved |
|---|---|---|
| 2026-10-22 | community.intel.com/t5/Intel-Tiber-Developer-Cloud/Standard- | Intel support reply, quoted: 'there are currently no free instances available for the Standard tier'; JupyterHub batch instances are accessible without payment |
| 2026-10-22 | community.intel.com/t5/Intel-Tiber-Developer-Cloud/Insuffici | 'you cannot reserve any instance if you are in a Standard account. The instance is only available for Premium and Enterprise only' |
| 2026-10-22 | community.intel.com/t/unacceptable-response-for-my-pull-requ | Intel reply that the Developer Cloud 'has been formally discontinued, and the infrastructure fully decommissioned' with customer data sanitised and unrecoverable |
More fields (1)
{
"wave2": {
"class": "refutation",
"free_tier_kind": "none",
"shape": {
"vcpu": null,
"ram_gib": null,
"gpu_class": "Intel Gaudi 2",
"gpu_count": null
}
}
}Unknown or withheld values (9)
$.egress.meteredegress-unknown$.egress.termsnot-stated$.identity_cost.kindidentity-defaulted$.per_object_cap.notesprocess$.per_object_cap.statednot-applicable$.reliability_notenone-observed$.retention.notesprocess$.retention.statednot-applicable$.toolingnot-stated