Start deploying

Infrastructure control

Your servers.
Your cloud.
One control panel.

Hardened servers in the cloud account you already pay for. Deploys that go live only when they’re healthy. Incidents that tell you what to do next.

  • AWS
  • Google Cloud
  • DigitalOcean
  • Your own server
Start deploying How a deploy works
Fig. 1 · Dashboard · sample workspace
01 · Needs attention
Open incidents, with a suggested next step when Alios has one.
02 · Fleet load
CPU and memory for every server, live from the agent.
03 · Site uptime
30 days of one-minute checks, plus SSL expiry.
04 · Deploy log
Every deploy, rollback and image update, with its commit.
Clouds 3 AWS · Google Cloud · DigitalOcean
Uptime check 60s every site, every minute
Deploys ZERO downtime · health-checked swap
Runtimes 5 PHP · Node · Ruby · Go · Static
SSL AUTO issued and renewed by Caddy
01 · Provision

Every server Alios creates goes through the same pipeline.

Connect DigitalOcean or Google Cloud with OAuth, or give AWS a scoped cross-account role. Pick a size and region, and Alios builds the server the same way every time. Docker and the Caddy proxy go on with your first site.

Provisioning · eu-web · fra1 Running 6 / 6 complete
  1. 01 Check connection Reach the new instance over SSH
  2. 02 Configure firewall ufw on: SSH rate-limited, HTTP and HTTPS open
  3. 03 Harden SSH Password logins off, keys only
  4. 04 Create user The account you’ll use on the server
  5. 05 Add SSH keys The keys from your profile
  6. 06 Install monitoring agent Streams CPU, memory, disk and I/O
02 · Deploy

Traffic moves only when the new build is healthy.

Each deploy starts a fresh container next to the live one, runs your post-start commands and health-checks it. If it fails, the old container keeps serving and you get its logs. Roll back to any earlier image in one click.

  • Laravel
  • WordPress
  • Next.js
  • Nuxt
  • Express
  • Rails
  • Static
  1. 01 Build
  2. 02 Start
  3. 03 Post-start
  4. 04 Health check
  5. 05 Swap
  6. 06 Proxy
09:41:02build image from main @ 3f2c1a9
09:41:48start shop-web-3f2c1a9
09:41:51exec php artisan migrate --force
09:41:55health GET / → 200 in 84ms
09:41:55swap shop-web-a91be07 → shop-web-3f2c1a9
09:41:56proxy caddy reloaded
09:41:56live shop.example.com
03 · Monitor

Watched every minute. Including sites Alios doesn’t host.

Uptime and response time for every site, SSL expiry and blocked renewals, and live CPU, memory, disk and I/O from a lightweight agent on each server. Point a monitor at any URL, even one Alios doesn’t host.

Site uptime · 30 days1 cell = 1 day
shop.example.com 100.0
app.example.io 99.96
blog.example.org 98.70
clinic.example.com 99.91
docs.example.dev 100.0
status.example.net 99.98
Server thresholds
CPU
at or above → incident
95%
Memory
at or above → incident
95%
I/O wait
disk contention
20%
CPU steal
noisy neighbours
10%
04 · Respond

An incident that tells you what to do next.

Incidents open and resolve themselves with the checks. The team owner gets an email about each new one, and where Alios can tell what to try, the incident suggests a next step drawn from what it already knows: the last deploy, the server’s memory, the DNS it sees.

Incident Crit INC-2F81A Site is returning 502 Bad Gateway blog.example.org Opened 09:28 · Acknowledged 09:31
→ Next step A deploy finished just before this started The last deploy (b41e0c2) finished 2 minutes before this incident opened, so it’s the most likely cause. If it is, redeploy the previous commit from the deploy history. Based on: deploy (b41e0c2) finished at 9:26 AM, 2 minutes before this incident opened
Timeline
  1. 09:28 Opened by uptime check · owner emailed
  2. 09:31 Acknowledged by Mike
  3. 09:32 Mike: redeploying the previous commit
05 · Security

Locked down before your first deploy.

Every server Alios creates is hardened during provisioning, the same way every time. Bring a server you already run and you can turn on the same firewall and SSH hardening from its server panel.

SSH
Password logins off, SSH keys only, and attempts rate-limited by the firewall.
Firewall
On from the start: SSH rate-limited, HTTP and HTTPS open, nothing else. Open more ports from the server panel.
Secrets
Tokens and passwords are redacted from the activity log before it’s stored.
Teams
Each team’s servers and sites are walled off. Read-only members can look but change nothing.
/etc/ssh/sshd_config.d/00-alios-hardening.confApplied
PasswordAuthenticationno
PermitRootLoginprohibit-password
MaxAuthTries4
LoginGraceTime30
X11Forwardingno
$ sudo ufw statusActive
ToActionFrom
OpenSSHLIMITAnywhere
80/tcpALLOWAnywhere
443/tcpALLOWAnywhere
06 · Pricing

One flat price. Your cloud bill stays yours.

Servers run in your own AWS, Google Cloud or DigitalOcean account and bill there. Alios charges only the plan below, with no markup on compute.

Solo Freelancers and side projects $19 / month Billed monthly Start with Solo
Servers
3
Sites
15
Workspaces
1
Team roles (Admin, Editor, Read-only)
Not included
Zero-downtime deploys + rollback
Included
Uptime, SSL + server monitoring
Included
Incidents with suggested next steps
Included
Firewall + SSH hardening
Included
Activity log with secret redaction
Included
Priority support
Not included
Business Most popular Agencies and teams running client work $49 / month Billed monthly Start with Business
Servers
Unlimited
Sites
Unlimited
Workspaces
Unlimited
Team roles (Admin, Editor, Read-only)
Included
Zero-downtime deploys + rollback
Included
Uptime, SSL + server monitoring
Included
Incidents with suggested next steps
Included
Firewall + SSH hardening
Included
Activity log with secret redaction
Included
Priority support
Included
Prices in USD · servers are billed by your cloud provider · change plans or cancel any time from the billing portal
07 · FAQ

Questions, answered.

Do I pay for servers through Alios?

No. Servers run in your own AWS, Google Cloud or DigitalOcean account and are billed there at their normal rates. Alios charges only the flat plan price.

What can I deploy?

Anything that runs in a container: PHP, Node, Ruby, Go or static sites, with first-class setups for Laravel, WordPress, Next.js, Nuxt, Express and Rails. Build from a GitHub repo, start from an Alios base image, or pull your own image.

What happens if a deploy fails?

The new container has to pass its health check before any traffic moves, so the live site keeps serving. You get the failed container’s logs and can roll back to any earlier image in one click.

Can I monitor sites Alios doesn’t host?

Yes. Add any URL as a monitor-only site for one-minute uptime checks, SSL expiry tracking and incident alerts.

How do alerts reach me?

By email to the team owner when a new incident opens, with a link to it. The incident keeps a timeline, suggests a next step where Alios can tell what to try, and resolves itself when the check recovers.

Get started

Connect a cloud. Ship something.

Start deploying
  1. 01 Connect Link AWS, Google Cloud or DigitalOcean, or add a server you already run.
  2. 02 Provision Pick a size and region. Alios builds and hardens the server.
  3. 03 Deploy Ship from a GitHub repo or an image. It goes live once it’s healthy.