Terms of service

Last updated November 10, 2026. About 15 minutes to read.

SmalBlu Technologies Private Limited, E-603, Iscon Platinum, Nr Bopal Cross Road, Bopal, Ahmedabad, Daskroi, Gujarat 380058, India. CIN U62013GJ2023PTC146272.

Contents

These terms are the contract between your company and smalBlu. smalBlu connects to your cloud and, if you allow it, makes changes there. So these terms say who is responsible for what when that happens, in words an engineer and a lawyer can both read.

1About these terms

1.1

These terms are between SmalBlu Technologies Private Limited, E-603, Iscon Platinum, Nr Bopal Cross Road, Bopal, Ahmedabad, Daskroi, Gujarat 380058, India, CIN U62013GJ2023PTC146272 ("smalBlu", "we") and the company named in the order ("you").

1.2

The contract is made of the order, these terms and the data processing agreement (DPA). If they conflict, the order comes first, then the DPA on personal data, then these terms.

1.3

The service is for businesses. It is not for consumers or for personal use. The person who signs or clicks to accept confirms that they have authority to bind the company.

1.4

If you only browse our website, sections , and apply to that use.

2The free cloud review

2.1

The free cloud review is a read-only look at the accounts you connect. We make no changes during it.

2.2

It is free, and you have no duty to buy anything afterward.

2.3

Findings are estimates. Any saving shown is an up to figure, and it is not a promise.

2.4

If you do not place an order, remove our role. We delete what we read within 30 days of the end of the review. A6

2.5

Sections , , , , and apply to the review. Because it is free and read-only, our total liability for it is limited to US$1,000. A15

3What the service does

3.1

We run the cloud accounts and layers named in your order. That work is to observe, recommend, simulate, apply within your rules, and log.

3.2

The service combines software, AI and our engineers. You deal with one team, and our engineers stand behind the changes we apply.

3.3

The service works across AWS, Microsoft Azure, Google Cloud and on-prem. Each order names the platforms it covers.

3.4

We may improve the service over time. We will not make a change that materially reduces what you ordered without telling you, and you may then end the affected part and receive a refund of any fees paid in advance for it.

3.5

We do not provide uptime commitments or service credits unless your order says so. A15

4Your approvals and guardrails

4.1

We start read-only. We make no change until you give us a separate role for changes.

4.2

Your guardrails are the rules you set: what may run without asking, on which resources, up to what limits, in which time windows, and what is off limits.

4.3

A change goes ahead only if it fits a guardrail or an approver named by you has approved it. An approval given by your approver through the agreed channel binds you.

4.4

Changes that cannot be undone. A change that deletes data, or that cannot be reversed, needs a person's approval each time unless a guardrail names that exact action. A14

4.5

Emergencies. We do not act outside your guardrails during an incident unless you have written an emergency guardrail or your approver tells us to.

4.6

You can change a guardrail or pause all changes at any time. This applies to new work at once. A change already running will finish or roll back, whichever is safer. A14

4.7

We simulate changes before applying them. A simulation is an estimate. Real systems can behave differently.

4.8

Every action is written to the action log. If there is a dispute about what happened, both of us will treat the log as the starting record, and you may show it is wrong.

5Who is responsible for what

5.1

A change you approved. You are responsible for the decision. We are responsible for carrying it out as approved, with reasonable skill and care.

5.2

A change inside your guardrails. You are responsible for the rule. We are responsible for staying inside it and for applying the change with reasonable skill and care.

5.3

A change outside your guardrails and without approval. That is our responsibility. We will tell you at once, roll it back where we can, and cover your reasonable cost of putting things right, up to the limits in section .

5.4

A recommendation you did not take. That is your decision, and we are not responsible for what follows from it.

5.5

Roll back. For each change we keep a plan to reverse it where that is technically possible. When a change causes a problem, we help fix it, whoever was responsible.

5.6

Your cloud provider. We are not responsible for outages, faults or price changes at your cloud provider. You pay your cloud bills directly.

