VICIfast
Feature · One-Click Resize

One-Click Resize.

Outgrown Growth? Move to Scale. Outgrown Scale? Move to Dedicated. Pick the new tier in the dashboard; we plan the move, take a fresh snapshot, resize the underlying VPS, restart services, and verify VICIdial is reachable on the bigger box. Average wall-clock: 3 minutes downtime, total. Your data, your config, your IPs — all preserved. No re-install, no re-import, no surprises.
See pricing

7-day free trial · Cancel anytime · Pay with card, PayPal, or USDT

vicifast — one-click-resize
[2026-05-21 11:14:02Z] resize_requested  · plan=growth → scale
[2026-05-21 11:14:03Z] capacity_probed    · region=fsn1 OK
[2026-05-21 11:14:04Z] snapshot_create    · pre-resize (47 GB)
[2026-05-21 11:14:48Z] services_stop      · asterisk, vicidial
[2026-05-21 11:14:52Z] hetzner_resize     · cpx22 → cpx32
[2026-05-21 11:16:30Z] hetzner_active     · 4 vCPU → 8 vCPU
[2026-05-21 11:16:34Z] services_start     · asterisk + vicidial
[2026-05-21 11:16:41Z] smoke_passed       · admin URL reachable
[2026-05-21 11:16:41Z] state: ACTIVE       (downtime: 1m 53s)
40smedian deploy time
99.94%fleet uptime · last 30d
6regions live
Auditedevery state change

What you get

The full one-click resize surface, end-to-end.

Every card below is a shipped capability. Hover for emphasis; click any matching feature for the deep page.

Same data, same config, same IPs

Resize works in-place on the Hetzner server — your IPv4 keeps its address, your DNS records stay, your VICIdial config stays. You log in to the same admin URL on a bigger box.

Pre-resize snapshot as a safety net

A fresh Hetzner snapshot is taken before the resize begins. If anything fails on the bigger SKU (rare — capacity is probed up front), we restore in <60 seconds. Auto-refund on the resize fee if the move fails.

Capacity check before charging

We probe Hetzner for the target SKU's availability in your region before the resize fires. If the region is full, we tell you up front and propose a sibling region you can move to next time.

Resize up or down

Downgrades at period-end (pro-rated billing). Upgrades immediate. Either way the resize machinery is the same — same snapshot, same service-restart, same smoke test.

Schedule it for off-hours

Resize can fire now or at a future timestamp. Most operators schedule for 03:00 server-local; the dashboard takes a cron-style spec. ~3 minutes of downtime at the floor's quietest hour.

Not a "create new server, migrate data" pattern

The Hetzner SDK supports in-place resize at the hypervisor level. No DB dump + restore, no IP swap. Less surface area to fail; less time spent moving bytes.

Pro-rated billing, no surprise

Upgrade mid-period: pro-rated to the new tier from the resize timestamp. Downgrade: takes effect at period boundary, you keep the bigger SKU until then. Stripe handles the math; the next invoice line-itemises the delta.

API for capacity-aware automation

POST /api/v1/servers/{id}/resize from a cron or a Lambda. Same auth as the dashboard, same state machine, same email confirmation. Useful for ops teams that scale up for Monday-AM peak and back down for the weekend.

Real resize timeline from a recent move (Growth → Scale). The pre-resize snapshot is the safety net; if the bigger SKU bounces, we restore. Less than two minutes of agent downtime.

FAQ

Questions worth answering

Outgrew Growth? Move to Scale in three minutes.

Start the trial. Resize lives in the dashboard from day zero. Pick the next tier; we plan the move, take the safety snapshot, swap SKUs. Same IPs, same data, ~3 min downtime.

All features