Terms of Service
Last updated
The terms for using Code Command Center and the CCC Cloud sync service.
What the service is
Code Command Center (CCC) is a dashboard that runs Claude Code sessions. The runtime is source-available and you host it yourself: it runs on your hardware, against your own Anthropic credentials, and it talks to a local server on your machine.
CCC Cloud is the optional service on top of that. It gives you an account, organisations and their members, and it syncs your project configuration between the machines you run CCC on. Cloud sync is off unless you turn it on by setting CCC_CLOUD_SYNC=1. These terms cover the cloud service and this website. Your use of the runtime itself is governed by its licence — see below.
The cloud is a mirror, not the source of truth for your work, and it is not a backup. Your local database stays the store your machine actually reads from.
Accounts and eligibility
To use CCC Cloud you need an account. Accounts are created through Supabase Auth with an email address and password, or through a social provider where one is enabled. You must be old enough to enter a contract where you live, and you must give an email address you actually control.
You are responsible for everything that happens under your account and under any CCC install you link to it. That includes what the agents you start do — the code they write, the commands they run, and the repositories they touch. CCC drives Claude Code with the permissions you give it; it does not review the work for you.
Each CCC install is linked to exactly one organisation, and the credential that links it acts as the user who linked it. Do not link an install to an organisation you are not entitled to act for.
Plans, and what billing does not do yet
There is one plan today and it is free. It carries starter limits on how many projects, members, installs, automations and concurrent sessions an organisation gets.
Paid plans are planned but not built. The shape we intend is a Pro tier at $12 per month per organisation, and a Team tier at $29 per seat per month. Those are our intended prices, not a live offer — they may change before billing ships, and nothing on this page can be purchased today.
We cannot currently charge you. Payment processing is not implemented. There is no checkout, no card form, no stored payment method and no subscription running anywhere. If you see a paid tier described in the product, it describes what is coming, not something you can buy today. When billing does ship, we will publish the terms that go with it before charging anyone. A paid plan buys the hosted service, higher limits, and a commercial licence for the runtime that lasts as long as the plan does.
Plan limits gate what you can create. If an organisation drops to a smaller plan, nothing you already have is deleted — new creates are blocked and future scheduled work is paused instead.
Licence for the runtime
The CCC runtime is published under the PolyForm Noncommercial license. In short: personal and other noncommercial use is free, and commercial use is not covered by it. The licence text is the authority on what those words mean — read it, not this summary.
If you want to run CCC at work, you need a commercial licence. That is a separate agreement — our licensing page sets out which uses are free, which need a licence, and how to ask for one. A paid CCC Cloud plan includes one: while your Pro or Team subscription is active, your organisation is licensed to run the runtime commercially, and that licence lapses when the subscription does.
Plan limits in the product are there to make the free tier behave sensibly. They are not a licence check and clearing them is not permission — the licence is what decides whether your use is allowed.
Your content, and acceptable use
Your code, your configuration files, your prompts and the output of your runs stay yours. We claim no ownership of them. We store the parts that sync so we can hand them back to your other machines, and we use them for nothing else. What we hold and how it is protected is set out on our privacy page.
You agree not to use CCC Cloud to:
- break the law, or help someone else break it;
- store or sync content you have no right to store or sync, including someone else’s credentials or personal data you were not given;
- attack, overload or probe the service, or work around its limits and access controls;
- resell access to the service or run it as a service for other people.
Sync has hard size limits and skips files it treats as binary, so the service is not a place to put artefacts that belong in object storage.
No warranty, and availability
CCC Cloud is provided as it is, with no warranty of any kind. We do not promise it is fit for a particular purpose, that it will work without faults, or that it will keep working the way it does today. To the extent the law where you live lets us disclaim these warranties, we disclaim them; where it does not, the law wins.
The service is early. We restart it, migrate its database, change its behaviour and take it down when we need to. We make no promise about how much of the time it is reachable, and there is no service level commitment attached to it. Free means free of obligations in both directions.
Because of that, keep your own copies. Your local install holds your work and your git remotes hold your history. Cloud sync moves configuration between your machines; it is not a backup, and losing it should be an inconvenience rather than a disaster.
Limitation of liability
Software that runs commands on your machine can do damage — delete work, push a bad commit, spend money at your model provider. You decide what permissions to give it, you decide what it is pointed at, and you carry the outcome.
To the maximum extent the law allows, Restart Labs LLC is not liable for any damages arising out of your use of CCC or CCC Cloud. That includes lost or corrupted data, lost or overwritten work, damage to your systems, money spent at your model provider or any other third party, lost profits, lost revenue, business interruption, and any indirect, incidental, special, consequential or punitive damages — whether or not we were told such damages were possible.
Some jurisdictions do not allow a liability exclusion this broad. Where that is the case, our total liability to you for all claims is limited to the greater of the amount you paid us in the twelve months before the claim, or one hundred US dollars. On the free plan that amount is one hundred US dollars, because you have paid us nothing.
Nothing in these terms excludes liability that cannot lawfully be excluded. Where the law says a limit is unenforceable, the law wins and the rest of this section still stands.
Run CCC against work you can afford to lose, or against work you have backed up somewhere we do not control. Cloud sync is not a backup — see the privacy policy for what that actually means.
Ending it
You can stop using CCC Cloud at any time. Turn sync off by unsetting CCC_CLOUD_SYNC and nothing further leaves your machine. Delete your organisation and its synced rows go with it. As our privacy page explains, some deletes are recorded as tombstones rather than removing the row immediately.
We may suspend or close an account or an organisation that breaks these terms or the acceptable use list above, or where keeping it running puts the service or other people at risk. If we do, we will tell you at the address on the account.
Ending your cloud account does not touch your local install, your local database or your repositories, and it does not change your rights under the runtime licence. Those are separate from this agreement and survive it.
Changes to these terms
We will change this page as the service changes — most obviously when billing ships, since none of it exists yet. The date at the top is the last time we edited it, and the current version is always the one published here.
If you keep using CCC Cloud after a change, you are accepting the updated terms. If you do not accept them, stop using the service and delete your organisation; the previous section says how.
The legal details
You are contracting with Restart Labs LLC, a Texas limited liability company, at 5900 Balcones Drive, Suite 100, Austin, TX 78731, United States.
These terms are governed by the laws of the State of Texas, without regard to its conflict-of-laws rules. Any dispute goes to the state or federal courts sitting in Travis County, Texas, and you and we both agree to that venue. Before filing anything, write to us — most things are faster to fix by email than by lawsuit.
For questions about these terms, for support, and for formal legal notices, write to support@restartlabs.ai. Privacy requests go to privacy@restartlabs.ai instead.
When paid plans do ship: you can cancel at any time and it stops the next charge, but we do not refund the period you are already in. There is nothing to refund today, because nothing can be charged today.
One question comes up often enough to answer plainly: a paid plan does include a commercial licence. Pro and Team buy the hosted service, higher limits, and the right to run the runtime commercially for as long as the plan is active. If you want a commercial licence without a cloud subscription, that is a separate agreement — see the licensing page.