Terms of use

These terms govern use of Kelvane (the website, account, preview, worker, and related APIs). By creating an account or clicking through, you agree to them. If you are using Kelvane for a company, you represent you can bind that company. The service is operated by a single-person business. This document matches the product; it is not a negotiated MSA and not legal advice. Contact hello@kelvane.dev.

1. The service

Kelvane has two products. They do not share an agent loop.

New app (greenfield)

You describe an application. An agent builds it in a workspace tied to your Auth0 account: the right first screen for that product plus one workflow that works, then a compile and a live preview of that app — not a static Harbor/Lumen/Atlas/Ledger mock. Follow-up messages edit the same workspace. Builds use credits: 10/day free (up to 40/month). Packs from $10 at $0.20/credit. Cutover and hosting are quoted with a human ($3k–$12k indicative founding range · timeline scoped per engagement).

The generated app includes auth, admin, mail, and billing files as seams. Generated auth is a local stand-in until you wire a real provider. Generated billing is not Stripe until you connect it. Treat first paint as a draft you own, not a certified production system.

Existing system (wrap)

After you accept the session NDA, you may upload source (zip/SQL) and screenshots. We scan; only clean copies reach the worker sandbox. Self-serve is a live Discovery map, questions generated from that map, then the same build as a new app. We do not put PHP into the generated app and we do not unzip on the Next.js host. Java, Python, .NET, or an ERP-sized tree overflows to a human quote.

Mapping and generated questions are free to run. Builds spend credits like a new app. A modern UI preview is in-product. Cutover, production hosting, HIPAA-ready processing, or an ERP core is a separate human engagement (indicative founding range in the product today: $3k–$12k indicative founding range · timeline scoped per engagement for one bounded system). That is quoted with a human, never charged self-serve. Waiting room is overflow, not the happy path.

Preview is not, by default, production

Kelvane hosts the workspace preview. That preview is not an SLA for your customers and not a place for live card data or PHI unless a written hosting addendum says otherwise. You may export a zip (or equivalent tree) and run the app on your own infrastructure; that is optional, not required. Share/publish, when offered, is the running preview (or a freeze of it), not a questionnaire skin.

2. Accounts

You must be 18 or older. You are responsible for the Auth0 identity you use and for activity under it. We may refuse, rate-limit, or suspend accounts that abuse builds, uploads, or previews. Super-user or operator accounts exist to run the product; they are not a license for you to bypass rate limits.

3. Pricing and payment

Kelvane is credit-metered for builds and quote-based for production work. Mapping an existing system and generated questions are free to run. Builds spend credits: 10 free credits per UTC day (up to 40 free per calendar month; unused daily credits do not roll to the next day). A first build uses 10 credits; a follow-up uses 3. After free credits are exhausted, you may buy prepaid packs in-product (minimum $10 at $0.20 per credit). That is not a subscription, and a pack is not charged mid-pass.

• Abuse control is credit metering and per-job caps: turn count and a per-job spend cap. Hitting a cap stops that job.
• Paid work — cutover, production hosting, an ERP core — is scoped and quoted with a human before it starts ($3k–$12k indicative founding range · timeline scoped per engagement). Nothing is charged without a quote you have agreed to. The range is indicative, not a fixed price or delivery SLA.
• Because prepaid credits never expire, unused pack credits stay on the account. Refunds for unused credits: email hello@kelvane.dev.
• Free credits are offered as-is and may be limited or withdrawn per account if abused.

Stripe’s terms apply to checkout for credit packs. Failed or disputed payments may block new pack purchases until resolved. We do not sell an “unlimited Claude” SKU.

4. Uploads and NDA

New-app attachments (images, CSV/TSV, short specs) do not require an NDA. Wrap source does. The in-product NDA is a click-through mutual non-disclosure so code does not change hands without a visible gate. It is not a substitute for a negotiated NDA/MSA.

You warrant that:

• you have the right to upload the files and to let us process them;
• the upload is not malware, a zip bomb, or someone else’s production secrets you are not allowed to share;
• you will not upload live PHI or live cardholder data into this version of the product.

We inspect type by magic bytes, cap size, and fail closed if a scanner cannot finish. Dirty or disallowed files are rejected, not sent to the model, and not served on share-preview. We may keep audit rows that a file was rejected without echoing attacker content into logs.

5. Intellectual property

Kelvane IP. The site, kit shell, worker, Discovery and Facade templates, trademarks, and documentation stay ours.

Your IP. Your briefs, uploads, and the session-specific files the agent writes for you (for example filled content.js and flow pages) are yours. We need a license to host, preview, compile, scan, and send allowed snippets to Anthropic so we can provide the service. That license ends when the copy is deleted from our systems, except backups and legal holds.

Feedback. If you send product feedback, we may use it without paying you.

Model output can be wrong, incomplete, or similar to other output. You are responsible for reviewing generated code and for whatever you ship after export.

6. Acceptable use

You will not:

• use Kelvane to attack systems you do not own or to build malware;
• bypass rate limits, per-job caps, sandbox isolation, or the NDA gate;
• resell raw model access or scrape the site in a way that impersonates the product;
• upload content that is illegal, or sexual content involving minors;
• treat preview as a production multi-tenant host for your customers.

We may stop a job, delete an upload, or close an account if this section is broken. Rate limits (builds, questionnaires, upload intents and bytes) apply to every account.

7. Confidentiality (wrap)

For wrap sessions, confidential information includes source, samples, architecture notes, and discovery artifacts. Each side uses that information only to evaluate and perform the engagement, and does not disclose it except to people bound to equivalent terms. Customer materials remain the customer’s. The click-through NDA is the visible gate before source moves; it is not a negotiated MSA.

8. No warranty

The service is provided “as is.” We do not warrant that a first paint will match a particular aesthetic, that wrap will recover every hidden rule, that preview will be available, or that generated code is fit for a regulated production. Founding software will break. Your remedy for a failed job is to retry (repairs may not spend credits) or ask us to look at it.

9. Limitation of liability

To the maximum extent the law allows, Kelvane and its operator are not liable for lost profits, lost data, business interruption, or indirect damages, even if we were told they were possible. Our total liability for a claim relating to the service is limited to the amounts you paid us for Kelvane in the three months before the claim, and to zero where you have paid us nothing. Some places do not allow these limits; they apply only as far as permitted. This does not limit liability that cannot be limited (for example, death or personal injury caused by negligence where that cannot be excluded).

10. Indemnity

You will defend and indemnify us against claims arising from your content, your uploads, your exported app in production, or your breach of these terms or of others’ rights — except to the extent a claim is caused by our willful misconduct.

11. Term and deletion

You may stop using Kelvane and delete sessions. You may email us to close the account. We may suspend or terminate for breach, non-payment, or abuse. After termination we may delete workspaces. Export anything you need first. Sections that should survive (IP, payment already due, confidentiality, no warranty, liability, indemnity, governing law) survive.

12. Governing law

These terms are governed by the laws of India, without regard to conflict-of-law rules. Courts of competent jurisdiction in India have exclusive venue, unless a mandatory consumer law in your country says otherwise. The UN CISG does not apply.

13. Changes

We may update these terms. The date at the top is the effective date. Material changes apply going forward. If you do not agree, stop using the service and export your workspaces.