Kindgi Cloud: terms of service

Version 1.1; effective October 25, 2026

These terms are between your organization (“you”) and Kindgi Inc., a Delaware corporation (“Kindgi”, “we”). They cover Kindgi Cloud, where we run Kindgi for you, at platform.kindgi.com.

Accepting them:

You accept these terms when you sign up for Kindgi Cloud, on behalf of your organization. You confirm you’re allowed to bind it.
We record which version you accepted, who accepted it, and when. If you want a copy signed by both of us, write to contact@kindgi.com.

What they include:

the data processing addendum, for personal data we process for you;
the price list at the end.

Our Terms of use still apply to our sites (their Part A). Privacy at Kindgi says how we handle your account’s information.

Kindgi Cloud is for organizations, for business use. It isn’t for personal or household use.

1. What Kindgi Cloud is

What we run for you: the Kindgi runtime and your packs (your agents, tools and flows), in Google Cloud’s us-central1 region (Iowa, USA).
How it’s organized:
- your organization has one workspace;
- each of your clients gets a project in it;
- each of your packs runs in its own isolated service.
What stays on your side: you build and test on your own machine with the Kindgi SDKs and CLI, under their Apache-2.0 license, and deploy to Kindgi Cloud.
No separate license: use on Kindgi Cloud, production included, is part of your subscription, so you don’t need the runtime’s production license for it. The runtime’s own licenses (Business Source License 1.1, and the production license) apply only when you run the runtime yourself.

2. What it includes today, and what it doesn’t yet

Kindgi Cloud is new. Its first version (v1) includes:

many organizations on one shared service, each kept apart from the others (the data processing addendum, Annex II);
each pack in its own sandboxed service, reaching only the public internet;
your agents started by your apps, by events (a new order, for example) or on a schedule;
approvals in the console and by email, by named people;
the full record of every run, with its cost.

v1 doesn’t yet have the following. We’ll tell you when each one arrives:

A separate encryption key per workspace. One key protects every workspace’s stored secrets. Deleting your secrets deletes them one by one, and copies in backups stay encrypted until those backups age out (the data processing addendum, sections 5 and 9).
Fixed outbound IP addresses. A client system that admits only known addresses can’t yet admit only us.
A choice of region. Everything runs in one US region, us-central1.
An uptime guarantee (SLA), or service credits (section 10).
A page with your usage. We count your runs, tool calls, approvals and model calls, per organization, project and agent, and apply your limits from those counts. You can’t see the totals yet; each run’s record shows its cost.
A security certification of our own, such as SOC 2. Google Cloud’s certifications cover the infrastructure; we don’t claim one for Kindgi.

3. Your account

When you sign up:

We check your email address by sending a link, and a bot check protects the page.
Give us accurate details: your organization’s legal name, address, billing contact and tax details. Keep them up to date.
Sign up once for your organization. Don’t create accounts to get around limits or the founding-price cap.

You’re responsible for your workspace:

the people you add, and the roles you give them;
everything done under your account;
keeping your API keys, signing keys and sign-in sessions secret.

If one leaks, revoke it in the console and tell us at contact@kindgi.com.

4. Building, testing and going live

Building, testing and staging are free. You pay only for the projects you set live, as live stores (the price list).
kindgi dev runs Kindgi on your own machine. Each preview release of it stops starting 90 days after it came out, and warns from 30 days before. Update the Kindgi CLI to keep going (preview releases). It doesn’t affect what we run for you on Kindgi Cloud.
Before you set a project live, you pay for it. You choose how many live stores to pay for, and pay the first month on Stripe’s page. Each project you set live takes one of them. To set more projects live than you’ve paid for, add stores on your billing page first (section 9).
Setting a project live means switching it to production, in the console, the CLI or the API. A project you’ve set live is “live”.
- When to set it: when the project serves end users or customers, or processes live business data as part of an organization’s operations. That’s what the published Terms of use call production, and it includes internal systems your own people use.
- You can set it back at any time. That frees its live store for another project. You keep paying for the store until you remove it (section 9).
- Don’t run live use from a project that isn’t set live (section 7).
A person at Kindgi looks at each organization when it first pays for live stores, or, for an organization in a preview, when we admit it. The look is at who your organization is (its account and billing details), never at what you built or your workspace’s data. We see those only as the data processing addendum (section 4) allows.

