Services · monthly support for websites, apps, automation and software

Maintenance and support. For everything we have built

Software does not end at launch. It needs updates, someone who sees when it goes down, and hours for whatever comes up along the way. Monthly support covers websites, mobile apps, automation and custom software: what we built and what we took over from others.

The problem. With nobody responsible, everything breaks

A plugin left un-updated, an expired certificate, a new version of iOS, an API that changed its format. Nothing dramatic on its own; together, a website that no longer loads and an app the store takes down. Maintenance turns “it is down” into “it was fixed before anyone noticed”.

What's included. Every month

01

Monitoring

Availability, errors, performance, with the alerts coming to us, not to your customers.

02

Updates

System, dependencies, plugins, iOS and Android versions, store requirements.

03

Security and backups

Patches, verified backups, a restore plan that has been tested.

04

Response time

For incidents, with contractual response times and priorities.

05

Development hours

Small features, adjustments, integrations, from the monthly package.

06

One person to talk to

Someone who knows the system and its history.

Support tiers. Chosen by system

Tier 1

Basic

For company websites and stable apps: monitoring, updates, backups and hours for small interventions. The hours and the response time are set in the contract.

Tier 2

Standard

For shops, customer apps and automation in production: everything above, plus a monthly package of development hours and a shorter response time for incidents, set in the contract.

Tier 3

Extended

For systems the daily business depends on: more hours, intervention outside working hours for critical incidents, a periodic architecture review. The terms are in the contract.

Priorities and response times are written into the contract, before the first month. The quote follows the assessment, because it depends on what has to be maintained.

How we take over. Software built by someone else

01

Assessment

Code, infrastructure, accounts, dependencies, risks. A written report.

02

Access and documentation

We take over the accounts, document what is not documented, set up the working environment.

03

Stabilisation

Critical errors and mandatory updates, first.

04

Monthly support

From the following month, on the right tier.

Infrastructure. Hetzner Cloud, in the EU

Our own systems run on Hetzner Cloud, in data centres in the European Union, and our product asoft-desk is one of them. Our servers are in Germany, created with Terraform and configured with Ansible. Today we also run a client’s application on Hetzner Cloud. If your application runs with another provider, moving it to Hetzner Cloud is a separate project, with its own quote.

Who it's for

Clients we have already built something for. Companies with a website, an app or a system left without a supplier. Companies in Romania, Europe, the Middle East and North America looking for a stable partner for existing software; we work remotely, in Romanian and English.

Proof

We maintain Jedan Couture’s site and online catalogue, month after month since 2024, and Divalook Academy’s website in Montréal since 2023, plus the Alcedo catalogue app, in production since 2016. We know what an update that breaks a page looks like, and how it is prevented.

Questions. Short answers

Yes. We start with the assessment; if the system is worth maintaining, we take it into support from the following month.

One channel, agreed from the start: e-mail or WhatsApp. The incident is recorded, someone is responsible for it, and you get an answer within the time set in the contract.

Yes, from one month to the next, as the system evolves.

Yes, as a separate project with its own quote. We start with a paid audit that ends in a written report: what your application uses at its current provider, what has an equivalent on Hetzner Cloud and what does not. Before it, you get a free 30-minute consultation. If something it depends on has no equivalent, we tell you before any work starts.

Tell us what you have and who built it. We come back with a plan

no obligation · the assessment is the first step, the tier comes after