Service Level Agreement (SLA)

Effective: November 16, 2026 for accounts created from that date; December 16, 2026 for existing accountsVersion: 1.0

This English translation is provided for convenience; the Portuguese version prevails in case of divergence.

1. Purpose

This Service Level Agreement (SLA) sets the monthly availability Zenifra commits to deliver for HTTP applications and managed databases, how it is measured, and what you can request when the commitment is not met. It is part of the Terms of Use.

The current platform status and incident history are public at status.zenifra.com.

    2. Monthly commitments

    Availability is calculated for each project, for each calendar month:

    • HTTP application with 1 instance: 99% monthly availability (up to 7 h 12 min of downtime in a 30-day month). With a single instance, the project may restart when a platform server fails, until it comes back on another one.
    • HTTP application with 2 or more configured instances: 99.5% monthly availability (up to 3 h 36 min in a 30-day month). If a platform server goes down, the other instances stay up.
    • Managed database with 1 instance: 99% monthly availability.
    • Managed database with 2 or more configured instances: 99.5% monthly availability.
    • Projects on the free Free, DB-Free, Cache-Free, and Queue-Free plans are not covered by the SLA: they have the same 99% target, but without the compensation in item 5.

    3. What counts as downtime

    Downtime is the period in which the application or database stops responding because of a Zenifra platform failure that affects, at the same time, at least 5% of the HTTP applications or 5% of the managed databases on the platform.

    The following do not count as downtime:

    • failures in the project code, image, dependencies, or configuration;
    • usage above the plan limits, such as memory, disk, or connections;
    • a project stopped by the user or suspended for lack of Credit or for breach of the Terms of Use;
    • third-party services chosen by the user, such as the domain DNS provider, the image registry, or the code repository.

    4. Measurement and period

    Monthly availability is the percentage of minutes in the month in which the project was not down under item 3. The count restarts on the first day of each month.

    The calculation is made exclusively by Zenifra, with the platform own monitoring. Measurements by the user or by third parties do not apply to this SLA.

      5. Compensation

      If the monthly availability of a project on a paid plan falls below the commitment in item 2, you can ask Zenifra not to charge that project for the time the failure lasted. Anything already charged for that period is returned as organization Credit.

      Make the request through support, giving the organization, the project, and the affected period.

        6. Support

        On WhatsApp and phone at +55 (11) 5199-3013, the average response time is up to 1 hour. By email at support@zenifra.com, the average response time is up to 12 hours. These are averages, not commitments.

        The guaranteed response time is up to 2 business days for any matter. It is also the response time for organizations that use only free plans.

          7. Contact

          For questions about this SLA, contact:

          • Email: support@zenifra.com
          • Address: Rua Pais Leme, 215 - Conj 1713 - 05424-150 - São Paulo, São Paulo

          🧾 Updated version

          Version

          1.0

          Last updated

          November 16, 2026

          We respect your privacy

          We use essential cookies to run this site. Measurement and marketing cookies, such as Google Ads, are only enabled when you accept all cookies. Read our cookie policy.