5. Your models: bring your own key

The model provider is yours. You register your own account with a model provider in your workspace, with your own key, and your packs call it with that key. The provider bills you directly, under its own terms.
We never resell model use. Model costs never appear on our invoices. We show you what each model call cost at your provider’s prices, for your information.
What your packs send to your model provider, or to any other service they call, goes there on your instruction, under your agreement with that service.

6. Your content and your code

Yours stays yours:

What you put into Kindgi Cloud, and what your packs produce, is yours: your packs, your data and your clients’ data.
You give us only the rights we need to host it, run it, store it, copy it, send it where your packs send it, and show it to you, so that we can provide Kindgi Cloud.
We don’t use it to train AI models, ours or anyone else’s. We don’t sell it, and we look at it only as the data processing addendum (section 4) allows.

You’re responsible for:

Permissions: having the rights and permissions for the data your packs handle, including your clients’ and their customers’ data.
What your agents do: the tools they call, the actions they take, what they say, and the approvals you put in front of them. AI output can be wrong, so decide where a person must approve.
The law that applies to your agents, for example privacy law, consumer protection, and rules that you tell people when they’re talking to an AI.
The credentials your clients give you, and keeping them in Kindgi Cloud’s secrets, not in your code.

7. Acceptable use

Don’t use Kindgi Cloud to:

break the law, or infringe anyone’s rights;
cause harm: send spam or phishing, spread malware, or host illegal content;
attack or probe anything: scan, probe or attack a system you don’t have permission to test.
- That includes Kindgi Cloud and other organizations on it.
- Don’t try to get out of your pack’s sandbox, or reach other organizations, our infrastructure, or the cloud’s metadata services.
- Found a security problem? Tell us at contact@kindgi.com. Testing Kindgi Cloud needs our written permission first.
run unrelated workloads: mine cryptocurrency, or run proxies, VPNs or general computing that isn’t your agents, tools and flows;
get around controls: limits, the live stores you’ve paid for, usage counting or the founding-price cap;
resell Kindgi Cloud itself as hosting. You can build and run agents for your own clients, and charge them for your work and for their use;
store sensitive data we haven’t agreed to, as the data processing addendum’s section 2 lists;
avoid paying: serve end users or customers, or process live business data, from a project that isn’t set live (section 4);
break sanctions: use it from a country, or for a person, that US sanctions or export controls forbid.

8. Limits

Each organization has limits:

on runs and how many run at once;
on each pack’s instances, memory and request time.

They keep the shared service fair and safe for every organization.

Changes: we tell you 30 days before we lower a limit, unless we must act sooner to protect the service.

Need more? Write to us.

9. Prices and invoices

The prices are in the price list at the end.
Paid monthly, in advance. Your organization has one subscription, through Stripe. Each month, it pays upfront for the number of live stores you’ve chosen. It renews each month until you remove every live store (below) or close your account (section 13).
Changing the number:
- Adding a live store charges the rest of the current month straight away.
- Removing one gives a credit for its unused time, toward your next invoice. We don’t pay credits out in cash. You can remove only a store no project is using, so set a project back first (section 4).
- Removing every store ends the subscription. What’s left of the month is kept as a credit toward your next invoice, if you pay again. Your account stays, and building and testing stay free.
Invoices and receipts come from Stripe, by email. Your billing page links to Stripe’s page for your payment card, your invoices, your billing address and your tax ID. We never see or store your card.
Taxes: prices don’t include taxes. We add any sales tax, GST/HST or VAT that applies.
Questions about an invoice: write within 30 days of receiving it. If we made a mistake, we correct it.
If a payment fails:
- Stripe tries again over the next 2 weeks, and we email your billing contact.
- Meanwhile, your live projects keep running, but you can’t set another project live.
- If it’s still unpaid after the last try, we suspend your account (section 12) until your open invoices are paid.
- We never delete anything for non-payment while your account is open.
Price changes: we tell you by email at least 30 days before a new price applies. Founding prices are locked as the price list says.

