StavenCTL Documentation

Install, configure, and operate self-hosted Linux hosting.

Use this guide as the product-ready entry point for StavenCTL setup, server requirements, core workflows, and launch checks.

Install Command

Run on your Linux server

Linux
curl -fsSL https://stavenctl.com/install.sh | sudo bash
Ubuntu, Debian, or Fedora Linux server
Root or sudo access for provisioning and service control
Public DNS records pointing to the server
Open HTTP and HTTPS access for certificate issuance

Quickstart

Three steps from server access to first hosted site.

Keep the setup path simple: prepare the server, install the control services, then create the first production workflow.

Step 1

Prepare the server

Start with a clean Linux VPS or dedicated server, sudo access, a public IP address, and DNS pointed at the machine.

Step 2

Run the installer

Install the StavenCTL control services and validate required packages for Nginx, SSL, files, backups, and monitoring.

Step 3

Create the first site

Add a domain, assign ownership, choose the document root, enable SSL, and let StavenCTL prepare the runtime workflow.

Server Requirements

Baseline checks before installation.

StavenCTL is designed for operators who want direct control over Linux hosting while keeping repeatable work in a dashboard.

Ubuntu, Debian, or Fedora Linux server
Root or sudo access for provisioning and service control
Public DNS records pointing to the server
Open HTTP and HTTPS access for certificate issuance
Enough disk space for hosted sites, logs, and backup restore points
Outbound network access for package and certificate operations

Launch Checklist

SEO and product-readiness checks after deployment.

These are the final checks to run once the updated site is live on stavenctl.com.

Submit /sitemap.xml in Google Search Console after deployment
Confirm /robots.txt allows crawling and references the sitemap
Verify HTTPS, canonical URLs, Open Graph previews, and favicon assets
Review every public navigation link for a 200 response
Keep release notes and documentation current as product workflows change