>< Lynx Devs' own platform

Monitoring for your online store: alert, interpretation, action and written proof

2
vantage points that confirm each other
min
the alert reaches our team, not your inbox
1
written monthly report, reviewed by a person
0
customer data leaves your server

How a store finds out something is wrong today

Almost always late, and almost always from someone who should never be the first to know.

"On football Sundays my store won't load"

During matches, some Spanish ISPs block Cloudflare IP ranges and your store stops loading even though it has nothing to do with it. Your host will tell you everything is fine.

The padlock nobody saw expire

The homepage loaded, so it was "fine". The real server's certificate had been expired for a day behind Cloudflare. Ordinary uptime checkers can't see it.

End-of-life versions and nobody told you plainly

PHP or PrestaShop without security updates for months. And sometimes "updating" isn't a task: it's migrating the platform. You need to know that beforehand.

"I pay for maintenance and don't know what you do"

Background work is invisible. Without a report, maintenance looks like a cost, not a protection.

How we do it

Four design decisions you can demand from any monitoring provider.

The alert reaches us

We don't email you at 3 a.m. so you can decide what to do. The Lynx Devs team receives it, interprets it and acts. You hear about what has already been solved.

What isn't stored can't leak

The agent never extracts log text or your customers' data: counts, versions and the e-mails of admin accounts (to alert you if a new one appears). What it sends is deleted within two months at most; the summarised history is kept for 13 months. A problem in one store gives no access to any other.

Nothing updates itself in your store

The monitor alerts; a person decides. No automatic update is going to break your checkout on a Friday afternoon.

The watchman is watched too

If the system itself stops reporting, an alarm goes off. A watchman who falls asleep unnoticed is worse than none.

Ask any monitoring provider this:

  • Who receives the alert and who fixes it? Or do you just forward it to me?
  • Do you see the real server's certificate behind Cloudflare, or only that "the homepage loads"?
  • Do you tell me whether my PHP or PrestaShop is still supported, and whether bringing it up to date is a task or a project?

What Lynx Monitor watches

Everything listed here is running today in the stores we maintain. What is still in development is not advertised.

Availability from two vantage points

Two independent observers; an outage is only reported when both confirm it. Far fewer false alarms and no single point of view.

Team alerts within minutes

Outage, recovery, upcoming expiry or a new admin account in your store: the Lynx Devs team gets it right away on its on-call channel.

Inventory of your platform

PrestaShop version, PHP version and installed modules. You finally know what you have and whether it is current.

End-of-life warnings

Unsupported PHP or platform, telling "it updates" apart from "it needs a migration". Before it becomes a hole, with an honest estimate of the cost.

Traces of an attack and new accounts

We look on your server for the traces an attack or an oversight usually leaves: executable code where there should only be images, forgotten database dumps, backup files, installers never deleted. And we alert you right away if a new admin account appears.

Domain and certificates, also behind Cloudflare

Domain and certificate expiry, including the origin server certificate that Cloudflare hides and ordinary monitors never see.

Forgotten maintenance mode and error trends

The store was left on "back soon" after an update, or server errors start climbing: we see it before it turns into an outage.

A written monthly report

Availability, resolved incidents, work done on your store and background work. What the agent sends from your store is signed and traceable; a person reviews the report before it is sent.

What it looks like from the inside

Real screenshots of our panel, with the stores renamed. You don't need to look at it: we do.

Lynx Monitor panel: list of stores with status, PrestaShop and PHP version and agent version
The portfolio at a glance. Status, PrestaShop and PHP version, and whether the agent is still alive. One traffic light per store.
Open warnings in Lynx Monitor: forgotten maintenance mode and unsupported PHP
Warnings with severity. This is where "unsupported PHP and the store doesn't accept a newer version" shows up: the difference between updating and migrating.
End-of-life and expiries: origin and edge certificates, domains and days left
Expiries, including the origin certificate. The one Cloudflare hides and ordinary checkers never see. Days left (rounded in the screenshot) for every domain and certificate.
A store's page in Lynx Monitor: traffic light, versions, signed agent and last scan
Each store's page. Code and database versions, PHP, signed agent and when the last full scan ran.
Availability: list of monitors per store (homepage, category, product page, DNS) with percentage and status
Availability, point by point. Homepage, category, product page and DNS of every store, each with its percentage. Every outage and recovery is recorded: that is what goes into the monthly report.