10. Support

How to reach us: email contact@kindgi.com.
When: every day, weekends included.
How fast:
- a first reply within 24 hours;
- best effort on the fix.
No uptime guarantee: there’s no service level agreement (SLA), and no service credits, in v1.
Incidents that affect your data: we tell you by email without undue delay, and within 72 hours of knowing about them (the data processing addendum, section 8).
Planned maintenance: we email you at least 48 hours ahead.
Security problems: report them to contact@kindgi.com.

11. Your data, privacy and security

The data processing addendum covers the personal data we process for you:
- where it’s stored: in the USA, in us-central1, with database backups in Google Cloud’s us multi-region;
- how it’s protected;
- how long it’s kept, and how it’s deleted;
- who our sub-processors are;
- what happens when your data comes from the EU, the UK, Canada or a US state with a privacy law.
Usage counts and the service’s technical records: we use them to run, secure and support Kindgi Cloud, to apply your limits and to show you your usage. They’re not your content.

12. Suspension

We can suspend a pack, a project or your account if:

an invoice stays unpaid after Stripe’s last try (section 9);
you break section 7;
something you run puts Kindgi Cloud or other organizations at risk;
the law requires it.

How we do it:

We suspend only as much as we need to.
We tell you first where we reasonably can, or else as soon as we can.
We restore service promptly once the reason is gone.
For an unpaid invoice, the suspension is automatic, and we email your workspace’s admins and billing contact when it happens. Your account runs again on its own once your open invoices are paid.

While something is suspended, nothing in it runs. You can still sign in, read your data and export it. A suspension doesn’t delete your data.

13. Ending

You can close your account at any time, by email to contact@kindgi.com. We confirm it within 24 hours. Your subscription ends that day: nothing more is billed, and what you’ve paid isn’t refunded. An invoice that’s still unpaid stays due.
We can end these terms:
- with 30 days’ notice;
- or straight away, if you seriously or repeatedly break section 7;
- or if you break these terms in another important way and don’t fix it within 10 days of our notice.
If we stop offering Kindgi Cloud altogether, we give you at least 90 days’ notice.
If we end these terms with 30 days’ notice, or stop offering Kindgi Cloud, we refund the part of your last paid month that comes after your account ends, to the card you paid with. We don’t when we end them because you broke them.
After your account ends, nothing runs any more, and you stop paying. As the data processing addendum (section 9) says:
- you can export the data stored in your workspace for 30 days, except secret values, which can’t be read back, by design. Your packs’ operational logs are kept for 30 days for operations and aren’t exported (section 9 of the addendum says what the export covers);
- we then delete your workspace, within 7 days after those 30 days.

Sections 6, 7, 9 (for amounts owed), 13 and 15 to 21 continue to apply after these terms end.

14. Changes to Kindgi Cloud and to these terms

We improve Kindgi Cloud all the time. If we remove or reduce something important you use, we tell you at least 30 days ahead.
When we change these terms, we update their version and date at the top.
- A material change: we email your workspace’s admins and billing contact at least 30 days before it applies. Using Kindgi Cloud after that means your organization accepts the new version, and we record it.
- If you don’t accept it: close your account before it applies, and you won’t pay for any use after that day.

15. Confidentiality

Each of us keeps the other’s non-public information confidential, and uses it only for these terms. That covers your content, our non-public plans and prices, and anything either of us marks as confidential.

It doesn’t cover information that:

is public, through no fault of the one who received it;
the receiver already had, or got lawfully from someone else;
the receiver developed independently.

If the law requires one of us to disclose the other’s confidential information, we tell the other first where the law allows.

16. Feedback and publicity

