1. The service
Krater Pro Cloud Lab lets an authenticated user save bounded virtual project files and chat history, connect a user-supplied Krater.ai API key for the current page session, and request coding assistance from the configured Kimi K3 model.
Cloud Lab is intentionally limited: it does not execute code, open a terminal, access a device filesystem, clone a repository, use Git, or deploy software. Descriptions of filesystem, Git, terminal, command-sandbox, or broader agent capabilities refer to the separate local Krater Pro CLI and IDE.
2. Accounts and account security
You must provide an email address, use a unique password containing 15 through 128 characters, and be legally able to agree to these terms. Cloud Lab does not verify ownership of that address or offer email-based password recovery. You are responsible for activity under your account and for keeping its credentials secure. Do not share a session or try to access another user’s account or projects.
If you suspect unauthorized access and can still sign in, delete the account to revoke its sessions, then create a new account with a new password if you want to continue. Cloud Lab does not currently offer password changes. Report a reproducible non-sensitive security concern through GitHub Issues; contact the maker privately through LinkedIn before sharing identity-linked details. Never send a password or API key.
3. Bring-your-own key and billing
Cloud Lab requires your own Krater.ai API key for model inference. Krater Pro does not sell, issue, subsidize, or recover Krater keys and does not manage your Krater.ai subscription. You are responsible for obtaining a suitable key, maintaining its access, monitoring usage, and paying all fees Krater.ai charges under your plan.
Requests made with your key count against your Krater.ai account. Model availability, limits, pricing, billing, and upstream service behavior are controlled by Krater.ai and may change. Validate the expected cost and permissions before connecting a key.
4. Acceptable use
You may not use Cloud Lab to:
- break a law, violate another person’s rights, or facilitate malware, fraud, abuse, or unauthorized access;
- probe, bypass, disable, or overload authentication, rate limits, project isolation, security controls, or service infrastructure;
- access another account, submit a key you are not authorized to use, or misrepresent your identity or rights;
- upload or transmit content you do not have the right to process; or
- use automated traffic in a way that degrades the service for others.
You are responsible for reviewing and safely using any code, commands, or advice produced through the service.
5. Your content, third-party rights, and open source
You retain whatever rights you already hold in the prompts, virtual files, and other content you submit. You permit Cloud Lab and its disclosed service providers to host, process, transmit, and display that content only as needed to operate the features you request.
You are responsible for ensuring your content and use of model output do not violate licenses, confidentiality duties, privacy rights, or other third-party rights. Do not assume AI-generated material is unique or free of third-party claims.
The Krater Pro source code is available on GitHub under the repository’s MIT License. That license governs your use of the open-source code; these hosted-service terms govern your use of Cloud Lab.
6. AI output and professional judgment
Model output can be incomplete, insecure, outdated, or wrong. Krater Pro may provide useful coding assistance, but it does not replace code review, testing, security analysis, or professional judgment. Verify dependencies, licenses, commands, migrations, credentials, and production changes before use. Do not rely on Cloud Lab for medical, legal, financial, safety-critical, or other high-stakes decisions.
7. Availability and no warranty
Cloud Lab, its features, and third-party integrations may be changed, limited, interrupted, or discontinued. No uptime, data-recovery, compatibility, model-quality, or continued-availability commitment is made.
To the extent permitted by applicable law, Cloud Lab is provided “as is” and “as available,” without warranties of merchantability, fitness for a particular purpose, non-infringement, or error-free operation. Keep independent copies of work that matters; Cloud Lab is a convenience, not a backup service.
8. Project deletion, account deletion, and termination
You can delete projects or request account deletion from the account menu. Account deletion removes the account and its associated projects and sessions from the active service, subject to the limited disaster-recovery history described in the Privacy Notice.
Access may be limited or terminated when reasonably necessary to protect the service or others, respond to legal requirements, or address a material breach of these terms. You should export or copy important content before deletion or discontinuation.
9. Changes and contact
These terms may be updated as Cloud Lab evolves. The current version and effective date will remain available on this page. Continuing to use the hosted service after an update means the updated terms apply from their stated effective date.
For non-sensitive questions or reports, use Krater Pro GitHub Issues. For a report involving your identity or private details, contact Supratim privately on LinkedIn first. Never send passwords or API keys.