Your own little cloud.

Slasha builds your app, deploys it without downtime and serves it over HTTPS. Databases, cron jobs and alerts included.

$curl -fsSL https://slasha.com/setup.sh | bash
~/storefront
storefront mainLive

Deployments

CommitStatus

Click a deploy for its logs. Hover an older one to roll back.

Deployed in 41sstorefront.ship.acme.dev

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

Apps

Manage and browse the applications running on this instance.

New app
storefrontstorefront.ship.acme.devLive
main· deployed 2m ago
apiapi.ship.acme.devLive
main· deployed 1h ago
adminadmin.ship.acme.devBuilding
main· deployed just now
docsdocs.ship.acme.devLive
main· deployed 3d ago
stagingstaging.ship.acme.devLive
develop· deployed 5h ago
worker-jobsworker-jobs.ship.acme.devFailed
main· deployed 20m ago

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.

Visitors must enter a password to access this app.

staging.ship.acme.dev

Access Required

This app is password protected.

••••••••
Continue

Domains

Add a domain, get HTTPS

Slasha checks the DNS and gets the certificate.

storefront.ship.acme.dev Healthy
shop.acme.com Healthy
Add a domain below

Point the domain at your server, and Slasha gets the certificate.

Scaling

Scale web and workers

Set how many of each process to run.

webServes HTTP traffic
workerBackground jobs
$

Rollbacks

Undo a bad deploy

Your last 10 builds are kept. No rebuild.

New pricing page9f3c2e1 · 3 min ago
Fix signup redirect4be81a0 · 2 hours ago
Node 22 upgradec71d9f4 · yesterday

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.

    storefront · Environment
    DATABASE_URL${{ db.DATABASE_URL }}
    REDIS_URL${{ cache.DATABASE_URL }}
    UPLOAD_DIR${{ SLASHA.managed_data_path }}/uploads
    LOG_LEVELinfo

    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

    Set up your agent

    Alerts

    Hear about problems first

    Failed deploys, full disks, expiring certificates. Sent to Slack, Discord, Telegram or email.

    1. storefront memory at 91%14:02
    2. Sent to #ops on Slack14:02
    3. 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.

    1. 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 | bash
    2. 02 · 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 | bash
    3. 03 · 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.
    How to set up an agent safely
    agent · ~/storefront
    › Ship this to our Slasha server and give it a Postgres database.

    ● 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.

    1. git pushfrom you or an agent
    2. BuildDockerfile or Railpack
    3. Releasemigrations run here
    4. Health checknew version must pass
    5. LiveCaddy switches traffic

    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?
    A Linux server with 2 GB of RAM, root access and a domain. The setup script installs the rest. See Install on a server.
    Is it really free?
    Yes. It is MIT licensed with no paid tier. You only pay for your server.
    Do I need a Dockerfile?
    No. Without one, Slasha detects your stack with Railpack. With one, it uses yours.
    How is this different from a hosted platform?
    Same push-to-deploy workflow, but on a server you own. You pay for the machine, not per app or per seat.
    Can my AI coding agent deploy with it?
    Yes. The slasha CLI covers deploys, logs, env vars, databases and rollbacks. See Slasha for agents.
    What happens if a deploy breaks?
    A new version only gets traffic after it passes a health check. If it fails, the current version keeps serving.
    Can I run it on more than one server?
    Yes. Add servers as nodes and pick which one each app runs on.

    Try Slasha on your own server

    Free and open source. Your first app can be live in ten minutes.

    $curl -fsSL https://slasha.com/setup.sh | bash