Terms of service

The operator details this page depends on (publisher identity, hosting provider and contact addresses) have not been published yet. This text is a draft for review. It is not indexed by search engines and does not take effect until those details are published.

These terms govern your use of cpuos.si, the cpuOS dashboard, the REST jobs API and the hosted cpuOS control plane (the service). By creating an account, creating an API key or using the service, you agree to them. If you do not agree, do not use the service.

The service is meant for professional use by developers and teams. By registering you confirm that you act for a business or in a professional capacity and, if you act for an organisation, that you may bind it. The legal notice identifies the publisher, and the privacy policy explains how personal data is handled.

cpuOS is a pilot for running bounded jobs on a worker you connect. You run the cpuOS worker, which needs Node 24 and Docker, on a machine you control. You submit Python 3.13 or Node 24 standard-library code from the dashboard or the REST API, with CPU, memory and time limits. The hosted control plane queues the job. Your worker runs it in a restricted Docker container without network access. The control plane stores the status, output and exit code. The cpuOS plan of a workspace limits how many of its jobs run at once: 5 on the free plan, which is the default plan, because no paid cpuOS plan is sold. The limit applies when a worker asks for a job, so further jobs wait in the queue.

The pilot does not include:

• paid plans, checkout or usage charging;
• an availability commitment, a service level agreement, SSO or audit export;
• isolation suitable for hostile code or for unrelated tenants;
• browsers, package installation, custom images, file transfer, exposed ports, snapshots or persistent sessions.

The pilot has no cpuOS checkout or usage charging. You provide and pay for the worker's hardware, hosting and connectivity. The cost calculator on this site is a planning model with illustrative rates. It is not an offer or a price list. Any paid use needs separate terms that we agree with you before they apply.

• Give accurate information and keep your sign-in credentials safe.
• gpuOS and cpuOS share one account, with the same workspaces, members and roles on both, and the member limit of the workspace's gpuOS plan (2 on Community, pending invitations included) applies on both. API keys are per product by default: a cpuOS key does not call gpuOS unless you allow it to call both products when you create it. Revoking a key that works with both products stops it on both; the gpuOS gateway can keep accepting it for up to 5 seconds after it was revoked on cpuOS. Using gpuOS is governed by its own terms.
• Workspace owners and admins decide who joins and which keys and workers exist. You are responsible for what happens under your workspace's keys and worker tokens.
• API keys and worker tokens are shown once. Treat them as secrets, revoke them if they leak, and keep them out of submitted code and public repositories.
• Tell us promptly at To be provided if you think an account was compromised.

You operate the worker. You install and update it, secure the machine and the worker token, and decide where it runs. Docker access gives root-level control of the host, and containers share the host kernel. Use a machine allocated to the pilot, run one worker process per worker token, and submit only code you trust and are allowed to run.

Jobs run on your machine under your responsibility. We are not responsible for what submitted code does there. A job whose worker is lost is marked failed and is not run again automatically, but it may already have had effects. Inspect the result before you retry.

You must not use the service to:

• create, process or distribute content that is illegal where you or your users are located, or that infringes someone else's rights;
• attack, scan or probe the service, other users' workspaces or third-party systems, or try to reach data or accounts that are not yours;
• enrol a machine you do not control or are not authorised to use as a worker, or use a worker to reach other systems;
• run code meant to escape the container, damage a worker's host or get around the job limits and the disabled job network;
• bypass or tamper with rate limits or usage records, or create accounts to evade them;
• send traffic designed to degrade the service for others;
• create malware or run phishing, fraud or spam campaigns, or harass people.

We may rate-limit, suspend or remove access, or delete a workspace, if we reasonably believe these rules are broken or that the service, other users or third parties are at risk. Where practical, we tell you why. To report abuse, write to To be provided.

You keep your rights in your code, output and data. You give us only the permission needed to operate the service for you: to store your account, workspace and job data, to send job code to your workers and to show you the results.

The control plane stores job code and output until their deletion deadline, which is set when a job ends from the retention period of your workspace, 7 days unless an admin or owner chooses none, 24 hours or 30 days, and then deletes them. A copy can remain in a backup for up to 30 days after that. The privacy policy lists what is stored, what is kept and for how long. Do not submit secrets, personal data or regulated data unless you are allowed to process them on a hosted service.

cpuOS is a pilot. It comes without an availability commitment, a service level agreement or a guaranteed support response time. Workers can go offline and the control plane can restart, which can interrupt or lose jobs. Queued jobs that no worker picks up in time fail.

We may change, add or remove features, runtimes, limits and worker versions.

You can stop at any time: revoke your keys and worker tokens, stop your workers and delete your account on gpuOS, in Settings > Your account. The privacy policy says what is deleted. The account is shared, so deleting it removes it on cpuOS too. Workspaces shared with other people stay, and their only owner must hand over ownership first. To have a single job deleted before its deadline, or for anything else, use the data request contact in the privacy policy.

We may suspend or end your access if you break these terms, if your use puts the service or others at risk, or if the law requires it. When access ends, your keys and worker tokens stop working.

To the extent the law allows, the service is provided as is and as available, without warranties of any kind, including fitness for a particular purpose and uninterrupted or error-free operation.

Nothing in these terms limits liability that the law does not allow us to limit, including liability for fraud, intentional misconduct, gross negligence, and death or personal injury.

Subject to that, we are not liable for indirect or consequential loss, or for loss of profit, revenue, data or goodwill. We are not liable for loss caused by your workers, your machines, the code you submit or third-party services such as GitHub or Google. Because the pilot is free, our total liability for all claims relating to the service is limited to the amount you paid us for it in the 12 months before the event that gave rise to the claim, which is zero unless we agreed paid terms with you.

We may update these terms. The date at the top of this page shows the latest revision (2026-10-15). Changes apply from the date they are published. If you keep using the service afterwards, you accept them. If you disagree, stop using the service.

These terms are governed by To be provided. Disputes go to To be provided, to the extent mandatory law allows.

• Legal notice
• Privacy policy