Joppa · Local HTTPS for your projects

macOS and Linux · v0.3

Joppa gives every local project a .test domain, a trusted certificate and its databases. No server to configure.

Download See pricing

Free to start

macOS
Linux
Windows · in progress

proxy :443

Trusted local CA

PostgreSQL

MySQL

MariaDB

Joppa's home screen: three projects, their HTTPS domains, their state and the last 24 hours of traffic — › Joppa's home screen: every project with its HTTPS domains, their state and its requests over the last 24 hours.

Features

Local infrastructure, minus the config.

An HTTPS proxy on :443, a local certificate authority and your services, run from a single window.

01 — domains

A .test domain per project.

Joppa finds the dev servers in a folder and gives each its own domain: app.myproject.test, api.myproject.test. No more localhost:5173 tabs that all look alike.

https://app.kinosante.test: → :48100
https://api.kinosante.test: → :48200

02 — https

Trusted HTTPS, no warnings.

A local certificate authority, added to the keychain once. Every domain gets its certificate; the browser shows the padlock, just like in production.

Certificate issued: *.kinosante.test
Proxy: listening on :443

03 — services

Your databases, one click away.

PostgreSQL, MySQL and MariaDB run in your container runtime, with one database per project and the extensions you need.

PostgreSQL 17: 127.0.0.1:5432 · pgvector
MySQL 8.4: 127.0.0.1:3306

Everything Joppa does

One app, your whole local environment.

Every feature has its page in the documentation.

Your projects

Point Joppa at a folder; it handles the rest.

Automatic detectionVite, Next.js, Nuxt, Astro, Laravel, monorepos and Docker Compose: Joppa finds the dev servers and their ports.Read the docs →A .test domain per serverapp.myproject.test, api.myproject.test, plus the web UIs of Mailpit, MinIO or pgAdmin, routed automatically.Read the docs →Processes and built-in terminalJoppa starts your dev servers and Compose containers in order, at launch if you like, and relaunches the ones that crash.Read the docs →A .env that stays up to dateHTTPS addresses and service connections written under the names your project already reads. Always a diff, always a backup.Read the docs →Node, bun and PHP per projectVersions pinned with Vite+ for Node and packages, static PHP builds from 8.1 to 8.5 with a shim that follows .php-version.Read the docs →Dev analyticsRequests, p95 latency, errors, uptime, slowest paths and N+1 bursts, measured by the proxy.Read the docs →New project from a templateVite+, monorepo, Next.js, Nuxt, Astro, SvelteKit, Laravel or a GitHub repository, with its versions and domains.Read the docs →

Your services

One server per engine, one database per project, in your container runtime.

PostgreSQL, MySQL, MariaDBSeveral versions, one database per project, and the extensions you need: pgvector, PostGIS, pgRouting…Read the docs →Redis and ValkeyCache, sessions and queues, kept on disk between restarts.Read the docs →MailpitEvery dev email caught over SMTP and shown in a web inbox. Nothing gets sent.Read the docs →Typesense and MeilisearchInstant search running locally, ready for Laravel Scout.Read the docs →Import from Docker ComposeThe data of your Compose databases and caches copied into Joppa, then the project switched over. The source is never modified.Read the docs →TablePlus in one clickEvery database opens in TablePlus, with a named connection tagged as local.Read the docs →

HTTPS and proxy

Like production, with nothing to configure.

Trusted certificatesA local authority trusted once, a certificate signed on the fly for every domain. mkcert is reused if it's there.Read the docs →A real reverse proxyHTTP/2, WebSockets for HMR, Server-Sent Events, X-Forwarded-* headers and readable error pages.Read the docs →Docker, Podman or nothingOrbStack, Docker Desktop, Colima or Podman for services. Domains and HTTPS need no runtime at all.Read the docs →Gets along with LerdLerd wants ports 80 and 443 too: Joppa detects it, stops it and hands the ports back when needed.Read the docs →

Keyboard, terminal and AI

The same app, wherever you work.

Keyboard firstEvery action has a shortcut. The ⌘K palette opens a project, copies a URL, starts a service or restarts the proxy.Read the docs →The joppa commandStatus, services, logs, databases and proxy from the terminal, with --json for your scripts.Read the docs →The app in your terminalA full-screen TUI, keyboard or mouse, with the same visual system as the window.Read the docs →MCP serverClaude Code, Claude Desktop and Cursor see your projects, start services, read logs and create projects.Read the docs →In four languagesEnglish, Français, Español and 中文, with light or dark theme and three icons to choose from.Read the docs →

Read the documentation First steps

Get started

Ready in a minute.

01■□□
Add a project
Drop a folder on the window, press N, or start from a template: Vite+, Next.js, Astro, Laravel…
02■■□
Joppa finds your servers
Vite, Next.js, Astro, Laravel, Docker Compose: Joppa reads the project and suggests a domain for each port.
03■■■
Open https://
The proxy listens on :443 and routes to your ports. Joppa can also run your dev servers for you.

~/Code/myproject

$ joppa status
› proxy :443 · CA joppa ok
› myproject  https://myproject.test → :5173
■ 1/1 domain online · postgres 17 running
$

Download

On macOS and Linux. Windows is coming.

One licence for all your systems.

macOS

your systemavailable

Download .dmg

Linux

your systemavailable

Download .AppImage Download .deb

Windows

your systemin progress

The Windows version is in development. Your Pro licence will work on it as soon as it ships.

Questions

Frequently asked questions

Why .test domains?

The .test domain is reserved for testing: it will never be assigned on the Internet. Joppa resolves it locally, to your machine.

Do I need to install Docker?

No. Domains and HTTPS work without any runtime. OrbStack, Docker Desktop, Colima or Podman are only used for services: databases, cache, mail and search.

Does Joppa change my files?

Never without showing you first. Changes to .env go through a diff you approve, and the original is saved to .env.joppa-backup.

I already have a docker-compose.yml with my databases.

Joppa reads it: it can run its services, or copy their data into its own services and point the .env at them, without ever modifying the source.

Does it work with Claude or Cursor?

Yes. The joppa command includes an MCP server: your assistant sees your projects, starts services, reads logs and can create a project.

Which systems are supported?

macOS and Linux. The Windows version is in development.

Joppa Pro

More projects, more services.

Buy a licence on the website, then activate it in the app in one click: Joppa opens and unlocks itself.

See pricing I already have a licence

Local infrastructure, minus the config.

A .test domain per project.

Trusted HTTPS, no warnings.

Your databases, one click away.

One app, your whole local environment.

Your projects

Your services

HTTPS and proxy

Keyboard, terminal and AI

Ready in a minute.

Add a project

Joppa finds your servers

Open https://

On macOS and Linux. Windows is coming.

macOS

Linux

Windows

Frequently asked questions

More projects, more services.

Write to support

Check your inbox

Write to support

Message sent

All your projects on https://

Local infrastructure, minus the config.

A .test domain per project.

Trusted HTTPS, no warnings.

Your databases, one click away.

One app, your whole local environment.

Your projects

Your services

HTTPS and proxy

Keyboard, terminal and AI

Ready in a minute.

Add a project

Joppa finds your servers

Open https://

On macOS and Linux. Windows is coming.

macOS

Linux

Windows

Frequently asked questions

More projects, more services.