Sign inGet started
Magento and Mage-OS

Your Magento server, run by your AI

From an empty VPS to a production Magento 2 shop, and the daily work after it: failing cron, 500 errors, slow pages, full disks, upgrades and skimmers. Your AI does it through SudoWhizzy with bin/magento and the shop's own database credentials, and asks you before anything destructive.

Connect your server free See the prompt

Works with Claude, Claude Code, ChatGPT and Cursor.

How your AI does it

  1. STEP 1

    It sizes the server first

    Your AI checks RAM, disk and what already runs. Magento needs at least 4 GB of RAM and 20 GB free disk; with 4 GB it adds swap and a small OpenSearch heap and tells you, and below that it recommends a bigger server instead of a slow shop.

  2. STEP 2

    It picks versions that belong together

    It reads the requirements of the newest stable Magento or Mage-OS release and matches PHP, MariaDB or MySQL, OpenSearch, Valkey or Redis and Composer to them, from signed repositories only. It never switches off a signature check to get past an error.

  3. STEP 3

    It builds the stack the way a Magento host would

    nginx with Magento's own nginx.conf.sample, PHP-FPM with every extension Magento needs and tuned OPcache, a secured database with a random password, OpenSearch on localhost, Valkey for cache, full page cache and sessions, and a dedicated system user that owns the code. Long steps such as composer create-project run as background jobs.

  4. STEP 4

    It installs and switches to production

    setup:install with a random admin path and password, production mode, indexers on schedule, Magento cron, Let's Encrypt and https base URLs. Admin two-factor stays on. SELinux stays enforcing, with the right file contexts.

  5. STEP 5

    It checks, saves and reports

    The storefront and admin answer, cron runs and the logs are clean. Credentials go to a root-only file on the server, never into the chat, and a snapshot of the code, /etc and the database is taken before it reports back.

On an existing shop, your AI can

  • Find every shop on the server with list_sites: version, root, owner and database
  • Run bin/magento as the shop's owner: cache, indexers, deploy mode, setup:upgrade, cron
  • Query the database with the shop's own credentials from env.php; reads are read-only
  • Find why the shop returns 500 from exception.log, PHP-FPM and nginx logs
  • Find why cron stopped, and get an email from SudoWhizzy when it stops again
  • Look for skimmers in core_config_data, CMS blocks and recently changed JavaScript
  • Take a snapshot of code and database before an upgrade, and roll back if it goes wrong
  • Write a Magento module on the server, deploy it and check it works

Tested on real servers

From our own test runs with Claude Code on fresh Rocky Linux 10 servers.

30 min

from a raw Rocky Linux 10 box to a live Mage-OS 3.5 shop with OpenSearch 3, Valkey, production mode, cron and Let's Encrypt, in 43 tool calls

0

signature checks skipped: when an OpenSearch 2 package failed its check, the AI used the 3.x repository that passes instead of bypassing it

Start with this prompt

Paste it into your AI with SudoWhizzy connected. It fetches the matching playbook and explains its plan before changing anything.

Using SudoWhizzy, set up my empty server as a Magento shop. Before you start, check the server with server_facts and ask me only for what you do not know, explaining why you need each: - the shop's domain (it should already point at this server) - Mage-OS (no Adobe keys needed) or Magento Open Source (I give you my Adobe access keys) - admin email and name, store language, currency and time zone Then follow the server-setup and magento playbooks (get_playbook). Run long steps with start_job. Do not paste passwords into the chat: write them to a root-only file and tell me where. Finish with a short report: versions, URL, admin path, what I should do next.

Set up a fresh server as a Magento shop · all prompts

Which plan

Starter and up: the Magento, database and snapshot tools are included. Free lets your AI look at the shop read-only. Pricing.

Questions

Mage-OS or Magento Open Source?

Both work. Mage-OS is the community distribution of the same code and needs no Adobe keys, so your AI recommends it when you have none. For Magento Open Source you give it your Adobe Marketplace access keys and it stores them in the shop user's composer auth file.

Does the AI see my database password?

No. db_query and the magento tool read the credentials from env.php on the server, running PHP as the shop's owner, and pass them to the database client in a private file. The password never reaches the chat.

Can it break my live shop?

Reads run at once and changes run after /etc is saved. Dropping or emptying tables, deleting folders and uninstalling the shop wait for your approval, signed in on sudowhizzy.com. Ask for a snapshot before risky work and a rollback is one call away.

Does it work on Debian and Ubuntu as well as Rocky and Alma?

Yes. The playbook covers both families: dnf with the distro's streams or Remi for PHP, and apt with Ondrej's PHP repository when the base is too old.

Safety on every task: destructive actions wait for your approval, /etc is saved before changes, and every action is logged. How it works.

More your AI can do

WordPress and WooCommerce

A fast, secure WordPress server, run by your AI

Fresh VPS

From an empty VPS to a secure web server, by asking

Hardening

Harden your Linux server without locking yourself out

Hacked site

Hacked shop or site? Find it, clean it, close the door

Migration

Move your site to a new server with minutes of downtime

Connect your first server

Start free with one server in read-only mode. Upgrade when you want your AI to fix things.

Get started