pal v1.3.13

LaraPal — the flagship of the Pal family. Five small desktop tools for PHP developers. One job each.

Written in Rust, shipped with Tauri. They start fast, stay out of the way and look like the terminal, because that is where the work already happens.

Download LaraPal v1.3.13 See all five
  • No Electron
  • No telemetry
  • No account
larapalservices
$ larapal
● php-fpm      running   :9000
● horizon      running   2 workers
● vite         running   :5173
○ mysql        stopped
────────────────────────────────
mail  3 caught   logs  tailing
dumps live       tinker ready
[q] quit  [s] start  [l] logs  [t] tinker

01 — the idea

One job each.

The Pal family is five separate programs. LaraPal watches a Laravel app. HttpPal sends requests. DataPal reads a database. GitPal handles branches and merges. PalPal installs the other four. Nothing overlaps and nothing tries to be a platform.

They are Rust binaries wrapped with Tauri. There is no bundled browser engine, so the downloads are small and a window opens in the time it takes to press the key. Nothing is sent anywhere: no analytics, no crash pings, no licence check, no sign-in.

Every panel is keyboard-driven. LaraPal also runs as a plain terminal UI, so it works over SSH on a box with no desktop at all.

02 — the family

LaraPal

v1.3.13 · shipping

Laravel companion — terminal UI and desktop app

Sits beside a Laravel app and shows what it is doing. Start and stop the things it depends on, then watch the output in one place instead of six terminal tabs.

  • Services — start, stop and watch php-fpm, queues, Vite, databases
  • Queue workers — jobs, retries and failures as they happen
  • Logs — tail and filter without leaving the window
  • Dumps — dump() output captured into its own pane
  • Mail catcher — every outgoing message held locally
  • Tinker — a REPL in the same session
Download from GitHub releases What it does, in full

HttpPal

coming soon

HTTP client — Postman-lite

Saved requests, environments and secrets, without an account or a workspace to invite anyone to.

  • Collections of requests, kept as files
  • {{env}} variables per environment
  • Secrets in the OS keychain, never in the collection
  • Requests fire from Rust: no CORS, no leaks
Tell me when it ships

DataPal

coming soon

MySQL workbench

A database client that knows it is sitting next to a Laravel app.

  • Paged grid over large tables
  • Inline edit, with the statement shown before it runs
  • SQL editor with autocomplete
  • Reads your Eloquent models and walks the real relations
Tell me when it ships

GitPal

coming soon

Git client

The day-to-day parts of Git, with a conflict tool worth opening.

  • Branches: list, switch, create, delete
  • Merges with the diff in front of you
  • Three-way conflict resolver in the PHPStorm style
Tell me when it ships

PalPal

coming soon

Installer and updater

One place to install, update and remove the other four.

  • One click per tool to install
  • Updates when you ask for them, not on a schedule
  • Shows the version of each tool you have
Tell me when it ships

03 — what they do not do

No Electron

Rust and Tauri, using the system webview. Small downloads, low memory, fast start.

No telemetry

No analytics, no crash reporting, no phone-home on launch. Nothing to opt out of.

No account

Download it and run it. No sign-in, no workspace, no seat to manage.

No cloud

Collections, connections and settings are files on your disk. Back them up how you like.

No lock-in

Every tool wraps something standard: Artisan, HTTP, SQL, Git. Delete it and your project is unchanged.

No feature creep

When a tool needs a job it was not built for, that job becomes a different Pal.

04 — the next four

One is out. Four are being written.

LaraPal is on GitHub releases now. The rest are not ready, and there is no date worth printing yet. If you want one of them, say which — mail goes straight to the author, and you get one message when that tool ships.

HttpPal DataPal GitPal PalPal

No list software and no tracking pixels. Your address is used for that one message and nothing else.

05 — the author

Five tools, one pair of hands.

The Pal family is written and maintained by one developer, for the work that developer does every day. That is why the five share a look, a set of key bindings and a release routine.

It also sets the pace. Things ship when they are usable, not when a roadmap says so, and bug reports land in the same inbox as everything else.