5.7

Your backups. You stay responsible for backups and disaster recovery unless your order says otherwise.

JobYour teamBothsmalBlu
Creating, limiting and removing our rolesYes  
Setting guardrails and naming approversYes  
Keeping your backups and recovery planYes  
Paying your cloud billYes  
Deciding whether to approve a changeYes  
Reviewing the action log Yes 
Fixing a change that caused a problem Yes 
Finding and simulating changes  Yes
Staying inside your guardrails  Yes
Applying changes with skill and care  Yes
Logging every action  Yes
Protecting the data we hold  Yes
SituationWho allowed itDecisionCarrying it outClause
You approved a resize and it hurt performanceYour approverYousmalBlu, with skill and care5.1
A rule you wrote stopped idle servers that were neededYour guardrailYousmalBlu, staying inside the rule5.2
We changed something outside your rulesNobodysmalBlusmalBlu: tell you, roll back, cover the cost5.3
We recommended a fix and you left itNobodyYouNobody5.4
AWS had an outageNobodyAWSAWS5.6

6Access and credentials

6.1

You give us access through roles you create in your own account. We ask for the least access the work needs.

6.2

We will not ask for your root login, passwords or long-lived keys. A1

6.3

We use your access only to provide the service, and we keep any credentials encrypted. A10

6.4

You may reduce or remove our access at any time. If that stops us doing part of the work, we are not in breach for that part, and fees continue until the contract ends.

6.5

Each of us will tell the other at once if we suspect that access has been misused.

7Your responsibilities

7.1

You confirm that you have the right to connect the accounts you give us, and that doing so does not breach your agreements with your cloud provider or anyone else.

7.2

You will name approvers and an escalation contact, and keep those details up to date.

7.3

You will keep your guardrails accurate. We rely on them.

7.4

You will not put secrets or sensitive personal data in resource names or tags.

7.5

You are responsible for how your own staff use the service, and for the personal data in your cloud.

8Acceptable use

8.1

You will not, and will not let anyone else:

  • use the service or website against the law, or for anything harmful
  • probe, attack or overload the service, or try to get around its security
  • copy, reverse engineer or resell the service, except where the law allows this and it cannot be excluded
  • use the service or its outputs to build or train a competing product
  • connect accounts you have no right to connect
  • use the service in breach of Indian or other applicable export control or sanctions laws
8.2

We may suspend access if a breach puts the service or other customers at risk. We will tell you first where we can, keep the suspension as narrow as we can, and lift it once the risk has passed.

9Fees and payment

9.1

You pay the monthly fee in your order. It is based on the infrastructure we run for you and is quoted per customer.

9.2

We invoice monthly in advance. You pay within 30 days of the invoice date, in the currency in the order. A15

9.3

Fees do not depend on savings or on any other result, except under the smalBlu guarantee in 9.10.

9.4

Fees exclude taxes. You pay any goods and services tax or similar tax that applies. If the law makes you withhold tax, you will send us the certificate on time so that we can claim the credit. A15

9.5

If the infrastructure we run grows or shrinks materially, either of us may ask to adjust the fee. We will agree the change in writing. A15

9.6

We may change fees at renewal with 30 days' notice. If you do not accept the change, you may end the contract before it applies.

9.7

If an undisputed invoice is more than 15 days late, we may charge interest of 1% a month and, after 15 more days' written notice, pause the service. A15

9.8

If you dispute an invoice in good faith, tell us within 30 days and pay the rest.

9.9

Fees already paid are not refundable, unless these terms or the law say otherwise.

9.10

The smalBlu guarantee. If, in a contract year, your savings from the service are less than the fees you paid us for that year, we pay you the difference. A contract year is each 12 months from the start date in your order. How savings are measured, when you claim and when we pay are set out in your order. A17

10Confidentiality

10.1

Each of us will keep the other's confidential information private, use it only for this contract, and share it only with staff, advisers and vendors who need it and must keep it private.

