Skip to content
Vimonto Deploy

AIBuilt into every plan

AI server management that explains, and leaves the decisions to you

When a deploy fails, an alarm goes off or a log fills up, AI reads it with you and says what happened and what to do next. It drafts scripts and configuration from a description and answers questions about your servers. It suggests; you decide.

What it is

An AI assistant for deployments and servers, inside the tool you already use

Vimonto Deploy sets up servers in your own cloud account, deploys your code without downtime and keeps an eye on it all. AI is a layer on top of that, not a separate product: it sits next to the deploy log, the server's monitoring, the site's logs and the editors you already work in.

It reads what Vimonto Deploy already knows (a failed deploy's log, an alarm, 30 days of metrics, a list of advisories) and tells you in plain language what it means and what to do. When you ask, it writes a first draft of a script, a configuration or an incident update. It never changes anything on its own: every fix, draft and action waits for you.

AI is in every plan, Free included, paid from monthly AI credits per organization. Secrets are redacted before anything is sent, and your .env is never sent.

  • Failed deploys and tasks explained, with a fix you can write into the deploy script
  • Logs explained and access logs analysed, with only figures sent
  • Alarms diagnosed with read-only checks on the server
  • Capacity advice from 30 days of measurements
  • Scripts, cron commands, Nginx config, redirects, security rules and incident updates drafted from a description
  • Questions about your servers answered in the search, with actions that only start when you confirm

Deploy errors

Why did my deploy fail? Explained in plain language

A failed build is thrown away and the live site keeps running, so a failure is never an outage. What it is, is a question: why? When a deploy fails, AI reads the end of the log, the deploy script and the site's facts (framework, PHP and Ubuntu version) and puts What went wrong on the deploy page: the cause in plain language and the likely fixes. It does this by itself, or when you click Explain this failure.

When the fix belongs in the deploy script, Write the fix puts the change into the editor for you to review. Nothing is saved until you save it. Failed tasks on the activity page, such as a provisioning step or a certificate request, have the same Explain this failure.

It works for every framework you deploy: Laravel, Symfony, Statamic, WordPress, plain PHP, Next.js and Nuxt. Composer that runs out of memory, a migration that cannot reach the database, a build step in the wrong order: the explanation names it and says what to change.

Example: a failed deploy explained
→ npm run build
sh: 1: vite: not found
✗ exit code 127

What went wrong
The deploy script builds the assets before the npm packages
are installed, so Vite cannot be found. Install them first.

  composer install --no-dev
+ npm ci
  npm run build

[Write the fix]   Nothing changes until you save it.

Logs

AI log analysis for Nginx, PHP and Laravel logs

A site's Logs page shows the Laravel log, Nginx's access and error logs and PHP-FPM's log. Two buttons read them for you.

  • Explain any log

    Explain with AI reads the lines on screen and lists up to six problems, each with how often it happened, the likely cause and a suggested fix. When nothing stands out, it says so.

  • Analyse your traffic

    Analyse traffic with AI turns the last 10,000 lines of the Nginx access log into figures: busiest pages, error spikes, the share of bots and scripts, each finding with a suggestion such as caching or a rate limit.

  • Only figures leave

    For traffic, only counts are sent: paths with numbers and ids taken out, status codes, visitor kinds. Visitor IP addresses are counted, never sent, and the log lines themselves stay in Vimonto Deploy.

  • Secrets taken out

    For an explanation, at most the last 8,000 characters are sent, with values from the site's .env and the server's secrets replaced by [redacted].

Monitoring

Find the root cause of server alerts

A monitor raises an alarm when CPU, load, memory or disk stays above its threshold. Knowing that the disk is at 92% is half the answer; the other half is why. Diagnose with AI looks at the server with read-only checks as root: load, memory, the busiest processes, the biggest directories under /var, /home and /tmp, the journal's size, deleted files still held open, processes killed for lack of memory and errors in the journal of the last hour.

The monitor then shows What is going on: the cause and suggested fixes. Nothing on the server is changed, and the output of the checks goes to the AI model with secrets redacted. Combined with uptime checks, heartbeats and email alerts, this is AI server monitoring that stays quiet until something is really wrong.

Diagnosing alarms in the docs

Capacity planning

Is my server the right size?

Too big costs money every month, too small costs you an outage. On a server's Monitoring page, Advise with AI adds up the last 30 days of measurements per day (CPU, load per core, memory, disk use and how fast it grows, network) and what runs on the server: sites per framework, processes, scheduled jobs and databases.

You get a verdict, Oversized, Right-sized or Close to full, with recommendations, what it saves or costs and the risk to watch. When your cloud provider lists its sizes, the current size and the sizes around it are compared with their prices; for a custom VPS the advice is in CPU and memory. Server names, domains and IP addresses are not sent, and resizing stays up to you, at your provider.

Capacity advice in the docs

Write it for me

Generate Nginx config, bash scripts and cron jobs from a description

Above the editors and forms where you would otherwise start from a blank page, Write it for me turns a description in your own words into a draft. Nothing is saved, run or posted until you do it yourself.

  • Bash scripts for recipes

    “Install Fail2ban and block an IP address after five failed SSH logins” becomes a recipe you can run on one server or many.

  • Deploy scripts

    A deploy script for your framework, or a change to the one you have. AI sees the site's facts and the current script, with secrets taken out.

  • Cron commands

    Describe the scheduled job and get the one command line for the server's Scheduler.

  • Nginx configuration

    Ask for a change to the site's Nginx config, such as longer upload limits or caching headers. Nginx still checks it with nginx -t when you save.

  • Redirects and security rules

    Redirect and security rule forms are filled in for you and checked against the form's own rules. Passwords for protected paths are never sent or written by AI.

  • Status page incident updates

    A clear incident, maintenance or update text for your public status page, from a few words about what is going on.

How a draft is made

  1. 1

    Describe it

    Click Write it for me and write what you need, in your own words and your own language.

  2. 2

    Get a draft

    Click Write draft. The draft lands in the editor or form, with “Draft written: check it before you save”.

  3. 3

    Check and save

    Read it, change what you need and save it yourself. Until then, nothing has changed.

Ask AI

Ask questions about your servers, in plain language

The search in the top bar (⌘K or Ctrl K) also answers questions. Type “Which sites still run PHP 8.1?” or “Why did the last deploy of shop.example.com fail?” and choose Ask AI. The answer comes from your servers, sites, deployments, tasks, databases, backups and recipes, with links to the pages it mentions.

It works much like asking an assistant, with two differences. It only sees what you can see: a member limited by teams gets answers about their own servers. And it can only read. When you ask for something to be done, it can propose a deploy or a backup run under Proposed actions; it starts only after you click Confirm, and your permissions are checked again at that moment.

Ask AI in the docs

Reviews and summaries

Dependency audits, deploy summaries and a weekly server review

  • Composer audit and npm audit, explained

    Every deploy can check your packages for known vulnerabilities. Review with AI says which advisories matter for this app, in what order to fix them, and the exact command for each, with Copy next to it.

  • What changed in this deploy

    Switch on deploy summaries and a successful deploy gets What changed: the commits since the previous deploy, summed up in one to five short points.

  • Weekly server review

    Every Monday, one email per person who manages servers: what needs attention on each server, from disk growth to expiring certificates, with a priority and a suggested next step.

Migration

Moving from another control panel, with an AI-reviewed dry run

Already run your servers on another server management platform? Vimonto Deploy imports them in place, without reinstalling. A dry run first works out what the move will do on each server, from the platform's data and a read-only look at the machine.

Review with AI then sums up what will happen, what to Check first and what to Check after the move. Only the plan is sent: no .env values, keys or passwords. After the move, Summarise the move with AI tells you what changed.

How the import works

Privacy

What is sent, and what never is

Each feature sends only what it needs to answer: the end of a log or a task's output, the error, the deploy script, commit messages, and facts such as the framework and versions. Each section of the documentation says exactly what.

  • Secrets are redacted before anything is sent: .env values, server passwords and keys, deploy keys, tokens and registry credentials become [redacted]
  • Your .env file is never sent
  • Visitor IP addresses are never sent
  • AI never changes anything on its own: drafts, fixes and actions wait for you
  • What runs by itself has its own switch under Settings → AI; only explaining failed deploys is on by default
  • Viewers can read explanations but cannot ask for new ones

AI credits

Included in every plan, paid from monthly credits

Every organization gets AI credits each month: 50 on Free and 300 on Premium. An answer costs a few credits, depending on how much it reads and writes; a short explanation costs a few, a long log a few more.

The monthly credits are renewed on the 1st. Need more? A pack of 1,000 credits costs €5 ($7), once, and bought credits never expire. When credits run out, nothing is sent or charged, and deploys, logs and monitoring keep working as before. See pricing.

How AI credits work

Why built in

An AI DevOps tool that knows your setup

You can paste a log into a chat window. The difference here is context: AI in Vimonto Deploy already knows the site's framework, PHP version, deploy script, the server's metrics and what changed since the last deploy, so you skip the copying and the explaining, and secrets are taken out before anything leaves.

And it stays in its lane. It reads, explains and drafts; the platform does the work, the way it always has: zero-downtime deploys, provisioning, backups and monitoring. Comparing control panels? See how Vimonto Deploy compares on the comparison pages.

Questions about AI

Do I need Premium to use AI?

No. Every plan gets AI credits every month: 50 on Free and 300 on Premium. You can buy extra credits on any plan.

Does AI ever change my servers or my code?

No. It reads and suggests. Drafts and fixes go into the editor or form and are only saved when you save them, the alarm diagnosis runs read-only checks, and an action proposed in the search only starts when you click Confirm.

Is my .env or are my secrets sent to the AI model?

Your .env file is never sent. Before anything else leaves Vimonto Deploy, secrets are replaced by [redacted]: the values of your .env, server passwords and keys, deploy keys and tokens, Composer and npm credentials, and anything that looks like a password, token or key.

How can AI explain why my deploy failed?

It reads the end of the deploy log, the deploy script and the site's facts, and names the cause in plain language with the likely fixes. When the fix belongs in the deploy script, Write the fix puts it in the editor for you to check.

Can it analyse my Nginx access log without sharing visitor data?

Yes. Analyse traffic with AI turns the access log into figures first. Paths are sent with ids replaced and query strings removed, along with status codes and visitor kinds. IP addresses are only counted, never sent.

Is this like ChatGPT for my servers?

It works much like asking a chat assistant: you ask in plain language and get an answer. But it answers from your own servers, sites and deploys, only sees what you are allowed to see, and can only start a deploy or a backup run after you confirm.

Can AI tell me if my server is too big or too small?

Yes. Advise with AI on the server's Monitoring page reads 30 days of measurements and what runs on the server, and says whether it is oversized, right-sized or close to full, compared with the sizes and prices your provider offers. It needs at least 7 days of measurements.

Which vulnerable packages should I fix first?

When the dependency audit of a deploy finds advisories, Review with AI ranks them for this app as fix now, fix soon or low risk, says whether each package is a direct or transitive dependency, and gives a command to fix it.

Can I switch AI off?

Everything that runs by itself (explaining failed deploys, deploy summaries, the weekly server review) has a switch under Settings → AI. The other features only run when someone clicks them, and viewers cannot start them.

What happens when the AI credits run out?

Nothing is sent and nothing is charged. A button says there are no credits left until the 1st of next month, or until you buy a pack. Deploys, tasks, logs and monitoring do not depend on AI and keep working.

Do unused credits carry over?

The monthly credits do not: they are renewed on the 1st. Bought credits never expire and stay until they are used.

Can AI be wrong?

Yes. Every answer is written by an AI model and says so. That is why nothing it writes takes effect until you have read it and saved it yourself.

A second pair of eyes on every server

Start free, with every feature and monthly AI credits included. No credit card required.