Features
Every step from domain to live site, handled.
The features below describe what CloudMagnus actually does today, not what it might do later. If you need to see it in detail, the docs walk you through every flow.
Managed provisioning
Adding a site is a wizard, not a checklist. Pick a framework, type a domain, and the platform walks the work: site user created, vhost configured, database provisioned (for PHP-backed and Python-backed types), framework scaffold installed, port allocated for Node and Python apps, all coordinated through a state machine that tracks every stage.
Real state machine
Every site goes through created → DNS waiting → DNS verified → SSL issuing → SSL issued → live. Failures land in named states (DNS failed, SSL failed) with specific copy explaining what to fix. No "try again later" without a reason.
Per-site isolation
Each site runs as its own system user with its own database credentials, its own SFTP login, and its own filesystem permissions. No shared mounts, no cross-site reads.
Honest failure reporting
If provisioning fails, the dashboard tells you which stage and why. The customer-facing copy maps to a small failure-reason vocabulary so the same problem always reads the same way.
Framework scaffolding
Pick a framework in the wizard and CloudMagnus installs it for you. Not "creates an empty directory and tells you what to install." The actual framework, with its dependencies, configured to talk to the database we just provisioned.
WordPress
WP-CLI downloads core, runs wp config create against the new database. You land on the install screen ready to enter your admin user and email.
Laravel
composer create-project installs Laravel. Your .env is pre-populated with the database we provisioned. php artisan key:generate already ran. Run migrate when you're ready.
Django
Virtualenv created, Django and Gunicorn installed, django-admin startproject executed. settings.py has your database connection wired in. You handle migrate and your app code.
Next.js
npm init, install of next, react, and react-dom, plus a placeholder app on the allocated port. Build locally; deploy via SFTP.
Generic stacks
PHP, Node.js, and Python all get clean working directories with a placeholder welcome page on the right port. Bring your own framework.
Static and React SPA
An htdocs/ directory ready for your build output. Drop the contents of dist/ via SFTP and you're live.
SSL handling
Let's Encrypt issues your certificate as soon as DNS resolves. Renewal is automatic. The platform handles the three failure modes we've actually seen in pre-flight: rate limits, DNS timing gaps, and CAA records.
Automatic issuance
The moment your A record resolves on both Cloudflare and Google's resolvers, the platform calls Let's Encrypt and installs the cert. No buttons to click, no flags to set.
CAA pre-check
If your domain has a CAA record that excludes Let's Encrypt, we surface that before calling LE so we don't burn a rate-limit slot on a domain that won't accept us. The dashboard tells you exactly which CAA record to add or remove.
Bounded retry
Transient failures (Let's Encrypt rate limits, DNS timing gaps where ACME's resolver lags ours) retry on a 1-hour, 6-hour, 24-hour schedule. After three attempts, the dashboard shows the failure reason and a manual retry button.
DNS guidance
DNS is the part of hosting where customers spend the most time stuck. CloudMagnus is honest about what it can see and what to check.
The exact record to add
The status page shows you the A record (type, name, IP, suggested TTL) with a copy-to-clipboard button on the value. No more typo-driven failures.
Live resolver readout
The page polls Cloudflare 1.1.1.1 and Google 8.8.8.8 every few seconds and shows you what each resolver currently sees. Mismatch is visible immediately.
Troubleshooting tree
After 30 minutes of unverified DNS, the page reveals the four common failure modes in plain language. After 24 hours, a support contact appears.
Operations
The bits that aren't user-facing but matter when something goes wrong.
Daily off-site backups
Every site backed up nightly to off-server storage. Restore via the dashboard. Backup retention is seven days; older copies are pruned.
Uptime monitoring
Per-site HTTP checks every minute. Status visible to you in the dashboard. The operator gets paged when a site is down.
Direct operator support
Email reaches the person who built the platform, not a tier-one queue. Same-day response on Business and above; next-day on Starter and Growth.