← All guides

Managed website hosting

Take a client website from source to a managed production pipeline

AnchorScape hides the container and Kubernetes assembly work behind a guided flow. Give it a repository or ZIP, choose the client and environment, and the platform prepares, deploys and verifies the site.

Result: A client site with isolated dev, staging and production environments, a verified domain, release history and a repeatable update, recovery and rollback path.

Start a website deployment

What you can host

  • Static HTML, CSS and JavaScript websites.
  • React, Vue, Vite, Next.js and other recognised frontend applications.
  • Server-rendered websites and APIs in supported Node.js, Python, PHP, Go, Java, .NET, Ruby and Rust stacks.
  • Existing Dockerised websites when the repository already defines the runtime.
  • Managed WordPress and WooCommerce with MariaDB, persistent uploads and recovery controls.

What you provide

  1. 1Choose a connected GitHub repository, public Git URL or source ZIP.
  2. 2Select the client application and start in dev.
  3. 3Add only the runtime secrets or external credentials the site genuinely needs.
  4. 4Test the generated dev URL before approving promotion.

What AnchorScape does

  1. 1Inspects the source and detects the framework, runtime, build command, port and database requirements.
  2. 2Uses an existing production Dockerfile or generates the missing container build for recognised stacks.
  3. 3Installs production dependencies without copying development and test tooling into the runtime.
  4. 4Builds and records an immutable release image.
  5. 5Deploys into the client’s isolated environment with resource limits, network policy, health checks and TLS.
  6. 6Runs post-deployment verification and keeps logs, diagnostics and rollback evidence with the release.

The release pipeline

  1. 1Deploy new source to dev.
  2. 2Promote the exact verified image to staging—AnchorScape does not rebuild it differently.
  3. 3Approve promotion of that same image to production.
  4. 4Add the client domain, copy the displayed DNS record and choose Verify domain.
  5. 5AnchorScape provisions TLS and retains the previous release for rollback.

How client sites stay separate

  • One application/project per client and separate dev, staging and production environments.
  • A dedicated namespace, resource boundary, network policy and release history for each environment.
  • Standard websites reject common WordPress exploit probes instead of forwarding them to the application.
  • Managed WordPress receives a different workload profile so legitimate WordPress routes work while sensitive paths remain protected.
  • Stateful production readiness includes paired backup and verified restore evidence.

Need help on the screen?

Open Anchorton and ask where a setting belongs. For runtime questions, open it from the deployment context so it can use the permitted status, event and log tools.