ReDesk
NewProposals drafted by ReDesk AI in under four minutesSee what's new
Case studySunfield EPC cut feasibility turnaround from 3.4 days to 6 hoursRead the story
Pricing
Sign inSchedule a demo
Legal and compliance

The paperwork, in plain language

Every agreement, policy and addendum that governs your use of ReDesk. Written to be read, versioned in public, and never changed without notice.

AgreementsLast updated 01 May 2026

Service level agreement

Uptime commitment, support response targets and service credits for paid plans.

Uptime commitment

We commit to 99.9% monthly availability for the ReDesk production platform on Growth plans, and 99.95% on Enterprise plans with a signed order form. Availability is measured per calendar month as successful requests over total requests to the platform API and web application.

Live status and historical uptime are published on our status page.

What is excluded

  • Scheduled maintenance announced at least 72 hours in advance, capped at 4 hours per month and run outside 09:00–21:00 IST.
  • Emergency maintenance needed to close a security vulnerability.
  • Failures caused by your network, your equipment, or third-party services you have connected.
  • Beta, preview and sandbox features, which carry no availability commitment.
  • Force majeure events outside our reasonable control.

Service credits

If we miss the commitment in a month, you can claim a credit against the following month's fees. Claims must be made within 30 days of the end of the affected month.

Monthly uptime
Credit
99.0% – 99.9%
10% of monthly fee
95.0% – 98.99%
25% of monthly fee
Below 95.0%
50% of monthly fee

Support response targets

Severity is set by impact, not by the channel you use. We will acknowledge within the target and keep you updated until resolution.

Severity
Definition
First response
S1 — Critical
Production down or data at risk
1 hour, 24×7
S2 — High
Major function unusable, no workaround
4 business hours
S3 — Normal
Function impaired, workaround exists
1 business day
S4 — Low
Question, request or cosmetic issue
2 business days

Incident communication

Any S1 incident gets a status page entry within 30 minutes, updates at least every hour while it is open, and a written post-incident review within five business days covering timeline, root cause and the changes we are making.

Something here unclear?

We would rather explain it than have you guess.