Store names and domains replaced with fictional ones; versions, dates and technical details deliberately rounded or hidden. The panel is internal and not handed to clients; what you receive is the monthly report.

How it works

From setup to the first report, without installing anything or looking at any dashboard.

01

Initial audit

We review versions, end-of-life status, certificates, domain and Cloudflare configuration. The audit report is a deliverable in its own right.

  • Versions
  • Certificates
  • Domain
  • Cloudflare
02

Installation and setup

We install the agent on your server with the access you already have, and configure the two vantage points and the alerts. No plugins in your store.

  • SSH or secure FTP
  • PrestaShop
  • No plugins
03

Monitoring and action

The system watches; we receive the alerts, interpret them and act according to your plan. Nothing changes in your store without a person behind it.

  • Team alerts
  • Human decision
  • Action
04

Monthly report

Early each month you receive the previous month's report by email: what happened, what we did and what is left to decide. We review it before sending; nothing goes out automatically.

  • Early each month
  • By email
  • Reviewed

Plans

Monitoring makes sense when someone acts on what it detects. That's why it comes with maintenance, and the setup fee is waived when you sign up.

Lynx Monitor setup

Initial audit + installation + alerts

€290one-off

  • Audit of versions, end-of-life status, certificates, domain and Cloudflare
  • Installation of the agent and the two vantage points
  • Alert configuration
  • Deliverable audit report

Fully waived when you sign up for maintenance.

Request setup

Lynx Monitor

Monitoring and report, no intervention

monthly fee, on request

  • Everything Lynx Monitor watches
  • Alerts handled by our team
  • Written monthly report
  • Interventions billed hourly

Requires setup. If we detect a problem, fixing it is quoted separately.

Ask us
Recommended

PrestaShop Maintenance with Lynx Monitor

Monitoring + action + support

from €150/month

  • Lynx Monitor included
  • Setup fee fully waived
  • Controlled updates of PrestaShop, modules and theme
  • Technical support hours and premium module pack
  • Incident recovery

This is the plan we recommend: detecting without acting protects nothing.

Request a quote

Prices exclude taxes. The setup fee covers the real hours of audit and installation: every server is different.

What it has already found in real stores

No names: a store's weak spots belong to its owner. No invented figures: the service is weeks old, not years.

  • The invisible padlock

    On its first measurement of origin certificates, Lynx Monitor found a store's origin server certificate expired since the day before. Ordinary uptime checkers couldn't see it: they look at the Cloudflare layer, which kept showing its own padlock. It was renewed the same day. "The homepage loads" is not "it's fine".

  • A whole portfolio on unsupported PHP

    The first assessment found every monitored store on a PHP version unsupported since the end of 2025, and on a PrestaShop version that doesn't accept a newer one. It's not enough to say something is old: you have to say whether the way out is a task or a project, and what each path costs.

  • We take our own medicine

    A review found outdated components in the monitoring system itself. We updated the same day what had a patch and scheduled the migration of the component that doesn't. A watchman that doesn't check itself can't be trusted.

  • Match days

    Several stores behind Cloudflare stopped loading in Spain during LaLiga blocks: collateral damage from blocks aimed at others. With each client's written authorisation, the system pauses Cloudflare for the duration of the block and re-enables it afterwards. During that pause the store loses Cloudflare's protection: a decision with a cost that the client makes, informed.

Frequently asked questions

Do I get access to a dashboard?
Which platforms are covered?
Do you guarantee an uptime percentage?
Will my store be 100% secure?
What data leaves my server?
How fast do you act?
What about LaLiga blocks on match days?

You sell. We watch, decide and act.

Tell us which store you have and where it is hosted. We'll tell you what Lynx Monitor covers in your case and what the initial audit found.

Contact us, don't be afraid.
Chat on WhatsApp