Deploy from Git, ZIP,
or Docker
Connect GitHub, GitLab, or Bitbucket with scoped deploy keys. Upload a ZIP, pull a Docker image, or start fresh. Per-app deployment scripts and one-click staging environments.
3
Git providers
14
Stacks supported
1
Click to staging
0
Config files to touch
Five ways to deploy a server
Whether you're starting fresh, bringing existing code, or running containers, SharkCluster has a deployment method for you. Each configures the stack automatically — you don't touch a config file.
Fresh Install
Choose frontend, backend, database & web server
Git Deploy
Clone & deploy from GitHub, GitLab, or Bitbucket
Upload ZIP
Upload existing source code directly
Custom Migration
Bring an existing site from another host
Docker Host
Run containers with CPU, memory & registry config
Blank Server
Configure everything manually
Git deploy with scoped deploy keys
The panel generates an SSH deploy key scoped to a single repository — safer than a full-account access token. The key must be added at your Git provider before creating the application, and the panel tells you if generation fails rather than silently continuing.
- Supports GitHub, GitLab, and Bitbucket
- Deploy keys scoped to one repo (not your whole account)
- Choose branch — defaults include main and Master
- Auto dependency install and build step execution
Docker host with full control
Run containers instead of a managed stack. Configure the image name, tag, container port, max CPU cores (fractional allowed), memory limit, and private registry credentials. A port mismatch produces a container that starts but is unreachable — the panel tells you this.
- Configurable image name and tag (defaults to latest)
- Container port must match the image's listening port
- Max CPU cores (fractional allowed) and memory limits
- Private registry credentials supported
Port
8080:80
CPU
1.5 cores
Container management, beyond one container
Manage images, containers, and Docker Compose stacks from the panel. Pull from public registries or from your own private registry with stored credentials.
- Docker Compose stack creation
- Container lifecycle — start, stop, restart, logs
- Private registry credentials
- Per-container CPU and memory limits
web
nginx:1.25
api
acme/api:2.4
worker
redis:7
Per-app deployment scripts
Each application has its own deployment script with build, migration, and cache steps that run automatically on every deploy. This is where you configure what happens when you push to production.
- Build steps (npm install, composer install, etc.)
- Migration steps (php artisan migrate, etc.)
- Cache clearing steps
- Custom commands per deployment
# Deployment script
$ npm install
added 312 packages in 4s
$ npm run build
✓ Building for production...
✓ Generated static files
$ php artisan migrate
Migration complete.
$ php artisan cache:clear
Application cache cleared!
✓ Deploy successful
One-click staging environments
Create a full copy of any application to test changes before touching production. Clone applications across servers. Each staging environment gets its own domain, SSL, and database.
- One-click staging — full copy of production app
- Clone applications to the same server or another
- Independent domains, SSL, and databases
- Test deployments before going live
Production
acme.com
Staging
staging.acme.com
SSL
DB
Domain
One server, many stacks
Fresh installation supports a wide range of stacks. PHP version is selectable per application — two apps on the same server can run different PHP versions.
PHP: Laravel (9–13), WordPress, Magento — PHP 7.3 through 8.3
JavaScript: Node.js, Next.js, MERN, Angular, Svelte — Node 16–20
Python: Django, Flask — Python 3.11, 3.12, 3.13
Everything around deployment
Pair deployment with the tools that keep your applications fast, secure, and resilient.
Yes, SharkCluster supports deploying from GitHub, GitLab, and Bitbucket repositories using either personal access tokens or panel-generated deploy keys scoped to a single repository.
Yes, SharkCluster supports Docker host deployment with configurable container images, tags, ports, CPU limits, memory limits, and private registry credentials.
Yes, every application can be cloned into a staging environment with one click — a full copy to test changes before touching production.
Ready to take control
of your hosting?
Deploy servers, run self-hosted business apps, and keep your data on your own VPS — with a dedicated DevOps manager by your side.