Monitoring and security for everything you host.

Servers, hosting accounts and websites in one dashboard. Related signals become one incident, and the fix waits for your approval.

Start free · See how it works · Try the demo

What Valinor does

  • Monitoring: Resources, services, availability and certificates, for every host.
  • Security: Logins, changed files, malware and the addresses that attack.
  • Incidents: Related signals reach you as a single alert, with their timeline.
  • Fixes you approve: Valinor proposes, you approve. By default, the agent only reads.

How you add your first host

First the path as recorded in the dashboard, on a VPS: from the empty dashboard to the first findings, in under a minute. Below it, the steps for each of the four host types.

VPS with agent

  1. Name it and pick the type: In the dashboard, under “Add a host”. Pick “VPS with agent” and how often the agent reports.
  2. Copy the command: The command carries the host’s key. The secret is shown once, so that is when you copy it.
  3. Run it on the server, as root: The installer downloads the agent, checks its fingerprint, starts a timer and sends the first report.
  4. The host shows up: The first report is accepted during the install. The outside checks are scheduled too.

Shared hosting

  1. Pick “Shared hosting”: A name and the account’s domain. The agent finds the webroot by itself.
  2. Copy the same command: It is the same as on a VPS, with this account’s key. The secret is shown once.
  3. Run it from the account terminal: From cPanel → Terminal or over SSH, as the account’s user. No root: the agent adds itself to the crontab.
  4. The account shows up: Fingerprints of the webroot files, malware patterns and the outside checks on the domain.

External site

  1. Type the domain: Optionally, a text the page must contain. Nothing gets installed.
  2. The HTTP probe answers first: Within the first minute you see whether the site answers, and with which code.
  3. The other checks get scheduled: TLS, DNS, blocklists, headers, email, domain expiry: each at its own pace.

cPanel/WHM reseller

  1. Give the WHM address and an API token: You generate the token in WHM, under Manage API Tokens. Nothing gets installed on the server.
  2. Save and test: The dashboard asks WHM which accounts exist and tells you at once whether the token works.
  3. One host per account: The list is read again every 30 minutes, so new accounts show up by themselves.

The whole path, from account to reports

What happens when something goes wrong

No need to keep an eye on the dashboard. Here is how it plays out in one example: a backdoor planted on a client’s site at night.

It notices

The agent, a script installed with one command, reports every 5 minutes by default. Sites where you cannot install anything are checked from outside.

It tells you once

Repeats of the same problem stay one incident. One message by email or push, plus Slack or Discord on paid plans.

It explains why

One click and the AI incident analysis reads the evidence and explains the likely cause in plain words.

You decide

When a fix can run from the dashboard, it waits for your approval. Nothing reaches the server before that.

Example incident on bakery.example, a client’s site on shared hosting. At 02:05 the agent report finds a file with an injection pattern. Seconds later one alert goes out by email and push. On your click, the AI incident analysis explains it is likely a backdoor. You pick the file, and its quarantine waits for your approval: nothing has run on the server yet.

An illustrative example: a client’s site on shared hosting, with remediation switched on. How soon you approve is up to you.

Afterwards: the incident stays in the host’s problem log; every outage keeps its cause in the uptime history.

What Valinor sees on each host type

Not every host can be seen equally deep. With an agent we see inside; without one, only what a visitor sees.

VPS with agent

The agent runs as root and reports resources, services, logins and the files of your sites. From outside we check the host address and every hosted site.

  • SSH logins, accepted and failed (every 5 min)
  • SSH keys, accounts and sudo (every 5 min)
  • Suspicious processes, by behavior (every 5 min)
  • Backdoor patterns and fingerprints in the webroot (every 5 min)
  • Disk and inodes, on every filesystem (every 5 min)

Shared hosting

The agent runs inside the hosting account, without root: the site files, the cron and the account logs. The site is checked from outside in parallel.

  • sha256 fingerprints of the webroot files (every 5 min)
  • Injection patterns inside the files (every 5 min)
  • The account access logs (every 5 min)
  • One-click cleanup, with your approval (on request)
  • HTTP availability (every 1 min)

External site

Nothing gets installed. You add the domain and the site is checked from outside the network, like any visitor would.

  • HTTP code and response time (every 1 min)
  • DNS records, alerting on change (every 15 min)
  • TLS certificate, days left (every hour)
  • Exposed sensitive files: .git, .env, backups (every 12 h)
  • Ports exposed to the internet (every 12 h)

cPanel/WHM reseller

