Skip to content

Legal · Last updated August 20, 2026

Service Level Agreement

What we commit to keeping available, how we measure it, what we do not count, and what you get back from us when we miss. The number is deliberately one we can hold.

1. Who this applies to

This Service Level Agreement applies to a Workspace on a paid plan for the billing period it has paid for. It forms part of our Terms of Service and uses the terms defined there.

It does not apply to the Free plan, to a Beta Feature, or to a Workspace that is suspended for non-payment or for breach of the Terms. A Beta Feature is any feature, model, connector or template we identify as alpha, beta, preview, early access or experimental.

2. What we commit to

We commit to a Monthly Uptime Percentage of 99.5% for each of the following, measured separately:

  • The Vibely platform — the dashboard at vibely.sh and the API at api.vibely.sh, including signing in, opening a Project, and starting an agent turn.
  • Published Apps — serving a Published App on its vibelyagent.com subdomain or on a custom domain you have connected through us.

3. What 99.5% means in minutes

99.5% of a 30-day month leaves 3 hours and 39 minutes of downtime before we owe you a service credit. We are stating the number we can hold with the infrastructure we run today rather than a number that reads better. If you need a higher commitment, ask us before you sign an Order — we will either write it or tell you we cannot.

4. How uptime is measured

The measurement window is one calendar month, in UTC. Monthly Uptime Percentage is (total minutes in the month minus Downtime Minutes minus Excluded Minutes), divided by (total minutes in the month minus Excluded Minutes), expressed as a percentage.

A minute is a Downtime Minute when the Service was unreachable or returned server errors for that whole minute. Slower-than-usual responses are not downtime.

Be aware of how we measure it. We do not operate third-party synthetic monitoring outside our production network today, and we do not run a public status page. Downtime is assessed from our own server-side and infrastructure provider logs, together with whatever evidence you send us. Send your evidence with the claim — timestamps, error responses, your own monitoring output — and we will weigh it alongside ours rather than treat our logs as the last word.

5. What is not downtime

The following are excluded from Downtime Minutes and count as Excluded Minutes where they occur inside a window we announced:

  • Scheduled maintenance announced as described below, and emergency maintenance.
  • Force majeure — events outside our reasonable control, including network or power failure at a facility we do not operate, government action, and natural disaster.
  • Anything caused by you: your application code, your Project configuration, a DNS or domain record you control, exhausting your Credits, or a suspension for non-payment or breach.
  • Failures of third parties we do not control — AI model providers, connector providers and the services your app calls, app stores, domain registrars, and the third-party accounts you connect.
  • Beta Features, and any feature made available to you outside a paid plan.
  • A paused sandbox. A sandbox that has been inactive for 72 hours is recycled by design; the Project recovers from its snapshot or its stored files on the next request.

6. This is an availability commitment, not a quality one

The commitment above is that the Service is reachable and responding. It is not a commitment about what the agent produces. Generated Output may contain inaccuracies and is not warranted to be fit for any particular purpose, and a turn that runs and returns a result you did not want is not downtime.

7. Scheduled maintenance

Our scheduled maintenance window is Sunday 18:00 to 22:00 UTC. We do not use the whole window, and most releases need no window at all.

We email Workspace owners at least 5 days before scheduled maintenance that we expect to interrupt the Service, with the date, the window, and what will be affected.

Emergency maintenance — a security fix or a fault that is actively causing harm — can happen at any time. We give as much notice as the situation allows and tell Workspace owners afterwards what happened.

8. Service credits

If we miss the commitment for a month, you can claim a service credit against the fees for the affected Workspace for that month. The thresholds apply to each commitment separately:

  • Below 99.5% and at or above 99.0% — 10% of the monthly fee.
  • Below 99.0% and at or above 95.0% — 25% of the monthly fee.
  • Below 95.0% — 50% of the monthly fee.

9. How a credit is calculated and applied

The monthly fee is what you paid for the affected Workspace for that calendar month. On an annual Order it is one twelfth of the annual fee. Credits purchased as top-ups are not part of the monthly fee and are not credited.

Service credits are applied against your next invoice or as Credits added to your Workspace, at our choice. They are not paid in cash and are not refunded. Total service credits for any single month will not exceed 100% of that month’s fee, including where both commitments are missed in the same month.

10. Service credits are the only remedy

Service credits are your sole and exclusive remedy for any failure to meet the commitment in this SLA. Nothing in this section limits any right you have as a consumer under the law that applies to you.

11. How to claim

Email [email protected] from the address on the account within 30 days of the end of the month you are claiming for. Include the Workspace name, the month, which commitment you say we missed, and the dates and times you saw the Service unavailable. We will respond within 30 days with the calculation and, where the claim is good, the credit. A month not claimed within 30 days of its end is closed.

12. Repeated failure

If we fall below 99.0% on the same commitment in three consecutive months, you may terminate your subscription by written notice within 30 days of the third month. We will refund the prepaid fees for the unused remainder of your term, including the pro-rata portion of an annual fee. That refund is created by this Service Level Agreement and survives the general rule in our Refund and Cancellation Policy.

13. Changes to this SLA

We give at least 14 days’ notice of material changes to this SLA by email or in-product notice. Where an Order states an uptime commitment, that Order wins for its term.

14. Contact

Claims and questions about this SLA: [email protected]. Vibely is operated by Mana Intelligence Private Limited, incorporated in India.

Questions about this document? Email[email protected].