Two tiers
Secure or Community?
A dedicated VM and its own GPU on both. Your data decides.
Side by side
Same VM. Different hardware.
| Feature | SecurePartner datacenters | CommunityIndependent providers |
|---|---|---|
| Hardware | Partner datacenters | Independent providers |
| Your session | A dedicated VM | A dedicated VM |
| GPU | Attached to your VM only | Attached to your VM only |
| Disk | Deleted at the end | Encrypted, erased at the end |
| Inbound | SSH from your IP only | No port open on the provider's machine |
| Access | SSH | SSH and JupyterLab |
| Physical access | Datacenter controls | Kept by the provider |
| Session memory | Datacenter controls | Readable by the provider, GPU included |
| Best for | Confidential code and data | Open data, research, rendering, open models |
Confidential code or data? Choose Secure.
Which one
Start from your data.
Secure
Choose Secure when
- Code, data or weights are confidential.
- A contract requires datacenter controls.
Community
Choose Community when
- Your data is open or public.
- You want JupyterLab next to SSH.
On both tiers
One account. Both tiers.
Balance
One balance.
Prepaid credit, for either tier.
Billing
By the minute.
On demand, or reserved up to 30 days.
Access
Your SSH key.
Same flow on both tiers.
Connect over SSH
Pick a machine.
Both tiers, one catalog.