Analysis
Technology and stack review
Do you really need a rebuild? We review an application's structure and explain what to keep or change.
Ongoing support / Backend development & data architecture
VAT-exempt under section 19 of the German VAT Act
Support application operations
We regularly review and document an application's technical condition within a limited support period.
US$799.00
Total price · one-offVAT-exempt under section 19 of the German VAT Act
- Four weeks of support for an existing application on one agreed hosting setup
- Four scheduled checks of existing availability, error and backup signals
- Six hours total for review, small agreed measures and documentation
Your enquiry is non-binding. An order is created only when you accept our quotation .
Image 1 of 4
Service scope
Your result
- Four documented checks and a traceable operational state
- Overview of addressed anomalies and further measures needed
Included
- Four weeks of support for an existing application on one agreed hosting setup
- Four scheduled checks of existing availability, error and backup signals
- Six hours total for review, small agreed measures and documentation
- Check an existing recovery procedure in a suitable test environment where the allowance permits
Excluded
- 24/7 monitoring, on-call service and guaranteed response times
- Complete new infrastructure or backup-strategy setup
- Provider fees, major upgrades and production emergency recovery
Which projects does this service suit?
Suitable if …
- An existing setup needs planned support for a limited period
- Existing operational signals and backups need regular review
Not suitable if …
- A business-critical service needs binding round-the-clock availability
- Monitoring, backups and basic operation first need complete setup
What this covers
Who checks that our application and backups still work as intended?
An application needs attention after development. Errors, failed backups or growing storage use may indicate work needed. This package includes four scheduled checks over four weeks and six hours total for review, small agreed measures and documentation.
We use an existing hosting setup and operational signals. Complete new setup is excluded. Constant monitoring and immediate response are not promised. Findings are documented and communicated through the agreed process; larger measures are planned separately.
A green signal does not prove successful recovery
A backup may report creation yet remain insufficient for the actual recovery case. We therefore examine an existing recovery procedure and, where the allowance permits, test it in a suitable environment. Restoring production is a different intervention.
Operational signals must fit the system. Homepage availability alone does not show whether a background job works. We define which existing signals to check and which areas they do not cover. The report states these limits.
Does this sound familiar?
Operational signals are rarely reviewed
Existing messages help only when reviewed and interpreted. The package defines a limited schedule with documented checks.
Backups exist but are barely tested
A backup file alone is not proof of recovery. We examine the existing procedure and suitable isolated testing within the allowance.
Small operational tasks need an owner
A limited support period can cover planned work. Larger interventions and emergencies remain separate tasks with expressly agreed procedures.
How we approach it.
Compare setup and review foundations
We examine the documented environment and existing signals. Check scope, contact method and support limits are defined beforehand.
Perform scheduled checks
Four checks examine agreed availability, error and backup signals. Small agreed measures are handled within the total allowance.
Hand over operational state and action needs
Documentation summarises observations and measures. Untested areas, larger risks and required follow-up work are not presented as completed.
After handover
Scheduled checks are not continuous monitoring. Incidents can occur between appointments; the package includes neither an availability guarantee nor on-call service.
New product functions and fundamental infrastructure changes are commissioned separately from planned operational checks.
Describe the intended function and an example of a successful process. Name existing systems and the roles involved without sharing real customer data or credentials.
After your enquiry, we clarify which data the function processes, which rules it must follow and which systems it must contact. Required documents and test access are agreed separately.
Terms used in this service
What does that mean?
- Operational signal
- An existing measurement or message about system state, such as availability, errors or a backup run.
- Recovery procedure
- The documented steps to recover a usable version from existing backups. Testing needs a suitable environment and clear ownership.
- On-call service
- Expressly agreed availability for unplanned incidents. It differs from occasional scheduled checks and is excluded from this package.
Before your enquiry
Questions about the offer.
What is included, what do you need and what happens after your enquiry?
The process in detail →Is someone available around the clock?
No. The package includes four planned checks and six hours total over four weeks. No 24/7 availability or guaranteed response time is included.
Are backups set up from scratch?
A complete backup strategy is excluded. Existing backups and their documented recovery procedure form the review's basis.
What happens during a major incident?
The issue is reported through the agreed contact method. Major repair or production recovery needs a separate commission and appropriate approvals.
Are hosting costs included?
No. Provider fees and infrastructure costs remain separate. The package describes work on an existing agreed setup.
Does support renew automatically?
No. Documented handover follows after four weeks. Further support needs a new agreement and is not triggered by an enquiry alone.
When does work begin?
We confirm the start and delivery deadline in writing after reviewing your documents. The agreed scope and complete source data determine the schedule.
Which access is needed?
A documented hosting setup with suitable access and existing operational signals A responsible contact, existing backups and suitable testing options Credentials must not be included in the enquiry. Details are agreed only after written commissioning.
What happens after handover?
One written follow-up round is included. The service scope lists the analyses, designs or technical changes covered by the package. We agree additional work with you before it begins.
Read more on this topic
Website maintenance: which tasks are included?
Updates, errors and backups need named owners. Distinguish maintenance, further development and operational support.
Read the guide ↗Related services
These may fit too.
Ongoing support
Develop an existing backend
We extend an existing backend within a limited work package, with prioritised tasks and documented changes.