Managed hosting and support from the team that built the system.

The terms after launch are the ones you sign.

Every row below comes from the agreement itself. The warranty, hosting and exit terms also appear on our commitments, so none of them turns up later as an add-on.

The warranty follows who controls the machine.

The warranty covers defects in what we built, for a period set by where the system runs. Hosting, monitoring, updates, backups and new features come under a paid plan, outside the warranty.

The extension is earned month by month after handover. Two unbroken years of the Premium Subscription earn the full 24 months, and if the subscription lapses the extension stops, with cover already earned kept.

The Premium Subscription maintains what we delivered.

This paid plan covers the system once the project is complete, and it sits on top of hosting, which is billed separately. Sign it whenever you like, before launch or long after. The agreement you sign lists what it includes:

• Server and infrastructure maintenance: operating-system patching, SSL/TLS renewal, dependency and framework upgrades.
• Monitoring of uptime, performance and errors, with alerting.
• Security: vulnerability monitoring, patching and incident response.
• Backups and recovery: scheduled automated backups with periodically tested restores, and a documented recovery procedure.
• Bug fixes beyond the warranty, and periodic health reporting.
• If you select it, a small monthly allowance of minor changes with a priority queue. Larger work is quoted as a change.

Backups sit outside the delivered build. After delivery they run only under a paid plan, meaning the Premium Subscription or a hosting plan in your proposal that names them. Prices are in the proposal, and pricing and engagement shows how each number is reached.

Response targets by severity, in business hours.

Under the Premium Subscription, the signed terms set a target for each severity, counted in business hours: Monday to Friday, 9 am to 6 pm UTC+4, outside UAE public holidays. Whoever picks up the issue works at the studio that built the system.

The agreement calls these response targets and sets no fix times. It gives no uptime percentage either, because a third-party provider supplies the hosting under its own terms. We answer for how we configure and manage the service, and we help you resolve the provider's incidents.

Hosted in Germany unless you choose otherwise.

Our hosting sits in Germany and is run to the GDPR, and on your own servers the warranty is 90 days. We arrange the hosting with a third-party provider as your agent and re-bill it at the fee in your proposal, since we run no data centre of our own. The contract names the location and carries the data-processing terms. Under Article 28 of the GDPR, a processor acts only on documented instructions under a written contract.

If a data protection law limits where your customers' personal data may sit, raise it on the first call. You and your counsel decide the location, and the contract names it, whether that is our hosting or your own servers. Security and data covers how each client system is isolated. A system another team built is assessed before we host it, as described under software rescue and modernization.

A backup counts once it has been restored.

Google's SRE book says 'no one really wants to make backups' and that 'what people really want are restores'. So we prove ours by restoring them. We extract the archive, check its file and byte counts against the archive's own manifest, then open each recovered file and look for its format's completion marker.

Monitoring treats silence as a failure.

A check earns its place by going red when the thing it watches breaks, and a check that stops reporting is treated as red too.

Changes after launch pass the same release gate as the build, so each one can be reversed. Where a system uses language models, upgrades, cost budgets and drift are watched as well, under model operations (LLMOps).