10.2

Confidential information includes customer data, your architecture and costs, our pricing, our methods, and anything marked or plainly confidential.

10.3

This does not cover information that is public through no fault of the receiver, that the receiver already held or developed on its own, or that it received lawfully from someone else.

10.4

If the law requires disclosure, the receiver will tell the other first, where that is allowed, and disclose only what is required.

10.5

These duties last for the contract and five years after. For customer data, they last for as long as we hold it.

11Data

11.1

Customer data means the data we read from your cloud and what we create from it for you, such as recommendations and logs. You own it.

11.2

You give us the right to use customer data only to provide the service to you, and to meet our legal duties.

11.3

Customer data does not train AI models, ours or anyone else's. If an outside AI model processes it, this happens under terms that forbid training. A3 A4

11.4

Our staff may see customer data only to run the service. A5

11.5

We do not read the contents of your databases or storage objects. The privacy policy sets out what we read and what we do not. A1 A2

11.6

We may keep totals that cannot identify you or your infrastructure, to run and describe our business.

11.7

Our privacy policy and DPA apply to personal data. SOC 2 and ISO 27001 are in progress and we do not hold them today. Nothing here is a promise of certification.

12Intellectual property

12.1

We and our licensors own the service, its software, models, methods and website. You receive the right to use the service during the contract, and no other rights.

12.2

You own your customer data, your cloud and your code.

12.3

Reports, recommendations, logs and configuration we produce for you are yours to use in your business, during and after the contract. This does not give you rights in our software or methods.

12.4

If you give us feedback, we may use it freely, without using your confidential information.

12.5

Neither of us will use the other's name or logo without written permission.

13AI output

13.1

Parts of the service use AI to produce recommendations, explanations and simulations. AI output can be wrong, incomplete or out of date.

13.2

Please review recommendations before approving them, and write guardrails with that in mind. Simulations reduce the risk of a change. They do not remove it.

13.3

Our responsibility for changes is set out in section . Section does not reduce it.

13.4

AI output is about your infrastructure. It is not legal, financial, tax or compliance advice.

13.5

Similar infrastructure can lead to similar recommendations for different customers. That does not mean any customer's data was shared.

14Warranties

14.1

Each of us confirms that it has the authority to enter into this contract.

14.2

We will provide the service with reasonable skill and care, and it will do materially what we describe.

14.3

We will comply with the laws that apply to us in providing the service.

14.4

We do not promise any particular result. Figures on our website, including up to 50% lower cloud bill, up to 30% better performance and up to 70% engineering hours saved, are up to figures and not commitments.

14.5

We do not promise that the service will be uninterrupted or free of errors.

14.6

If the service does not meet section , tell us and we will correct it. If we cannot do that within 30 days, you may end the affected part and receive a refund of fees paid in advance for it.

14.7

Except as these terms say, all other warranties are excluded to the extent the law allows.

15Liability

15.1

Cap. Each party's total liability under this contract is limited to the fees paid or payable in the 12 months before the event that caused the claim. A15

15.2

Higher cap. For a breach of section or 11, the limit is 2 times that amount. This higher limit is the total for those breaches and is not added to the limit in 15.1. A15

15.3

Losses neither of us can claim. Neither of us is liable for indirect or consequential loss, or for loss of profit, revenue, goodwill or anticipated savings.

15.4

Direct loss from a change. If we apply a change outside your guardrails and without approval, your reasonable cost of fixing it, and the extra cloud cost it caused until it was fixed, count as direct loss and fall within section .

15.5

No cap. Nothing limits liability for fraud, for deliberate wrongdoing, for the indemnity in section , for your duty to pay fees, or for anything the law does not allow us to limit.

15.6

Each of us will take reasonable steps to reduce any loss.

16Indemnity

16.1

