How long does VICIdial provisioning actually take?

When we say "live in under 60 seconds" we mean it. Here's the breakdown of what's actually happening in those seconds.

The clock starts at card validation

Order → card validates → we kick off provisioning. From that instant:

| Second | What's happening | | ------- | ------------------------------------------------------- | | 0 - 4 | Cloud server allocated, IPv4 assigned | | 4 - 8 | DNS A record created in your zone | | 8 - 12 | First boot, base image personalization begins | | 12 - 20 | Database initialized, VICIdial schema applied | | 20 - 30 | Asterisk + Apache + firewall configured for your domain | | 30 - 40 | Let's Encrypt TLS cert issued via DNS-01 | | 40 - 52 | Smoke check: HTTPS admin URL responds | | 52 - 58 | Email sent, server.status = ACTIVE |

That's a representative run. The variance is mostly in the cert issuance step — DNS propagation can take a few extra seconds depending on resolver caches.

Why this matters

Self-hosted from scratch on a fresh Ubuntu box: 45 minutes minimum, often a full day if it's your first time and apt is slow. We watched our own first-time install take a weekend in 2018.

Other managed VICIdial hosts: 15-30 minutes typical. Better than self-host, but you're still waiting half an hour for a server you paid for.

Under 60 seconds means:

• You order in the middle of a sales call, the server's ready before you hang up.
• You can demo VICIdial to a customer live, on screen-share.
• You can spin up + tear down per project, not per year.

What we don't compromise to get there

• Asterisk built fresh, not reused across customers.
• TLS cert issued for your FQDN, not a wildcard.
• Random DB credentials, random admin password, random firewall port. No two customers share secrets.
• Full firewall ruleset configured before the box accepts public traffic.

What you'll see

The dashboard shows the live deploy timeline as it runs. You'll get an email the moment your admin URL is reachable.