Built and hosted in the EU

A URL for everything you make.

Client sites, Node apps, agent output — one flat monthly price that doesn't count projects, seats or builds.

// sign in with GitHub, or mail hello@slew.sh — I'll migrate your first client site for you, free

slew-hq/slew-web — a real deploy

$ slew git connect slew-hq/slew-webConnected slew-hq/slew-web @ main.Every push now deploys; PRs get preview URLs. $ git push  succeeded 3221baa → https://slew-marketing.slew.cloud

The slew dashboard listing four live projects — skills, slew-docs, slew-marketing and app — each showing its domain and most recent deployment.

Five commands

That's the whole platform.

git push
most people start here
Connect a repository once through the GitHub App. Every push builds and deploys, every pull request gets its own preview URL, and a deploy that crashes on boot never takes traffic. No repository? slew deploy dist ships a built folder the same way — static sites, or Node and Next.js apps as real servers.
That session is real output — slew-hq/slew-web is the repository of this site.
```
$ slew git connect slew-hq/slew-web
Connected slew-hq/slew-web @ main.
Every push now deploys; PRs get preview URLs.

$ git push
  succeeded 3221baa → https://slew-marketing.slew.cloud
```
slew forms
this one is live
A contact form is not a backend project. Point any HTML form at a path on your own site — submissions land in the console, you get an email, export is CSV, and a retention window keeps GDPR simple. Static sites included.
This panel is a real form: <form action="/_slew/forms/hello"> on this page. It emails me.

slew share

One file, one link, gone in a week — no account needed to open it.

$ slew share report.html
Shared 1 file at https://quiet-harbor-lantern.slew.cloud

slew stats

Cookieless traffic on every site, measured at the edge — no script, no banner. slew.sh measures itself the same way.

$ slew stats
  requests   12,405 (96.2% from cache)
  by hour    ▁▁▂▃▅█▆▅▃▂▂▃▄▅▆▅▄▃▂▂▁▁▁▁

slew token ai
An OpenAI-compatible endpoint in front of EU-hosted models only — mint a key and point any OpenAI SDK at ai.slew.cloud. Metered in euros of credit, priced per model, prompts never logged.
```
$ slew token ai "local dev"
slew_9f2k… — shown once, keep it safe

$ export OPENAI_BASE_URL=https://ai.slew.cloud/v1
```

For coding agents

Your agent ships its own work.

Hand Claude Code, Cursor or whatever you run the slew-share skill and every plan, report and mockup it writes comes back as a link you can open and send to a client — no account needed to read it, and it deletes itself after a week so your throwaways stay throwaway.

$ slew share plan.html

Every command is also a page in the dashboard if you'd rather click, and all of it is in the docs.

Where it runs

Entirely in Europe.

An EU-incorporated company on European infrastructure — servers in Germany, edge in Slovenia, billing in euros. Your source, builds and traffic never leave EU jurisdiction, and there is no US parent company. When a client asks where their site lives, that's the whole answer.

slew.sh, the dashboard and the docs all deploy on slew, on that same infrastructure. Need the full facts for a procurement checklist? The comparison with Vercel and Netlify has the table.

Who you're buying from

I'm Hessel. slew is me.

I write the CLI, run the servers, carry the pager, and answer hello@slew.sh myself. There is no support tier to escalate through and no queue your ticket sits in — you email, I answer.

That's the trade, and I'd rather be straight about it: slew is smaller than the American platforms and it will stay smaller. What you get for that is a platform where the person who can fix your problem is the person who reads your email, a price that changes only when I tell you it's changing, and a roadmap you can actually influence — ask for something and it might ship next week.

I run my own work on it. If slew breaks, my sites go down with yours.

And the obvious question, answered before you have to ask it: if I ever stop, you are not stuck. Your repository is the source of truth, builds are plain static files or plain Node, and nothing here is a proprietary format. Moving off slew is a git push somewhere else — which is exactly why you can put a client on it.

— Hessel Tjeerdsma, Netherlands · LinkedIn · hello@slew.sh

Building in public

Recently shipped.

What went live on slew in the last few weeks. Ask for something and it lands on this list.

1 Aug 2026
Forms
Every site now takes form submissions — static sites included. Point a plain HTML form at /_slew/forms/<name> on your own domain: submissions land in the console, owners get an email, and each form has CSV export and a retention window. Included in every plan; a hidden honeypot field and rate limits keep the bots out.
1 Aug 2026
Rewrites and exact status codes
slew.json redirects can now name their exact code (301, 302, 303), and a new rewrites array serves another path of the same site with the URL unchanged — the classic sub-app shell, checked only after every redirect missed. The migration importers translate both from vercel.json and _redirects.
1 Aug 2026
Image optimization
Every project now answers /_slew/image: ask for a width, get a resized WebP served from the CDN edge. Nothing to enable, included in every plan, and the work happens off your instance — an image request never wakes a scaled-to-zero server. Next.js apps opt in with a one-line loader.
31 Jul 2026
The Vercel and Netlify importers
slew import migrates the project in your current directory: an honest compatibility report first, then env vars, redirects, crons and the git connection, ending in a DNS cutover checklist. Read-only towards your old host — nothing there changes until you flip DNS yourself.
31 Jul 2026
A CDN zone per project
Every project now fronts its own CDN zone instead of a shared one — cache, edge settings and logs are isolated per site, and a password-protected site no longer shapes caching for anyone else. Existing projects were migrated in place; nobody changed a DNS record.

The full changelog — and every release gets a short post on LinkedIn.

Switching

Move one site. Leave the other thirty-nine.

Point a single project at slew and keep the other thirty-nine exactly where they are. Same repository, same build, one extra live URL. Nothing about your current setup changes until you change a DNS record — so there's no migration to schedule and nothing to roll back if you don't like it.

Coming from Vercel or Netlify, the CLI does the move for you: slew import reads your existing config, starts with an honest compatibility report, copies env vars, redirects and the git connection, and ends with a DNS cutover checklist. Read-only towards your old host — the walkthroughs are in the migration guides.

In electronics, slew rate is how fast a signal can flip between states. Leaving should be that cheap too: builds are plain static files or plain Node, your repository stays the source of truth, and there's no proprietary config to unwind. A platform that's easy to leave is one you can put a client on.

Pricing

Pick a plan. That's the bill.

Every plan is the whole platform — git push, preview URLs, server runtimes, image optimization, forms, analytics, share links, rollback, custom domains, AI gateway. Plans differ only in how much you hold at once. Flat euros, no seats, no usage meter.

Free

€0no card, no trial clock

For side projects and kicking the tires.

3 projects, 1 custom domain
1 server app kept ready
50 GB bandwidth/mo

Start free

Pro

€9per month, ex VAT

For products and client work in production.

10 projects & custom domains
2 server apps kept ready
100 GB bandwidth/mo

Go Pro

That's the whole platform.

git push

slew forms

slew share

slew stats

slew token ai

Your agent ships its own work.

Entirely in Europe.

I'm Hessel. slew is me.

Recently shipped.

Forms

Rewrites and exact status codes

Image optimization

The Vercel and Netlify importers

A CDN zone per project

Move one site. Leave the other thirty-nine.

Pick a plan. That's the bill.