From us. We will defend you against a third-party claim that the service, used as these terms allow, infringes that party's intellectual property rights, and pay the damages awarded or settlement we agree. If this happens we may change the service, obtain the right to keep it, or end the affected part and refund fees paid in advance for it.

16.2

From you. You will defend us against a third-party claim arising from your breach of section or section , and pay the damages awarded or settlement you agree.

16.3

How it works. The party claiming protection must tell the other quickly, let it control the defense, and give reasonable help. Neither of us will settle in a way that admits fault for the other without its agreement.

16.4

Section does not cover claims caused by your data, your changes to our outputs, or use outside these terms.

17Term and termination

17.1

The contract starts on the date of the order and lasts for the term in it. If no term is stated, it runs month to month. A15

17.2

A fixed term renews for the same length unless either of us gives 30 days' notice before it ends. A month-to-month contract ends on 30 days' notice. A15

17.3

Either of us may end the contract at once by written notice if the other materially breaches it and does not fix the breach within 30 days of being told, or if the other becomes insolvent.

17.4

If you end the contract for our breach, we refund fees paid in advance for the period after it ends. If we end it for your breach, the fees for the rest of a fixed term become due.

17.5

Sections that by their nature should continue will continue, including 10, 11, 12, 15, 16, 18 and 19.

18When the service ends

18.1

On the end date we stop all changes and stop reading your accounts.

18.2

Within 30 days we make your action log, findings, guardrails and any configuration we produced available to you in a standard format.

18.3

You remove our roles from your accounts. We will tell you which ones to remove.

18.4

We delete customer data within 30 days of the end date, and it leaves our backups within 60 days. We keep the action log for 12 months, and invoices and records for as long as the law requires. We will confirm deletion in writing if you ask. A6 A12

18.5

Changes already made stay in your cloud. They are yours. We will not leave anything in your cloud that stops working because we have left, unless we told you about it first. A14

18.6

If you would like help with handing over, we can agree this in writing at our usual rates.

19Governing law and disputes

19.1

Indian law governs this contract.

19.2

If a dispute arises, senior people from both sides will try to resolve it within 30 days of written notice.

19.3

If they cannot, the dispute will be finally resolved by arbitration under the Arbitration and Conciliation Act 1996, before one arbitrator agreed by both of us or appointed under that Act. The seat and venue will be Ahmedabad, and the language will be English. A16

19.4

The courts at Ahmedabad have exclusive jurisdiction over anything that cannot go to arbitration, and over requests for urgent relief. A16

20General terms

20.1

Whole agreement. This contract is the whole agreement on its subject, and replaces earlier discussions. Terms on your purchase order do not apply.

20.2

Changes to these terms. We may update these terms with 30 days' written notice. A change that is worse for you applies from your next renewal. For a month-to-month contract, you may leave before it applies.

20.3

Assignment. Neither of us may transfer this contract without the other's written agreement, except to a successor in a merger or sale of the business, with notice.

20.4

Subcontractors. We may use subcontractors and remain responsible for them. Companies that handle personal data are listed in our privacy policy.

20.5

Events beyond control. Neither of us is liable for delay caused by events beyond its reasonable control, such as a major outage of the cloud provider, war, natural disaster or government action. This does not excuse payment.

20.6

Notices. Legal notices are sent by email to the contacts in the order and to hello@smalblu.ai, and take effect the next business day.

20.7

Relationship. We are independent companies. Neither of us is the other's agent or employee.

20.8

Anti-corruption. Each of us will comply with applicable anti-bribery and anti-corruption laws.

20.9

Waiver and severance. Not enforcing a right does not waive it. If part of these terms cannot be enforced, the rest stands.

20.10

Electronic signatures. The contract may be signed electronically and in counterparts.

20.11

Language. This contract is in English.

21Contact

21.1

Questions and legal notices: hello@smalblu.ai.

21.2

Post: SmalBlu Technologies Private Limited, E-603, Iscon Platinum, Nr Bopal Cross Road, Bopal, Ahmedabad, Daskroi, Gujarat 380058, India.