CloudStick

Spin up and run your sites from one place, no matter where your machines live. Start by linking your cloud accounts to CloudStick using API tokens from providers like DigitalOcean, Linode, AWS, Google Cloud, or Vultr. Prefer bare-metal or your own KVM box? Add it by IP and SSH, and CloudStick will harden access, configure users, and apply sane defaults. Choose a region and size, then let the platform install the web stack, set up firewalls, and verify health. Every step is recorded in a live timeline so you can confirm who did what and when.

Next, wire your code to your server. Connect a GitHub, GitLab, or Bitbucket repository, pick a branch or tag, and define build steps for your stack—Composer for PHP, npm or pnpm for Node, or your own script. Add environment variables and secrets without committing them to source control. On deploy, CloudStick builds artifacts, runs migrations, and switches traffic with zero downtime. Push a new tag to kick off an automatic release, and roll back in a click if something misbehaves. Use guarded deploys and required approvals to keep production safe when multiple developers collaborate.

Point traffic in minutes. Attach a domain or subdomain, copy the suggested DNS records, and enable automatic certificates so HTTPS just works. Terminate TLS before it reaches your app processes to reduce CPU load, then redirect all traffic to secure endpoints. Map multiple domains to a project, create staging URLs for previews, and keep certificates renewing in the background. If you manage high-traffic sites, route assets through offloaded encryption to keep response times consistent while your app focuses on business logic.

Operate with confidence after launch. Use the activity feed to watch deploys, new signups, purchases, and other app events you forward via webhook, and route critical notifications to Slack or email. Plan releases on the built-in tasks board, assign owners, and prioritize work so your team knows what ships next. Schedule recurring jobs with cron, manage workers and queues, and track status across environments. Typical flow: connect your cloud account, provision a server, link your repo, set env vars, map your domain with HTTPS, invite your team, then ship with a tagged release. For agencies, create a template configuration, clone it for each client, lock down roles per project, and keep an audit-ready trail of changes across all servers.