Your work stays yours.

Your code, datasets, and models are private to you. Here is how that works, in plain terms.

Hosted in Malaysia

On GPU clusters run by our data center partners.

Isolated containers

Every workspace is separate from other users'.

No passwords

Sign in with Google or a magic link.

Deleted means gone

Delete a volume or your account and we keep no copy.


The details

Container isolation

Every workspace runs in its own Docker container, separate from other users' workspaces. Your work is not shared with or visible to other users on the platform.

GPU and VRAM allocation

Our VRAM slicer virtualizes GPU memory and allocates it to each workspace. You choose how much VRAM you need when you start an instance, and your workspace gets exactly that amount. Each workspace is limited to its own allocation, so one user's job can't take memory from the slice you are paying for.

What we can and can't see

Sovernstack staff cannot access the inside of your containers. The only thing we see is the state of your instance, such as running or idle, which we need to run the platform and bill you correctly. We can't read your files, code, or running jobs. The data center operators hosting the hardware can't access them either.

Your data and volumes

Your data lives on mounted volumes that are separate from the container. If you delete a container, the container is gone and your data stays on its volume. If you delete a volume, the data is gone and we keep no copy. If you delete your account, we delete everything. Your data is encrypted.

Where it is hosted

In Malaysia. Your workspaces, volumes, and the open-weight models behind our LLM gateway run on GPU clusters in Malaysia, operated by our data center partners. If one cluster goes down, another takes over for the LLM gateway. See who hosts the hardware on our partners page.

Sign-in and access

You sign in with Google or with a magic link: enter your email and we send you a one-time login link. We don't use passwords, so we don't store any, and there is no password to leak, reuse, or guess.

SSH access

SSH sessions use .pem key files that you download yourself. We don't have access to your private key, so only you can open a session to your instance. Keep the file safe and treat it like a password.

Questions or concerns?

If your supervisor, IT team, or compliance team needs more detail, get in touch or email hello@sovernstack.com. You can also read the common questions.


Ready to start?

Open a workspace and see if it fits what you are building.

Try for Free