Getting Started with strackt

strackt manages the code you write, on servers you own. You bring your application and a server — one you already rent, or a fresh one from a cloud provider — and strackt handles the rest: provisioning it, deploying your code, keeping it patched, and watching over it. Getting your first application live is two steps.

Most applications arrive as a git repository, and from then on you deploy by pushing a commit. A WordPress site is the exception: it can be created without a repository, or brought over from a site you already run, and strackt keeps it inventoried, updated inside a protected pipeline, and one click from a restore point.

What strackt does not do: packaged software you install rather than write — Nextcloud, Immich, Vaultwarden and the like — is outside what strackt does, even when it happens to be written in a language strackt supports. Those ship as prepared release archives rather than buildable source, which is a different job; Coolify does it well. That stays true however you host it, and whoever you run it for.

1. Connect a server

Point strackt at a server you control. It takes over the machine, prepares it with everything your applications will need, and from then on manages its updates and security for you. This usually takes a few minutes.

Start with Connect a server.

2. Add and deploy your application

With a server connected, add your application. For most applications that means telling strackt where your code lives and confirming what it detects your app needs; a WordPress site is instead created fresh or brought over from a site you already run, with no repository to point at. Either way strackt configures the server and runs the deploy for you, showing each step live.

Walk through the repository route in Add and deploy an application, or the WordPress route in Add a WordPress site.

From here

Once your application is running, you'll usually want to point a domain at it and set its environment variables. An application built from a repository also needs you to add the databases or caches it asks for; a WordPress site already has those. Each of those has its own short guide, and there's one for what to check when something doesn't go to plan. You manage all of it from the same place — your servers stay yours, and strackt keeps them running.