Its own technology stack
Containers, the web server, certificates and agent tools are selected and configured to work together from the first start.
You install ContextAdmin on a server you administer. You need Linux with systemd and administrator privileges; on Windows you can set up such an environment in WSL.
Installation has been tested on Debian 13. The installer supports the apt, dnf, pacman and apk package managers. It requires systemd and root or sudo access.
You run the panel inside WSL with systemd enabled. The Local plan is meant for local projects.
The starting point is 2 GB of RAM. The panel binary takes about 160 MB; plan extra memory and disk for applications, databases and backups.
For your own domain and certificate you need a correct DNS record. You can also set up access to the panel through an IP address or an SSH tunnel.
Download the installer and answer its questions: purpose, panel access, software, license key and administrator password. Running it again updates and repairs the installation while keeping your data, projects and license.
curl -fsSL https://dist.contextadmin.com/setup -o setup.sh
sudo bash setup.sh
# answer the questions and check the summary
# confirm the settings before the installation starts
You install a carefully prepared technology stack with ready configuration, security and optimization.
Containers, the web server, certificates and agent tools are selected and configured to work together from the first start.
We built a secure structure for hosting and publishing in containers, based on the experience of our developers.
Log limits, projects restarted after a server reboot, a separate port for each project and application uptime checks.
The panel runs on popular Linux distributions and installs and configures the tools it needs by itself.
Systems
Tools
Names and logos belong to their owners. Other distributions with systemd and the apt, dnf, pacman or apk package manager are also supported.
The AI accounts are yours. Add profiles for the accounts you use and pick one when you start a session. You pay for model access separately, directly to the provider.
Before you start, check permissions, the machine's resources and the access method you chose.