Terms of service

Bee Workspace is the trading name of a registered Individual Entrepreneur, identification number 306502594. It is a sole trader, not a company: the other party to this agreement is a person, and that person is named with their registered address in section 19.

“We” and “us” below mean that person; “you” means whoever holds the account. Using the site or a workspace means accepting these terms. If you are agreeing on behalf of a company, you are confirming you may bind it.

The product is a virtual machine running Linux, rented by the month or the year, reachable through an HTTPS gateway, with a set of development tools already installed. You get root on it. Root is the point of the product, and it is also the line where responsibility moves.

We are responsible for:

• provisioning the workspace and handing it over;
• the host and hypervisor layer underneath it;
• network connectivity to it;
• the initial configuration of the workspace and its tools;
• support for the platform itself.

You are responsible for everything inside the workspace:

• operating system updates and security patching, except where section 7 says we apply them for you;
• firewall rules, SSH configuration, and credential management;
• every piece of software you install, and compliance with its licence;
• your data, and your own backups of it — section 5 says what an included backup does and does not cover;
• the consequences of configuration changes you make.

We provide the machine, not the things you run on it. The bundled tools, including the third-party agent CLIs, come as their authors publish them, under their own licences.

You sign in with an email address, and access to a workspace runs through that sign-in. Keep it secure. Anything done through your account is treated as done by you, so tell us promptly if you think someone else has got in.

What you may not do with a workspace is set out in the acceptable use policy, which forms part of these terms. It is a separate document so that it can be updated as abuse changes without reopening this one.

It covers deliberate misuse and also negligently permitting misuse — you have root, so a workspace of yours that is compromised and used to attack someone else is still a workspace of yours.

Machines on this plan are built with the provider's automated backup: a periodic snapshot held by the provider, not on your machine. You cannot restore it yourself — you would ask us — and we have not committed to how far back a snapshot reaches or how long a restore takes. Keep your own copy of anything you cannot lose.

That applies to Developer and Max. On Basic and Pro, no backups are included. You are responsible for backing up your data.

We do not keep a copy of workspace content ourselves, on any plan. Where a plan includes the provider’s automated backup, what exists is a snapshot in the provider’s systems, and we have committed to no retention period and no recovery time for it. We do not undertake to recover your data — not after you delete it, not after a fault, and not after the term ends. A workspace is a machine, not an archive.

There is no service level agreement, no uptime commitment, and no service credits, on either the consumer or the business track. We aim to keep workspaces up and to do disruptive work with notice, but a single virtual machine can fail, and this product is priced as what it is rather than as a fault-tolerant platform.

Plan accordingly for anything you cannot afford to have offline. If you need availability guarantees, this is not the right product and we would rather say so here than argue about it later.

On Basic, Pro, Developer and Max, we apply the operating system’s security updates for you. What that covers, in full:

Ubuntu security updates are applied for you, in a window of about an hour each night. Security packages only: the development tools are pinned and an update never moves them. Nothing is restarted and nothing is rebooted for you — where a patch needs a reboot the machine says so and waits for you to take it. You can turn the whole thing off from the machine's own dashboard.

It is a schedule and not a guarantee: a machine that is off, or unreachable, or whose package mirror is failing, misses its window and tries again at the next one. We do not undertake that any particular patch is applied by any particular time, and a missed window is not a service failure. The machine records when it last ran and what it applied, and that record is what either of us would be looking at.

Separately from that, we may provide updates, patches, and improvements to the preinstalled workspace stack — the agent CLIs, the editor, the terminal and the rest of the tooling we install. Those are not the operating system’s security updates and are not covered by anything above: they are provided on a best-effort, goodwill basis, on no schedule, with no undertaking to support any particular version of any tool or to maintain compatibility with changes you have made. An update that does not arrive is not a service failure.

The service depends on third-party infrastructure providers. We are not liable for their acts, omissions, outages, price changes, throttling, or termination of service.

We may change infrastructure providers, data centre locations, or underlying hardware at any time without notice. If a provider stops serving us or you, we may migrate, modify, or terminate your workspace with reasonable notice. You choose a zone — a part of the world — and which data centre that resolves to is ours to decide and ours to change.