You save a WHM token and every account we find becomes a host, including the ones that appeared without you knowing.

  • API tokens and the 2FA policy (every 6 h)
  • Web traffic of the accounts without an agent (every 5 min)
  • Accounts added, removed or suspended (every 30 min)
  • Shell, plan, IP and mail hold (every 30 min)
  • Domain answering from elsewhere, or re-registered (every hour)

What sits under security

Besides incidents, the dashboard has a few pages that gather the same data from another angle: who attacks, which files look suspicious, which addresses are blocked.

Attackers

Attack events, grouped by source address and its country. You tick the addresses and propose the block, which runs only after you approve.

Malware

Suspicious files from every site, in one list. Quarantine needs approval; the file stays as evidence and goes back with one click.

Firewall lists

Your own lists of blocked and allowed addresses, applied by the agent on VPS hosts with fixes turned on. An allowed address cannot be blocked by mistake.

PHP2Shell check

Find out whether a site runs a PHP version affected by the PHP2Shell advisory, and what to do until you update. Available on every plan.

Check a site

Checks from outside

The TLS certificate, DNS, blocklists, exposed files and ports, email posture and domain expiry, with nothing installed.

What gets checked on an external site

Nothing runs without you

The agent reads. Remediation ships disabled, and you approve every command.

  1. The switch on the server: It is turned on only at install, with --enable-actions. An agent update cannot turn it on.
  2. The switch in the dashboard: On the host’s page. Without both, the agent refuses any command, however correctly it is signed.
  3. The remediation waits for you: The animation stops here: the next step is yours. Approve or reject, right in the window.
  4. The agent picks it up: The signed command leaves with the agent’s next report. The configuration is tested before the restart.
  5. The result goes into the incident: The HTTP probe confirms the site answers, and the steps stay in the incident’s history.

Read-only by default

A shell script that uses standard tools: curl, openssl, sha256sum. It reports; it executes nothing until you switch remediation on.

Two switches for remediation

One when you install the agent on the server, one in the dashboard. Without both, even a correctly signed command is refused.

One key per host

Revocable and rotatable. A wrongly signed command opens a critical incident by itself.

Only four kinds of command

On a VPS: block an IP with an expiry, stop a process, quarantine a file, restart the web server after testing its configuration. On shared hosting, only quarantine. Nothing else.

Read what the agent does and does not do

From one site to your clients’ fleet

Starter and Plus start with 14 days for free, no card needed. Then you pick a plan by how many hosts you watch.

  • Free · 0 EUR/month: One site or server, watched from outside.
  • Starter · 4.9 EUR/month: One server, with the agent and remediation.
  • Plus · 19 EUR/month: A few servers, one screen.
  • Pro · 49 EUR/month: For agencies and hosting companies.
  • Ultra · 129 EUR/month: Large fleets, the tightest cadence.

See all plans

Ask your infrastructure

Ask in plain language about your servers and incidents.

Exposed does not mean exploitable

An assessment started on demand, with a report and remediation steps.

from 99 EUR

What people ask before installing the agent

Do you need root on my servers?

It depends on what you want to see. On a VPS the full agent runs as root, because it reads the authentication log, the firewall and every user’s processes. On a hosting account root is not needed: run without it, the installer switches by itself to shared hosting mode, which sees the site files, the account cron and the access logs. In both modes the agent is read-only by default; remediation is switched on separately and runs only with your approval.

What happens if the agent stops?

After three missed reports, the host shows a silent agent and a critical incident opens, with an alert. A silent server is itself a signal, not an absence.

Where does the data from my server go?

The agent sends numbers, names, fingerprints and summaries, not whole files, .env, databases or private keys. On a critical incident it attaches short evidence: the process command line, the last 60 lines of the authentication log when an account or key changes, the first 256 bytes of a new executable, and for a suspicious web file the matched fragment and its line. The data is stored in our database, isolated to your account. The language model only gets data on request: the evidence of the chosen incident for an analysis, or the account data the AI assistant reads when you ask it something.

Does it work on shared hosting, without root?

Yes. The agent has a mode for hosting accounts: it runs from the account crontab, without root, and watches the webroot file fingerprints, malware patterns, the cron and the account access logs. The site gets ten outside checks in parallel.

Can I try it before paying?

Yes. Starter and Plus start with 14 days for free, with no card: the agent on your servers, cPanel accounts, remediation on your approval. At the end you pick a plan; if you do not, the account moves to Free, which is permanent: one host checked from outside, with email and push alerts. Nothing is deleted.

Want to see it on your own infrastructure?

Start free with an external site, or try Starter or Plus for 14 days with the agent on your servers. No card.

Start free