Requirements
What you need to run Sitewyn.
Sitewyn is a self-hosted Node.js platform that issues certificates and serves your customers’ websites itself. It needs a server you control.
Server
| Minimum | Recommended | |
|---|---|---|
| CPU and memory | 2 vCPU, 4 GB RAM | 4 vCPU, 8 GB RAM |
| Disk | 40 GB SSD | 80 GB SSD or S3-compatible storage |
| Operating system | Ubuntu 22.04 or 24.04 (Debian 12 works) | Same |
| Software | Docker Engine 24+ with Compose v2 | Same |
| Network | Public IPv4, ports 80 and 443 open | Same, plus IPv6 |
The Docker stack brings Node.js 22, PostgreSQL 16, Redis 7 and Caddy with it. Hosts without Docker can follow the PM2 and Caddy path in the HTML manual included in the download, on the same kind of server.
Domain and DNS
- Your app domain
- An A record, for example studio.example.com pointing at your server IP
- Customer subdomains
- A wildcard record, for example *.sites.example.com pointing at your server IP
- Customer domains
- Each customer adds one A record, or a CNAME for www, pointing at your server
- Certificates
- Issued automatically by Caddy with Let’s Encrypt; nothing to buy
Accounts and keys
Required
- At least one AI provider key: OpenAI, Anthropic, Gemini, OpenRouter or an OpenAI-compatible endpoint
- The purchase code or licence key from the platform you bought on
Optional
- SMTP, Resend, Mailgun, SES or Postmark for email
- An image generation provider, and Unsplash or Pexels keys for stock photos
- S3-compatible object storage
- Cloudflare Turnstile or reCAPTCHA keys for form spam protection
- Accounts with the payment gateways you want to offer
Not for shared hosting
Shared cPanel or Plesk hosting cannot run Sitewyn. It has to listen on ports 80 and 443 to issue certificates for your customers’ domains, keep Node.js processes and a background worker running, and serve many hostnames from one server. Shared plans allow none of these.
Install in one command
$ unzip sitewyn-v1.0.0.zip && cd sitewyn-v1.0.0/source/sitewyn/deploy$ bash scripts/install.sh --domain studio.example.com --email you@example.com
The script checks Docker, ports, DNS, disk and memory, writes the environment file with generated secrets, then builds and starts the stack. The web installer creates your super-admin account and verifies your purchase code.