Skip to content

What Happens During Provisioning

Last updated: March 2026

What happens behind the scenes

When you click Deploy and complete payment, OneClickClaw kicks off a fully automated provisioning pipeline that transforms a bare virtual private server into a production-ready AI agent host. This section explains every step of that process in plain language so you know exactly what is happening while you wait.

You do not need to understand any of this to use OneClickClaw. It all happens automatically. But if you are curious about what is going on during those 5 minutes, read on.

Note

If provisioning takes longer than 10 minutes, please open a support ticket. Our team is automatically alerted when provisioning exceeds the expected time window, but a support ticket ensures we prioritize your deployment.

Provisioning timeline

The total provisioning time is approximately 5 minutes, broken down into three stages:

1

Server creation (~2 minutes)

A brand-new virtual server is created in our EU datacenter in Denmark. The server is provisioned with the exact CPU, RAM, and SSD specifications matching your plan (for example, 2 vCPU and 4 GB RAM for the Starter tier). By the end of this step, a fresh Ubuntu installation is running and accessible over the network.

2

Software installation (~2 minutes)

Our bootstrap script runs on the new server and installs everything your agent needs:

  • Node.js (the runtime that powers OpenClaw)
  • OpenClaw (the AI assistant gateway software)
  • Nginx (the web server that handles encrypted traffic)
  • SSL certificates (so all connections are secure)
  • Process manager (keeps OpenClaw running 24/7, restarts it if it crashes)

The script also hardens security by configuring the firewall, disabling password login, and setting up SSH key authentication.

3

Configuration and connectivity (~1 minute)

OpenClaw is started as a managed service, health monitoring is enabled, and the server sends a secure callback signal to OneClickClaw confirming it is ready. At this point your server appears as "Online" in your dashboard and the Onboarding Wizard launches automatically.

Provisioning Progress — What You See

Stage 1: Creating Server

✓ Complete — VPS created in Denmark (DK-DC1)

AMD EPYC processor, DDR5 RAM, NVMe SSD allocated

Stage 2: Installing Software

✓ Complete — Ubuntu hardened, OpenClaw installed

Nginx configured, SSL certificates provisioned

Stage 3: Configuring Agent

⟳ In progress — Starting OpenClaw, enabling monitoring...

Ready

○ Waiting — Onboarding Wizard will launch when ready

What each status means

During provisioning, your server passes through several status states. Here is what each one means:

StatusWhat It MeansAction Required
ProvisioningYour server is being created and configured. The automated pipeline is running.None. Wait for completion (~5 minutes).
Setting UpThe server exists and software is being installed. Security hardening is in progress.None. Almost done.
Ready / OnlineYour server is fully configured and running. OpenClaw is active and waiting for configuration.Complete the Onboarding Wizard to configure your agent.

Note

You may also see brief intermediate states like "Installing packages" or "Configuring Nginx" in the detailed progress view. These are normal sub-steps within the main stages.

What can go wrong

Provisioning failures are uncommon, but when they do occur they typically fall into a few categories:

  • Infrastructure delays. The datacenter may be experiencing unusually high demand, which can slow down server creation. These delays are temporary and usually resolve within minutes. The provisioning pipeline automatically waits and retries.
  • Network issues. If a software repository is temporarily unreachable, package installation may fail. Our bootstrap script includes automatic retries with exponential backoff for transient network errors.
  • Hardware allocation failure. In very rare cases, the specific hardware configuration may be temporarily unavailable in the datacenter. If this happens, our system automatically retries on alternative hardware within the same datacenter.

In all cases, OneClickClaw monitors the provisioning pipeline and takes corrective action automatically. If automatic recovery fails, our support team is alerted and intervenes manually. You are never charged for a deployment that does not complete successfully.

Warning

If your deployment has been stuck in "Provisioning" status for more than 15 minutes, something has gone wrong. Contact support and we will resolve it. You will not be charged for the failed deployment.

How we know when your server is ready

Once the bootstrap script finishes installing and configuring everything on your new server, the server sends a secure callback signal to OneClickClaw. Think of it like a notification from the server saying, "I am set up and ready to go." This callback includes a cryptographic token that proves the signal is authentic and not coming from an impersonator.

When OneClickClaw receives this callback, it updates your dashboard status from "Provisioning" to "Online" and launches the Onboarding Wizard. If the callback does not arrive within the expected time window, our system automatically checks on the server and, if needed, retries the final configuration step.

This two-layer approach (callback plus automatic health check) ensures that no deployment gets stuck in a "Provisioning" state indefinitely. Even if the callback fails due to a network blip, the health check system catches it within minutes and completes the process.

Tip

You do not need to understand or interact with the callback system. It operates entirely behind the scenes. All you need to do is wait for the "Online" status to appear in your dashboard, and then complete the Onboarding Wizard to finish setting up your agent.