Skip to main content

Early access. Capacity is limited while we finish our provider agreements, so we are onboarding a few customers at a time.

Ratel
  • Home
  • Features
  • Models
  • Pricing
  • Trust Center
  • Docs
  • About
Sign in Request access
⚠

DRAFT — pre-GA. This Service Level Agreement is a pre-GA draft under legal review. During the invite-only beta the Service is provided on a best-effort basis with no binding uptime commitment and no service credits, as set out below. A firm, credit-backed SLA will be introduced at general availability.

Service Level Agreement

Last updated: 12 July 2026 Version: 0.1 — invite-only beta draft

Pre-GA draft. This document is a placeholder under legal review — written to be substantively accurate for the invite-only beta, but not yet the final, counsel-approved version that will govern general availability.

This Service Level Agreement ("SLA") describes the availability and support norms for the Ratel platform (the "Service") and forms part of the Terms of Service. It should be read together with the Terms, which contain the warranty disclaimers and liability limitations that apply to the Service.

Beta status — the headline. Ratel is in an invite-only, pre-general-availability beta. During the beta the Service is provided "as available" on a commercially reasonable, best-effort basis. There is no binding availability guarantee and no service credits are payable during the beta. We publish an availability target below to be transparent about what we aim for and to describe the framework that will firm up at GA — but during the beta it is a goal, not a contractual commitment.

1. Definitions

  • "Availability" — the percentage of time in a calendar month during which the covered Service is materially able to serve inference requests to a running endpoint, calculated as: (total minutes in the month − Downtime minutes) ÷ total minutes in the month × 100.
  • "Downtime" — sustained periods during which a running, correctly-configured endpoint is unavailable due to a fault within Ratel's control, excluding the Exclusions in section 5.
  • "Covered Service" — the production inference endpoints and the control-plane API and portal used to manage them.
  • "Maintenance" — planned or emergency work described in section 4.

2. Covered Service

This SLA relates to the production inference endpoints you deploy and the control-plane API and portal used to manage them. It does not cover: beta or preview features labelled as experimental; the public marketing website; issues arising from the open-weight models themselves (including their output quality); or anything within the Exclusions in section 5.

3. Availability target

Beta target (non-binding): Ratel aims for monthly Availability of 99.5% for the Covered Service. This is an operational goal during the beta and does not create a right to credits or refunds. We monitor availability and use it to drive reliability improvements ahead of GA.

At general availability we intend to introduce a firm, contractually-committed Availability target with a defined service-credit remedy (for example, tiered credits when monthly Availability falls below the committed level). The exact target, measurement method, and credit schedule will be published in the GA version of this SLA and communicated before they take effect.

4. Maintenance

Planned maintenance: we aim to give reasonable advance notice (targeting at least 24 hours) of planned maintenance likely to affect the Service, and to schedule it during low-usage periods where practicable. Emergency maintenance (for example, to address a security vulnerability or urgent stability issue) may be performed without advance notice. Because endpoints run on dedicated GPU instances, some maintenance may require a brief restart or re-provisioning of your instance. Maintenance periods are excluded from Downtime.

5. Exclusions

The following are excluded from Downtime and from any availability calculation:

  • Planned or emergency Maintenance as described above;
  • Factors outside Ratel's reasonable control, including force majeure, internet or upstream network failures, and failures of infrastructure providers beyond Ratel's control;
  • Issues caused by your configuration, code, models, or misuse, including exceeding quotas or resource limits, or use in breach of the Acceptable Use Policy;
  • Suspension or termination in accordance with the Terms of Service or AUP;
  • Beta, preview, or experimental features, and free trial-credit usage;
  • Your failure to follow reasonable operational guidance, or unavailability of your own systems or connectivity.

6. Support

During the beta we provide support on a best-effort basis by email at [support@justratel.com] (and via the contact page), during business hours in the Central European Time zone, excluding public holidays. Our target initial-response norms — again, non-binding during the beta — are:

Severity Description Target first response
Critical Covered Service is down or unusable for you with no workaround Within 1 business day
High Major feature impaired; workaround may exist Within 2 business days
Normal General questions, minor issues, feature requests Within 3 business days

These are response targets, not resolution guarantees. Formal, time-bound support tiers will be defined at GA and may vary by plan.

7. Incident communication

For incidents with broad impact, we aim to communicate status and material updates to affected customers (for example by email or a status notice) and to share a brief summary of significant incidents where appropriate.

8. How this SLA firms up at GA

At general availability this SLA is expected to become binding, with: a committed monthly Availability percentage; a defined measurement methodology; a service-credit remedy and claim process; and support tiers that may differ by plan. We will publish the GA SLA and give notice before it takes effect. Until then, the best-effort framework in this document applies and no credits are payable.

9. Changes

We may update this SLA as the Service evolves toward GA. Updates are posted here with a new "Last updated" date; material changes will be notified as described in the Terms of Service.

This document is a pre-GA draft. It is not final and not legally binding, and it will be reviewed by counsel before it takes effect at general availability.

Related documents

  • Terms of Service — warranties and liability
  • Acceptable Use Policy — use that can affect availability
  • Trust Center · Contact

Product

  • Features
  • Models
  • Pricing
  • Documentation

Trust & Compliance

  • Trust Center
  • Privacy Policy
  • Terms of Service
  • Security

Company

  • About
  • Contact
  • Acceptable Use
  • Service Level Agreement

Legal

  • Data Processing Agreement
  • Cookie Policy
  • Subprocessors
  • Report illegal content

© 2026 Ratel. All rights reserved. Proprietary and confidential.

EU data residency — GDPR-aligned