helper.lt
Menu

Cloud infrastructure and DevOps

Infrastructure tends to get noticed only when something breaks. We set it up so that new versions are deployed automatically, backups are tested regularly, and you hear about errors as early as possible – often before your customers do. The whole configuration is described in code and documented, so the environment can be rebuilt or handed over.

Example

Example: a fictional company and made-up data.

Deployment, backups and monitoring of a fictional company's system
Ordering portalAll services running

Latest deployment

Change: invoice export to PDF

30 Sep 2026, 10:31–10:42, automated
  1. Code

    Change approved at 10:31

  2. Tests

    All 214 tests passed

  3. Staging

    Deployed and checked at 10:38

  4. Production

    Live at 10:42, no downtime

Response time

24–30 September, daily average

209 mstoday

Response time, 24–30 September, daily average
DayResponse time
24 September212 ms
25 September204 ms
26 September171 ms
27 September164 ms
28 September218 ms
29 September247 ms
30 September209 ms

Load

Server CPU, daily average

40%today

Load, Server CPU, daily average
DayLoad
24 September38%
25 September41%
26 September22%
27 September19%
28 September44%
29 September57%
30 September40%
Alert29 Sep 2026

Errors rose after an update

  1. 14:05New version went live
  2. 14:064.2% of requests failing
  3. 14:09Previous version restored
  4. 14:10Errors stopped

Fixed version deployed on 30 Sep 2026

Resolved

Backups

Every night at 02:00, kept for 30 days

Backups
BackupSizeStatus
30 Sep 2026, 02:0018.4 GBCreated
29 Sep 2026, 02:0018.3 GBCreated
28 Sep 2026, 02:0018.3 GBCreated
27 Sep 2026, 02:0018.2 GBCreated

Restore tested on 15 Sep 2026The copy was restored to staging and checked

What it covers

  • Cloud environment set up on AWS or another cloud provider
  • Automated build and deployment (CI/CD)
  • Backups and tested restores
  • Monitoring, logs and error alerts
  • Security updates and access management
  • Moving systems off old servers or shared hosting into the cloud

Who it suits

  • Your systems run on an old server that nobody dares to update.
  • The server was set up long ago by a former employee or supplier, and nobody knows exactly what is installed on it and how it all fits together.
  • New versions are deployed by hand, so every release takes time and carries risk.

How the work goes

  1. 1We find out what you need
  2. 2We analyse and propose
  3. 3We design the solution
  4. 4We build in parts
  5. 5We test and launch
  6. 6We maintain and improve

Examples of our work

Development and modernisation of a training organisation's platform

2024–2026

We took over a working platform, updated its technology and keep developing and maintaining it.

The platform we maintain has 30 pages, 19 API controllers and 25 data models.

Nuxt 4 / Vue 3, AdonisJS (Node.js), MySQL, Docker

Enquiries from every channel and email conversations – in the CRM

2026

Enquiries from website, Facebook, Instagram and Google Ads forms reach the CRM once, and each one shows the full email conversation.

Spam is flagged automatically, and a real enquiry is never lost.

Node.js / TypeScript, AWS API Gateway, SQS, Terraform

Field technicians' app that works offline

2023–2026

Tasks, customer sites, equipment, van stock and payments – on the technician's phone, even where there is no signal.

Developed continuously since late 2023, it syncs 33 data types to the phone.

Flutter / Dart, SQLite, Node.js / TypeScript, Server-Sent Events

Helper Sync – a sync platform for apps that work offline

2025–2026

Our platform for apps: all data is kept on the device, the app works offline, and changes reach other devices in real time.

It runs at sync.helper.lt, and our own apps use it.

Rust, PostgreSQL, Flutter / Dart, Server-Sent Events

Questions and answers

Does it have to be AWS?

No. We also work with other cloud providers and with your own servers. We choose the environment based on the system's needs, the budget and where the data has to be stored.

Will the system have to stop during the move?

Usually only briefly. We set up and test the new environment in advance and schedule the switch for when the system is used least.

Got a task or an idea?

Describe it in a few sentences – we'll reply and talk through how we could help.