Business Continuity
How LeraLink keeps running, and how you keep your data, if SSStudio or a supplier is unavailable.
AuthorLeraLink Team
Last updated: 13 November 2026
Operation and continuity partner
LeraLink is developed, owned and operated by SSStudio. SSStudio has a written, signed strategic partnership agreement with DotNet Talk AB, organisation number 559480-2570, Nordostpassagen 15, 413 11 Göteborg, Sweden. The partnership exists for continuity: while SSStudio operates the service, DotNet Talk AB performs no operational work; if SSStudio cannot continue, DotNet Talk AB takes over the operation of the service. This partnership is the continuity guarantee for customers.
To make a takeover possible, DotNet Talk AB holds standing access to the code base (the source repository) and to the Cloudflare account that hosts the service, and therefore technical access to the databases and stored data. It has no access to the Superadmin console. It does not use this access in normal operation. It is bound by a written agreement that includes confidentiality and data-protection obligations, and it is listed as a subprocessor in Subprocessors and Recipients. Day-to-day operation runs on Cloudflare's infrastructure, and backups, cleanup and monitoring are automatic.
Safeguards
| Safeguard | What it means for you |
|---|---|
| Everything as code | The application, the database structure, the configuration and the deployment procedure are in a version-controlled repository. Someone with access can rebuild and deploy the platform without relying on anyone's memory. |
| Documented procedures | Restore, incident response, maintenance, releases and the EU move are written down as step-by-step procedures, and were followed in practice. |
| Managed infrastructure | The platform runs on Cloudflare. There are no servers of our own to maintain. |
| Independent status page | status.lera.link runs on GitHub, independently of LeraLink, and keeps reporting if LeraLink does not. |
| Nightly backups and tested restore | The database is backed up every night and kept 30 days in the EU. Restore is a tested tool. See Backup and Recovery. |
| Data portability at any time | Each installation can export its content, and each person can download their own data, without asking us. See the Data Export and Exit Policy and Your Data Rights. |
| Continuity partner | Under a written strategic partnership agreement, DotNet Talk AB holds standing access to the source repository and to the Cloudflare account, without access to the Superadmin console, so that it can take over the operation of the service if SSStudio cannot continue. See above. |
| Source-code escrow | An organisational customer may ask for a source-code escrow arrangement. It requires a separate agreement between SSStudio, the customer and an independent escrow agent, which sets what is deposited, when it is updated, the conditions for release (such as the bankruptcy of SSStudio or the end of the service without a successor) and the costs, which the customer bears unless agreed otherwise. |
| Successor entity | If SSStudio becomes a private limited company (BV) or another successor takes over, the Customer Agreement lets the contracts be transferred to it with at least 30 days' written notice; a customer with a reasonable objection may end its agreement without a fee. |
Supplier failure
| Supplier | If it fails | What happens | What we can do |
|---|---|---|---|
| Cloudflare (hosting, storage, DNS, default AI) | Partial outage | Parts of the service may be slow or unavailable. | Follow Cloudflare's status, inform customers through the status page. |
| Cloudflare | Prolonged or total outage | The whole service is unavailable. There is no automatic failover to another provider. | The nightly backups are in an open format that can be restored outside Cloudflare, but rebuilding the service elsewhere would take substantial time. |
| Cloudflare | Loss of the account | The service and the data in it are unavailable. | The backups are held in the same Cloudflare account, so there is no independent copy to restore from today. Customers' own exports are the remaining copy; see the limits below. |
| AI providers (Cloudflare Workers AI, OpenAI, Google) | One provider unavailable | Each AI task tries its models in a fixed order set by the platform. If the first fails, the next allowed model in the installation's AI policy is used. | Nothing; this is automatic. A model the installation's policy does not allow is never used as a fallback. |
| AI providers | All providers for a task unavailable | That AI task is unavailable. Writing, reading and publishing continue unaffected. No AI step is needed to publish. | AI can be switched off for a task or an installation at any time. |
| Resend (email delivery) | Unavailable | New sign-ins by email code cannot complete, because the code cannot be delivered. People already signed in continue. Administrators with a passkey can still sign in where passkeys are enabled. Newsletters and notifications are delayed. | Newsletters and notifications that fail because the provider is unavailable are retried; a sign-in code is requested again by the person. Moving email delivery to another provider would need a change to the platform's code. |
| GitHub (code hosting, status page, internal monitor, deployment) | Unavailable | The running service is not affected. New releases, the status page and the internal monitor are paused. | Wait until GitHub is available again. |
What customers should plan for
- Keep your own export. Export your installation's content regularly, and keep it outside LeraLink. This is your strongest protection against any failure on our side, including our exit.
- Know your own obligations. If your organisation needs a guaranteed recovery time beyond the Service Level Agreement, plan for it: for example, by keeping a published archive of your content elsewhere.
- Keep contacts current. Make sure we have a working contact address for your organisation, so that notices about incidents and changes reach you.
- Plan around support hours. Questions and support requests are handled during office hours; there is no 24/7 support desk. Incident monitoring and incident response run around the clock; see the Service Level Agreement.
- Ask for escrow if your organisation depends on LeraLink for a critical function and needs that assurance.
- During the pilot, treat LeraLink as a service still being proven. The Pilot Programme describes what that means.
Limits
- Continuity depends on SSStudio and, if SSStudio cannot continue, on DotNet Talk AB taking over as agreed. The safeguards above reduce that dependency; they do not remove it.
- The platform depends on one infrastructure provider. A prolonged Cloudflare failure would make LeraLink unavailable, and moving to another provider would take substantial work.
- Backups are stored with the same provider, and in the same account, as the live data.