Your own little cloud.
Slasha builds your app, deploys it without downtime and serves it over HTTPS. Databases, cron jobs and alerts included.
Deployments
Click a deploy for its logs. Hover an older one to roll back.
Use + and −, then apply.
Services
DATABASE_URL is set on storefront
$ slasha services proxy db
REDIS_URL is set on storefront
$ slasha services proxy cache
Redis is a cache, so it has no backups.
Cron jobs
Press ▸ to run a job now.
Metrics
Files
main · read-onlyAnyone with the link.
Domains
Apps
Nodes
Click a node to open a console on it.
Try
Rules
Recent
Users
Click a role to change it. Admins manage nodes, alerts and users.
Lets you push over SSH as well as HTTPS.
Database backups and SQLite copies go here.
Works with Node.js, Python, Ruby, Go, PHP, Java, Rust, static sites or any Dockerfile.
Why Slasha
Hosted platforms get expensive
They bill per app, per database and per seat. Slasha runs on a server you already pay for.
You pay for the server
Ten apps and three databases cost what the server costs.
Your data stays with you
Code, databases, logs and backups stay on your server and your S3.
Little to maintain
One program. It handles HTTPS, health checks, rollbacks and restarts.
The dashboard
Take a look around
Click through the main screens.
Every app on the server, with its branch and status.
Apps
Manage and browse the applications running on this instance.
Commit
9f3c2e1
Status
Duration
41s
Message
Add pricing page
No lines match.
CPU
25.6%
Memory
261 MiB
Network
179 KB/s
Disk I/O
23 KB/s
CPU
1.8%
Memory
182 / 512 MiB
Volume
1.2 GB
DATABASE_URL is injected into storefront automatically. Or reference any value:
Tunnels over HTTPS. The database port is never opened to the internet.
Schedule
0 7 * * *
Every day at 07:00
Timezone
Europe/Berlin
Next run
Tomorrow, 07:00
Runtime
App image
Command
node scripts/send-digest.js
Run history
Timeline
Triggered
Memory at 87.2% (threshold 85%)
Notified #ops on Slack
and on-call by email
Re-notifies every 15 min while it stays open
Triggered: storefront memory above 85% (87.2%)
Nodes
Add nodethis server
root@203.0.113.21
root@198.51.100.7
root@eu-worker-1:~# uptime -p
up 3 weeks, 2 days, 4 hours
root@eu-worker-1:~# nproc
4
root@eu-worker-1:~# cat /proc/loadavg
0.41 0.38 0.35 1/312 48211
root@eu-worker-1:~# free -h | grep Mem
Mem: 7.7Gi 4.8Gi 2.9Gi
root@eu-worker-1:~# df -h / | tail -1
/dev/sda1 80G 31G 46G 41% /
root@eu-worker-1:~#
Built in
What comes with it
Each of these would be a separate tool on a bare server.
Private apps
Hide staging from the public
Public, password protected or team only. No login code.
Domains
Add a domain, get HTTPS
Slasha checks the DNS and gets the certificate.
Point the domain at your server, and Slasha gets the certificate.
Scaling
Scale web and workers
Set how many of each process to run.
Rollbacks
Undo a bad deploy
Your last 10 builds are kept. No rebuild.
Click Roll back on an older build.
Cron jobs
Run jobs on a schedule
Type a schedule to see when it runs.
Times shown in UTC. Each job picks its own timezone.
Environment
Point env vars at a database
Credentials stay in one place.
Databases
Query production from your laptop
One command opens a tunnel. No public ports.
❯ slasha services proxy db --port 5432
✓ Tunneling db (PostgreSQL)
Listening on: 127.0.0.1:5432
Press Ctrl-C to stop.
❯ psql -h 127.0.0.1 -U postgres
postgres=# select count(*) from orders;
count
-------
18204
postgres=#
CLI and agents
Your coding agent can run it
Each step is one command, with plain-text docs at /llms.txt.
❯ slasha deploy -f
building · releasing · health check
✓ live at storefront.ship.acme.dev
❯ slasha logs --search error
no matches in the last 2000 lines
Alerts
Hear about problems first
Failed deploys, full disks, expiring certificates. Sent to Slack, Discord, Telegram or email.
- storefront memory at 91%14:02
- Sent to #ops on Slack14:02
- Resolved, back to 58%14:09
Logs
Live logs you can search
Build, app, database and cron logs in one place.
web.0 GET /cart 200 12ms
web.0 GET /api/items 200 8ms
worker.0 sent 3 emails
web.1 slow query 812ms
web.0 POST /checkout 201
Backups
Database backups on a schedule
To disk or any S3 bucket. Restore in one click.
- today 03:0012.4 MB · S3
- yesterday 03:0012.1 MB · S3
- Oct 30, 03:0011.9 MB · S3
Servers
Add more servers
Connect one over SSH. Pick where each app runs.
- local18%
- eu-worker-141%
- us-gpu-17%
Getting started
From a new server to a live app in ten minutes
One command on the server, one on your laptop, then push.
01 · On your server
Install Slasha
Installs Docker, a firewall and Slasha. Then point your domain and a wildcard record at the server.
$curl -fsSL https://slasha.com/setup.sh | bash02 · On your laptop
Install the CLI and log in
Create your admin account in the dashboard, then log in from the CLI.
$curl -fsSL https://slasha.com/install.sh | bash03 · In your project
Create an app and push
Create the app, add its git remote and push. Every push to main deploys.
$git push slasha main
Prefer clicking? The dashboard does all of this too. Full quickstart →
AI agents
Let your coding agent deploy
Your agent can deploy, read the logs, fix what broke and deploy again.
- Every step is one CLI command.
- Docs for agents at /llms.txt.
- Give the agent its own limited user.
- Failed builds never get traffic.
● Bash(slasha services provision postgresql db)
⎿ db (postgresql 17) is provisioning
● Bash(git push slasha main && slasha deploy -f)
⎿ release: column "plan" does not exist
⎿ deploy failed, previous version still serving
A migration ran before the one that adds plan. Reordering them.
● Edit(prisma/migrations/…)
● Bash(git commit -am "Fix migration order" && git push slasha main)
⎿ health check passed · live at storefront.ship.acme.dev
Deployed. DATABASE_URL was set for you.
How it works
What happens when you push
Every deploy takes the same path. Your current version keeps serving until the new one passes its health check.
Receiving your push…
Also inside the same program
- Schedulercron jobs and database backups
- Logs and metricsstored in DuckDB on the server
- Alertsrules checked every minute
- Stateone SQLite file
Talks to
- Your S3 bucketbackups and SQLite replication
- More serversadded as nodes over SSH
- Your channelsSlack, Discord, Telegram, email
- GitHuboptional, deploys on push
Features
Everything that's included
No plugins, no paid tier.
Frequently asked questions
Have another question? Ask on GitHub.
What do I need to run Slasha?
Is it really free?
Do I need a Dockerfile?
How is this different from a hosted platform?
Can my AI coding agent deploy with it?
slasha CLI covers deploys, logs, env vars, databases and rollbacks. See Slasha for agents.What happens if a deploy breaks?
Can I run it on more than one server?
Try Slasha on your own server
Free and open source. Your first app can be live in ten minutes.