π Language: English Β· π·πΊ Π ΡΡΡΠΊΠ°Ρ Π²Π΅ΡΡΠΈΡ
Open source utility for managing runtime applications on Linux: a daemon and CLI written in Rust that launch and maintain applications of any runtime β Docker containers, native applications (systemd) and plain processes. Included: a package manager, backups, monitoring, and an MCP server for AI. Works standalone via the CLI or as an agent of the AdminService.Cloud SaaS platform. Runs in any Linux environment, including WSL (Windows Subsystem for Linux).
- π± Application management β Docker containers, native applications (systemd) and system utilities
- π» CLI β full server management from the terminal (
asc ...) - 𧬠Instance cloning β
asc app clone <id>: a full copy of an application instance (data, env, settings) with a new id; via the AdminService.Cloud UI a clone can be moved to another node - π‘ ConnectRPC + REST API β the API proto contracts live in this repository (
proto/) and ship together with the daemon; the AdminService.Cloud platform links them from here. REST (JSON/HTTP) runs alongside ConnectRPC on the same server β from the same contracts - π¦ Package manager β an
asc.yamlmanifest, registries (like apt) and installation viaasc install <package> - π€ MCP server β manage the server through AI (Claude Code, Claude Desktop, the ASC platform)
- πΎ Backups β full and incremental, local and to the cloud (S3/SFTP), with rotation
- π Monitoring β system and application metrics, health checks
- π SFTP server β file access isolated to a specific application
- ποΈ Databases β create databases and users (PostgreSQL, MySQL, MongoDB, Redis)
- π₯οΈ Consoles β WebSocket application terminal and SSH console for the UI
- β° Scheduler β scheduled (cron) tasks, a priority queue
- π asc-updater β a separate updater utility: auto-updates (can be disabled), stable/beta channels, rollback; at install time β pick default settings or your own
- π§ Skills for AI agents β ready-made skills for Claude Code and other models in the skills/ directory
Existing panels solve only part of the problem: Portainer manages Docker, Pterodactyl manages game servers, classic hosting panels manage websites. As soon as a real server mixes containers with native services, you are back to raw SSH. asc-daemon was born to manage any runtime through one tool β Docker containers, systemd services and plain processes β with the same commands, the same API and the same package manager. And because AI agents are becoming the way servers get managed, the daemon speaks MCP natively, so an AI can operate your server as a first-class client. The daemon is fully autonomous: everything works locally via the CLI, no platform account required.
curl -fsSL https://raw.githubusercontent.com/AdminServiceCloud/asc-daemon/main/install.sh | sudo bashinteractive: shows the default settings and asks β accept or change
curl -fsSL https://raw.githubusercontent.com/AdminServiceCloud/asc-daemon/main/install.sh | sudo bash -s -- --silentsilent mode: one command, everything installed with defaults and no questions
You can also configure it after a silent install: asc-updater + /etc/asc/config.toml.
- π§ OS: Debian and Ubuntu are supported today, including under WSL (Windows Subsystem for Linux); other distributions (CentOS/RHEL, Fedora, Arch, etc.) and macOS are planned
- 𧬠Architectures: x86_64, ARM64, ARMv7
- π Root/sudo for installation; Docker is installed automatically when needed
- βοΈ systemd (for
asc serviceand autostart)
asc service installβοΈ install the daemon's API service as a systemd unit (autostart)
asc service start|statusπ start the service / check its state
asc statusπ server and application status
asc install helloworldπ¦ install an application from the registry
asc app logs helloworldπ application logs
asc app clone helloworld𧬠clone an application instance (data, env, settings)
asc app settings helloworldποΈ interactive settings editor (types, limits and enums from asc.settings.yaml)
asc config lang ruπ change the CLI output language (en|ru)
asc connect <token>βοΈ connect to the AdminService.Cloud platform
asc mcp serveπ€ run the MCP server for AI clients
The skills/ directory contains ready-made Agent Skills that teach AI agents to manage the server through asc:
cp -r skills/* ~/.claude/skills/Claude Code: install the skills globally (for all projects)
cp -r skills/* .claude/skills/Claude Code: install the skills for the current project only
| Skill | What it does |
|---|---|
| π₯οΈ asc-server-management | Server management: applications, logs, backups, databases. If asc is not installed, it checks, then offers to install it from the official repository with a single command (silent mode) |
| π¦ asc-app-packaging | Packaging applications: asc.yaml / asc.stack.yaml, validation against schemas, publishing to a registry |
For MCP clients (Claude Desktop and others) use the daemon's MCP server instead of skills: asc mcp serve.
Documentation for the daemon's modules lives in the docs/english/ directory (π·πΊ Russian version):
| Doc | Description |
|---|---|
| π¦ Daemon overview | Architecture, API, installation |
| π‘ api | gRPC (ConnectRPC) + REST on one port, tokens |
| π± app-management | Docker and native applications, CLI |
| π¦ package-manager | asc.yaml, registries, asc install |
| π€ mcp-server | MCP server for AI |
| π monitoring | System and application metrics |
| πΎ backups | Application backups |
| π sftp | SFTP isolated per application |
| ποΈ database | Database management |
| π₯οΈ console | WebSocket and SSH consoles |
| β° scheduler | Task scheduler |
| π updater | The asc-updater utility: auto-updates, channels, rollback |
The roadmap for the whole project is kept in the asc-platform repository:
- π― ROADMAP β daemon tasks use the
DMN-*prefix - π€ Development process
Reach out to the maintainers through any of these channels:
- π GitHub Issues β bug reports and feature requests (templates included)
- β GitHub Discussions β questions and ideas
- βοΈ adminservice.cloud β the platform website and contact options
If you want to say thank you or support the active development of asc-daemon:
- β Add a GitHub star to the repository
- π¦ Share the project on social media
- π Write about the project on your blog or at meetups
- π€ Contribute β code, docs, translations, registry packages
Contribution rules are in CONTRIBUTING.md; CI and releases run on GitHub Actions (.github/workflows/). Developing on Windows? Use WSL (Ubuntu) to build and test the project: cargo build / cargo test run in WSL, while cargo check / clippy work from the host against the Linux target (see .cargo/config.toml). Every pull request automatically gets a review from the code owner (@statebyte) via CODEOWNERS.
Please read our π€ Code of Conduct before participating β we are committed to a welcoming and harassment-free community.
The original setup of this repository is by Omar El Sayed (@statebyte), AdminService.Cloud, Anytecture Software.
For a full list of all authors and contributors, see the contributors page.
asc-daemon follows good practices of security, but 100% security cannot be assured. The software is provided "as is" without any warranty.
Found a vulnerability? Please report it privately β see our π‘οΈ Security Policy.
MIT β free to distribute, modify and use commercially, but with mandatory attribution: Omar El Sayed (@statebyte), the AdminService.Cloud project, Anytecture Software.