Scope and definitions
- 1.1
This SLA sets out the service level provided by Michał Fox, ul. Józefa Mackiewicza 25, 31-214 Kraków, Poland ("we") under the Flaem licence. It is part of the Agreement described in the licence terms, and capitalised terms have the meaning given there.
- 1.2
The SLA applies for the whole duration of the Agreement, including any notice period.
- Business hours
- 9:00 to 17:00 Polish time, on Business days.
- Business day
- in response times, means 8 Business hours.
- Month
- a calendar month.
- Downtime
- every full minute in which the Licence server does not respond correctly to activation and heartbeat requests, subject to the exclusions in clause 4.4.
- Availability
- the percentage of minutes in a Month that are not minutes of Downtime.
- Support request
- an email to support sent to hello@flaem.net as described in section 7.
What the SLA covers
- 2.1
The Licence server: activating Installations with a Licence key, receiving heartbeats and delivering renewals and changes to the Licence scope. For the Licence server we guarantee the Availability in section 4.
- 2.2
The Release channel: publishing signed Software releases and the file listing new versions at flaem.net/releases. We keep it running without interruption, but it is not covered by the Availability target. An outage only delays downloading updates and does not affect how the Installation runs.
- 2.3
Support: answers to Support requests about Software bugs, installation, Software configuration, updates and the Licence, within the times in section 6.
What the SLA does not cover
- 3.1
Flaem runs on the Licensee's infrastructure, so the SLA does not cover:
- the availability of the Installation, the panel and the services of Customers of the Licensee, which depends on the Licensee's machines, network and data centre,
- the Licensee's machines, operating system, Docker, Proxmox VE, network, power and backups,
- external services the Installation connects to, in particular payment gateways, KSeF, domain registrars and DDoS protection providers,
- the effects of changes to the Software's code or database made by the Licensee or third parties,
- building custom features to order and administering the Licensee's servers.
- 3.2
If diagnosing a Support request shows that the cause lies outside the Software, we tell the Licensee and, where we can, point to what to check, without guaranteed times.
Licence server availability
- 4.1
We guarantee Licence server Availability of at least 99.5% in every Month. That means at most 216 minutes of Downtime in a 30-day Month and 223 minutes in a 31-day Month.
- 4.2
We measure Availability with our own monitoring, which checks the Licence server's responses every minute. The Licensee may present its own measurements, and where they differ we take them into account when handling a request under section 8.
- 4.3
We announce planned maintenance by email at least 2 Business days ahead and keep it as short as possible.
- 4.4
Downtime does not include:
- planned maintenance announced under clause 4.3,
- interruptions caused by force majeure as defined in the licence terms,
- lack of connection caused by the Licensee's network or infrastructure.
When the Licence server is down
Licence server Downtime never stops an Installation. This is how the Software handles it:
- 5.1
The state of the Licence depends solely on the date up to which the Licence is paid, stored in the signed Licence record. The Installation checks that signature itself, with a public key from the release, without contacting us.
- 5.2
When a heartbeat fails, the Installation records the error and the number of failed attempts, and the Licence state stays as it is. It retries after one minute, and each following attempt after twice as long, never less often than the normal heartbeat rhythm, which is one day by default.
- 5.3
An Installation holding a valid Licence record keeps running even if the Licence server stopped answering for good. The stages after a missed payment in section 9 of the terms are counted from the paid date, not from the last successful heartbeat.
- 5.4
The only thing Downtime can delay is a renewal or scope change arriving by heartbeat. On request we then send the renewal as an Offline token, which the Licensee pastes into the panel.
- 5.5
An Installation activated with an Offline token never connects to the Licence server, so Downtime does not affect it.
- 5.6
When the Installation cannot read its own Licence state from its database, for example while the database restarts, nothing changes for 10 minutes. If the problem lasts longer, the Installation only stops accepting growth, and every other admin action and all customer services keep working.
- 5.7
When a Software release does not know the key that signed a newer Licence record, for example after we rotate signing keys, the last verified Licence state stands for 14 days. Updating the Installation within that time is enough.
Support and response times
- 6.1
Response time runs from receipt of a Support request to the first answer from a person on our team that contains a diagnosis, a workaround or specific questions needed for the diagnosis. An automatic acknowledgement is not a response.
- 6.2
Response time runs in Business hours. For a Support request sent outside them, it starts at the beginning of the next Business hours.
- 6.3
The Licensee sets the priority in the subject of the Support request. We may change it if the description does not match the definitions in the table below, and we explain why in our answer.
- 6.4
After responding we say how we will solve the problem: with a workaround, a fix in the next release or a configuration change, and give an expected date. Time to fix is not guaranteed, and we keep working on critical requests until resolved, during Business hours.
- 6.5
We answer in Polish or English, in the language of the Support request.
| Priority | When | Response time |
|---|---|---|
| Critical | The admin panel or the panel of Customers of the Licensee does not work: it does not start or nobody can log in. | Within 8 Business hours |
| High | An important feature does not work and there is no workaround, for example creating services, renewals, payments, invoices or Licence activation. | Within 1 Business day |
| Normal | Other bugs and questions about installation, configuration, updates and the Licence. | Within 2 Business days |
How to report
- 7.1
Send Support requests by email to hello@flaem.net, with the priority in the subject, for example "[Critical] Panel does not start after the update".
- 7.2
A Support request should include:
- the company name and the first group of characters of the Licence key, or a note that the Installation runs on an Offline token,
- the Software version, shown in the panel,
- a description of the problem: what happened, since when, after which steps and what was expected,
- where possible, a log excerpt or a screenshot, without data of Customers of the Licensee unless it is needed.
- 7.3
We diagnose from the information in the Support request. We do not require access to the Installation. If the Licensee chooses to give it, the Data Processing Agreement applies.
Credits for missed Availability
- 8.1
For every full 0.5 percentage point by which Availability in a Month was below 99.5%, we extend the Licence by 10% of the length of that Month. The total extension for one Month is at most 50%.
- 8.2
The Licensee sends a credit request by email within 30 days of the end of the Month concerned. We answer within 14 days with the measured Availability.
- 8.3
A granted extension moves the date up to which the Licence is paid. The new Licence record reaches the Installation by heartbeat, and for an Offline token we email a new token.
- 8.4
The credit in this section is the remedy for missed Availability. It does not limit liability for damage caused intentionally or other rights under section 11 of the terms.
| Availability in the Month | Full 0.5 points below 99.5% | Licence extension |
|---|---|---|
| 99.5% or more | Target met | No extension |
| Below 99.5%, above 99.0% | 0 | No extension |
| 99.0% or less, above 98.5% | 1 | 10% of the Month, 3 days in a 30-day Month |
| 98.5% or less, above 98.0% | 2 | 20% of the Month |
| 98.0% or less, above 97.5% | 3 | 30% of the Month |
| 97.5% or less, above 97.0% | 4 | 40% of the Month |
| 97.0% or less | 5 | 50% of the Month, the upper limit |
Changes to the SLA
- 9.1
We announce changes to the SLA by email and on flaem.net at least 30 days before they take effect, under the rules for changes to the licence terms.
- 9.2
A change that lowers the guaranteed service level does not apply during a Billing period the Licensee has already paid.
- 9.3
This SLA is in force from 24 October 2026.
Questions about this document, or need a copy to sign? Write to hello@flaem.net.