Keep the context of a project together and reuse it when requesting compute.
Create a workspace
Open Workspaces, choose a project name, describe the workload and select its type. Add an existing S3 location if useful, then select Create workspace.
A workspace saves configuration and data references. It does not create a bucket, upload files or start a GPU session. Workload types describe your requirements; they do not install a framework or container image.
Request compute
Open your workspace and select Get compute for this project. The request includes your saved objective, workload type and data reference. Review those details, then choose the GPU count, location, UTC window and budget.
Submitting a request does not charge your account or reserve GPUs. You can find submitted requests again from the workspace.
Update the project
Edit the configuration and select Save changes. Existing requests keep the workload details you originally submitted. If another edit happened first, reload the current configuration before saving again.
Data and access
Workspaces are private to your signed-in account. Enter S3 references such as s3://your-bucket/project/, without credentials or signed URLs. Saving a reference grants no access to the bucket. Keep API keys, passwords and sensitive data out of free-text descriptions.
Run code on your reserved GPUs
When a matching offer supports Workspace · Python and shell, choose that access mode before accepting the quote. Once the reservation is ready, open My workspace from its reservation page.
- Select Check GPU access. The check reports the GPUs visible inside your environment.
- During your reserved window, select Confirm access & start session. This starts the usage counter; preparing the environment does not.
- Choose Python or shell, enter your code and select Run on my GPUs. Read its exit status and output under Command results.
- Select Stop session & release GPUs, or tick End the reservation when this command finishes before running code. The reservation shows the final charge and returned credits after it ends.
One command runs at a time, for up to five minutes and within the reservation window. Code is limited to 4 KiB and displayed output is bounded. The supplied Python environment includes PyTorch; network access follows the approved supplier policy. This interface executes commands in your GPU container; it does not grant administration of the supplier's host.
Files in /workspace last only for that GPU reservation. Save results before stopping. Your project description and data references remain in your account, but this does not persist the files from the GPU environment or mount an S3 bucket automatically.
Connect with SSH or VS Code
For a running session with an SSH-capable supplier, open SSH & VS Code on the session page. Paste your Ed25519 public key from ~/.ssh/id_ed25519.pub, then download the connection file. Never upload your private key.
Download the SSH helper from that page and run the displayed setup command. It requires Python 3.10+ and OpenSSH on macOS or Linux. The helper creates a dedicated Python environment, stores the temporary credential with restricted permissions and adds a Requenta host to your SSH configuration. Existing SSH entries are preserved. Use the printed ssh command or choose that host in the VS Code Remote-SSH extension. Open /workspace to work with the same files as your browser commands. SFTP is available to copy results to your computer.
Access lasts up to one hour, within your reservation. Creating a new connection file replaces the previous access. Revoke access closes tunnels within 15 seconds; stopping the reservation also closes access. Reconnect using a fresh file when access expires. Delete the downloaded JSON after setup; it contains a temporary connection credential.
The helper checks the SSH host key supplied by your session. Your computer and the supplier agent connect outward to Requenta over HTTPS; the supplier does not expose an incoming SSH port. SSH gives access to the allocated container, without host administration. Only loopback TCP forwarding is supported. VS Code can download its server locally and transfer it over SSH when the supplier environment cannot reach the Internet; its extensions remain subject to the supplier network policy.
SSH availability is confirmed by the supplier agent. If setup is unavailable, the existing browser command interface remains accessible for a running workspace. Storage is still temporary and is not shared automatically between reservations.
Disk and transfer budget
The reservation shows its temporary disk allocation and transfer allowance. With the included resource profile, /workspace holds up to 10 GiB and is removed during cleanup. Going over the Kubernetes disk limit can evict the workload. Persistent storage and automatic backups of these files are not provided.
SSH, SFTP, VS Code and loopback forwarding share one combined transfer budget across all your connections. Check the remaining allowance in the workspace, including before uploading large datasets. The counter allocates blocks up to 1 MiB per direction and conservatively retains unused tails after disconnects. It includes SSH protocol traffic. At exhaustion, further transfers are blocked without an overage charge; compute keeps running and can still be stopped from the console. Download results before exhausting the allowance or ending the reservation. There is no automatic paid extension.
Direct outbound Internet access from the container remains disabled. Browser commands and their bounded output use the control channel, not this SSH budget. For a supplier gateway, follow the resource limits in the accepted quote; the console does not display a live meter for external access.