Operating ProcedureExecution layer

Microweber White-Label Server Provisioning (Onboarding)

A sequence with 7 steps: Activate the white-label license on the target server IP.

By InnovaAI ResearchPublished

What are the steps?

sequence

Microweber White-Label Server Provisioning (Onboarding)

  1. 01

    Activate the white-label license on the target server IP

    Log into the Microweber white-label admin, bind the license to the server IP, and confirm the Single Server License ceiling of around 5,000 users before you onboard any client. If projected client volume crosses that ceiling, provision against the Multiply Server License (3 IP at $600/month or 5 IP at $900/month) instead of stacking single licenses.

  2. 02

    Rebrand the platform under the agency identity

    Replace the Microweber logo, favicon, and admin panel branding with the agency's own, and point the platform at the agency domain. This is the step that lets delivery hand clients a login screen carrying the agency name rather than the vendor's.

  3. 03

    Set the template and module baseline for client builds

    From the 450+ layouts and 75+ modules, pin a curated shortlist per client vertical so builders do not start from the full library on every project. Keep the AI text generator enabled for copy drafting but require an editor pass before anything publishes.

  4. 04

    Configure ecommerce and multilingual defaults

    Enable product management and order processing only for clients who sell, and import their catalogue via CSV rather than manual entry. Turn on multilingual support at the site level so language variants are set once, not retrofitted after launch.

  5. 05

    Create the client site from the multi-site dashboard

    Provision the client site under the agency's white-label instance, assign the matched template, and set SEO metadata fields before the first content pass. Record the site in the agency's own tracker with the server IP it lives on so license headroom stays visible.

  6. 06

    Hand content editor access to the client with guardrails

    Issue a scoped editor account, not admin, and walk the client through the drag-and-drop builder in a recorded session. Document which modules they may edit and which are locked, so retainer scope stays defined.

  7. 07

    Run a pre-launch check against the license and billing baseline

    Confirm the site resolves on the correct IP, verify the user count against the license tier, and reconcile the vendor cost line (from $220/month entry) against the retainer the client is paying. Flag any client whose hosting margin falls below the agency threshold before launch.