Feedback: if you send us ideas or suggestions, we can use them freely.
Publicity: we don’t name your organization as a customer without your permission.

17. What we promise, and what we don’t

What each of us promises: that it may agree to these terms.
What we promise you: we provide Kindgi Cloud with reasonable skill and care, as these terms describe it.
Everything else is “as is”: to the extent the law allows, Kindgi Cloud is otherwise provided “as is” and “as available”, without other warranties, express or implied. That includes merchantability, fitness for a particular purpose and non-infringement.
No guarantees on:
- uptime: we don’t promise Kindgi Cloud will be uninterrupted or error-free;
- AI output: we don’t promise that what your agents or your model provider produce is correct.

18. Limitation of liability

To the extent the law allows:

No indirect losses: neither of us is liable to the other for indirect, incidental, special, consequential or punitive damages, or for lost profits, revenue, data or business, arising from these terms or Kindgi Cloud.
Our total liability for all claims about Kindgi Cloud is limited to the greater of:
- the amount your organization paid us for Kindgi Cloud in the 12 months before the event that caused the claim;
- USD 100.
Exceptions: these limits don’t apply to your payment obligations, to section 19, or to a breach of section 7.

Some places don’t allow these limits, so they may not all apply.

19. If someone makes a claim against us because of you

Your organization defends Kindgi against third-party claims arising from:

your content;
your packs and what they do;
your clients’ use of what you build;
a breach of section 7.

It also pays what a court awards, or what you agree to in a settlement.

What we do in return:

tell you promptly about the claim;
let you control the defense;
help you reasonably, at your cost.

20. Governing law

These terms are governed by the laws of the State of Delaware, USA, without regard to its conflict-of-laws rules. Any dispute about them goes to the state or federal courts in Delaware, and both of us agree to their jurisdiction.

21. General

The whole agreement is these terms, the data processing addendum and the price list.
- Where they disagree about personal data, the addendum wins.
- Otherwise these terms win over the published Terms of use, for Kindgi Cloud.
Assignment:
- Neither of us may transfer these terms without the other’s consent.
- Either of us may transfer them to a successor in a merger or a sale of its business, with notice.
Events beyond our control: neither of us is liable for a delay or failure caused by something beyond its reasonable control, such as a cloud provider’s outage. Your payment obligations aren’t excused this way.
Notices:
- to us: contact@kindgi.com;
- to you: your workspace’s admins and billing contact, by email.
The rest of the agreement survives:
- if a court finds part of these terms unenforceable, the rest still applies;
- not enforcing a term isn’t a waiver of it.
Independence: we’re independent contractors. Nothing here makes us partners or agents of each other.

22. Contact

Kindgi Inc., 500 Westover Dr #38104, Sanford, NC 27330, USA. contact@kindgi.com

Price list

Prices are in US dollars, paid monthly in advance, plus any tax that applies (section 9).

Free:

building, testing and staging;
tests, dry runs, replays and evaluations.

A live store: $19 a month. Each project you set live takes one live store (section 4), and you choose how many to pay for. There’s no charge per agent or per run: fair use applies, within your limits (section 8).

Founding price: $10 a month for each of the first 250 live stores across Kindgi Cloud.

An organization can hold at most 20 founding stores.
They keep the founding price until 24 months after your organization’s first paid month, while your subscription stays active. Your billing page shows the date, and we email your billing contact at least 30 days before it. If the subscription ends, the founding price ends with it.
After that, each of them is $19 a month.
A founding store, once given, counts toward both numbers for good: removing it doesn’t free it, for you or for anyone else.

The apps preview: free. An organization we admit to the apps preview hosts one live app free until Kindgi 1.0, within your limits (section 8). We give at least 60 days’ notice by email before any charge, and nothing is charged until you choose a plan. For more than one live app, contact us.

Model use: none from us. Your model provider bills you (section 5).

What the words mean:

A live store: one paid place for a project you’ve set live (section 4), usually one client’s store or site, whatever runs in it.
A live app: the same, for an organization in the apps preview.