Each size has a fixed allocation of vCPU, memory, and disk, published on the pricing page, along with the outbound traffic included. Nothing here is unlimited, and we do not describe anything as unlimited: our own upstream providers reserve the right to throttle disruptive usage, so a promise of unlimited anything downstream would be one we cannot keep.

We may throttle, or charge for, usage that goes materially beyond the published allocation. Where we can we will tell you first.

Bring your own API keys. We do not supply, resell, or pass through access to any AI model or API. You contract directly with whichever providers you use, you pay them directly, and their terms apply between you and them.

We give no warranty as to the accuracy, quality, or fitness of anything a model produces on your workspace. Outputs must not be relied on for medical, legal, or financial decisions.

If you run a model on your workspace, complying with its licence is yours to do. Open-weight licences carry real restrictions — acceptable use clauses, scale thresholds, attribution requirements — and we neither check them nor take responsibility for them.

Prices are on the pricing page. Paddle.com Market Ltd is the merchant of record: it sells the subscription to you, takes the payment, adds any VAT or sales tax due where you are, and issues the invoice. Your card details go to it and never reach us.

A workspace runs for the term you paid for — a month or a year. Annual plans are not refundable after the 14-day window. Cancelling stops renewal; it does not refund the remaining term.

Refunds are covered in the refund policy, which forms part of these terms.

A failed payment does not delete anything immediately, and it does not leave things running indefinitely either. The timetable is fixed and it is this:

When the grace period runs out your machine is reclaimed and its disk is wiped. We do not hold your data for a retention period afterwards and we undertake no recovery of it, on any plan. Export anything you need before that date.

We email you when the payment fails, before the grace period runs out, and when the term has ended. The second of those states the date.

You can stop at any time by letting the term run out, or by asking us to shut the workspace down sooner.

For a serious breach — illegality, a breach of the acceptable use policy, a security threat, or a demand from an infrastructure provider or law enforcement — we may suspend or terminate immediately, without notice, and no refund is payable.

For anything less serious we will tell you what the problem is and give you a reasonable period to fix it before we act. If we terminate for something that was not your fault, you get back the unused part of what you paid.

You will reimburse us for costs, fines, or claims we incur as a result of your use of the service.

Nothing in these terms excludes or limits liability for death or personal injury caused by negligence, for fraud or fraudulent misrepresentation, for gross negligence, or for anything else the law does not permit to be limited.

Subject to that, and to the maximum extent the law allows, we exclude liability for lost profits, lost revenue, lost or corrupted data, business interruption, and any indirect or consequential loss. Our total aggregate liability for all claims is limited to the fees you paid in the three months before the claim arose.

Beyond the warranties the law gives you and does not let us exclude, the service is provided as it is.

We may change these terms where there is a good reason to — a change in the law, a change at an infrastructure provider, a security requirement, or a change in what the service does. We will give you reasonable notice by email before a material change takes effect, and the date at the top of this page always says which version you are reading. Continuing to use the service after that means accepting the change.

The acceptable use, refund and privacy policies change on the same terms and carry their own dates. None of it reaches backwards: the version in force on the day you paid is the one that governs what you paid for.

A price change never applies part-way through a term you have already paid for. It applies at renewal, and we give at least 60 days notice of it. If you do not want the new price, do not renew.

These terms are governed by the laws of Georgia, and the courts of Tbilisi, Georgia have jurisdiction.

• Neither side is liable for failure caused by events outside its reasonable control.
• You may not assign this agreement without our written consent. We may assign it as part of a transfer of the business, on notice to you.
• If any clause is unenforceable, the rest stays in force.
• These terms, with the acceptable use, refund, and privacy policies, are the whole agreement between us.
• Not enforcing something once does not waive the right to enforce it later.
• Notices to you go to your account email; notices to us go to the address in section 1.

Legal notices: [email protected]. Support and refunds: [email protected]. Abuse reports: [email protected]. Include your order code if the question is about a specific workspace.

The trader you are contracting with, and the address written notice goes to: