Ozekai — More Info

Lifecycle

The web UI owns the session lifecycle. You launch and terminate sessions from the dashboard then open the workspace with SSH or VS Code.

Billing

Ozekai uses prepaid credits to rent GPUs.

⚠ Closing your SSH terminal does NOT stop billing. You must end the session from the dashboard.

SSH Access

Session lifecycle actions are dashboard-only. Shell and editor access use normal SSH into your assigned GPU workspace.

Account SSH key

Add one OpenSSH public key on the Dashboard. Active sessions expose a managed workspace endpoint for that key.

SSH key troubleshooting

If you add or replace your account SSH key while a workspace is already running, save the key again from the dashboard. Active workspaces sync the saved account key shortly after that update.

If SSH says the host key changed, clear the stale local entry with ssh-keygen -R ozekai-training, replacing ozekai-training with your workspace alias, then reconnect and accept the new host key prompt.

Software Inside the Workspace

Ozekai workspaces are intentionally minimal. Install the operating-system and language packages your job requires during the active session.

pip caches downloaded packages under /workspace/.cache/pip by default, so repeated installs can reuse cached wheels inside your workspace.

Note: apt-get is not available — use conda to install system libraries instead.

Jupyter Lab (optional)

Install and launch Jupyter Lab inside your session without a browser:

pip install jupyterlab
jupyter lab --no-browser --port=8888

Then open a second terminal on your local machine and forward the port over SSH:

ssh -L 8888:localhost:8888 ozekai-training

Copy the http://127.0.0.1:8888/lab?token=… link printed in the session terminal and paste it into your local browser.

Tips & Best Practices

Your /workspace directory is persistent for the duration of your session. It is wiped immediately after teardown.
Use the Dashboard for start/terminate lifecycle control and SSH instructions.
Closing SSH does not end billing. Ending the dashboard session removes the workspace.

Spot GPU

Ozekai offers GPU access at prices that are hard to find anywhere else. The model is simple: spot-backed capacity, minimizing idle GPU time, and billing tied to active runtime only.

What you get

Every spot session gives you an isolated Linux workspace with GPU access and standard SSH for terminal and VS Code workflows.

What you do not get

Ozekai spot sessions are not meant to be your permanent storage layer. If you end the session, you should expect local session storage to be gone unless you copied it somewhere else first.

Availability expectations

Spot supply is demand-sensitive. Some GPU types may be available immediately, while others may sell out or take longer to find.