Vaporware is a native Mac app that runs your Vapor projects locally — no terminal wrestling with swift run, no Docker configs, no manual database setup. Open the app, and it works.
Notarized DMG · built-in updates · no account, no license keys
Vaporware manages servers, Swift toolchains, databases and domain routing, so you can spend your time in the code — not the config.
Point Vaporware at any Vapor project — or scaffold a new one — and it builds and serves it with live status: Starting → Building → Running, with compile progress parsed straight from the build.
Package.swift, entrypoint, routes and optional Dockerfile.Install database engines from Settings in one click — they’re fetched on demand, verified, and managed entirely by Vaporware. Start and stop them from the app or the menubar.
CREATE DATABASE and a pre-filled .env with working credentials.myapp.test instead of localhost:8080Vaporware runs a local DNS resolver and reverse proxy, so every project can have a friendly .test hostname — with automatic HTTPS from a local certificate authority your browser trusts.
/etc/hosts hacks — routing is handled by an internal proxy..test back to other tools (like Laravel Herd) with one click.A built-in SMTP inbox captures outgoing mail during development — password resets, receipts, notifications — so nothing ever reaches a real inbox by accident.
localhost:1025 and you’re done..eml files across launches..env, as an interface.Each project’s environment variables get a visual editor — add, toggle, reorder and comment variables without leaving the app. Changes round-trip cleanly to the file.
Vaporware lives in your menubar with quick controls for every service and project. Prefer the terminal? The vw CLI drives the same services — and an optional headless daemon keeps them alive with the app closed entirely.
No YAML, no containers, no PATH surgery. Vaporware detects the Swift toolchains you already have and handles the rest.
Open an existing Vapor package or scaffold a new one — optionally with a database provisioned and .env pre-filled.
Vaporware resolves, builds and serves with live progress. Pick a Swift toolchain per project if you need to.
Give it a myapp.test hostname with automatic HTTPS, watch requests stream in, and get back to writing Swift.
The details that usually eat an afternoon, already handled.
Build each project with the Swift version it expects. Vaporware detects installed toolchains — no swiftenv gymnastics.
Request logs, route matches and errors stream into the app as your server runs — filter by method or path.
Turn a Pixla Sites project into a real Vapor 4 app — pages become Leaf templates, forms become Fluent routes.
One button packages your project and hands it to Pixla Hosting for production — build, TLS and routing included.
Vaporware updates itself in the background and shows release notes — no App Store, no re-download dance.
One built-in uninstaller removes everything — routing, certificates, CLI tools and data. Project folders untouched.
Vaporware works entirely on its own. Pair it with other Pixla apps when you want the full path from idea to production.
Publish a Vapor project straight from the app — builds, TLS and routing handled.
Learn more →Design without code, then export a deployable Vapor app with Leaf templates.
Learn more →Announce releases and reach your users — email campaigns and newsletters, native on Mac.
Learn more →Free and full-featured. Every feature above ships in the one and only version — no Pro tier, no trial, no license key.
↓ Download for macOS8.4 MB · Requires macOS 26 (Apple silicon) · Notarized · engines download on demand
.test ownership is an explicit toggle — you can hand it back to other tools at any time.~/Library/Application Support/Vaporware. Your project folders and .env files stay exactly where you created them.