The Problem

Artisan Commands Shouldn't Require SSH

Every time you need to run an Artisan command in production, someone has to SSH into the server, remember the exact syntax, and hope they don't run something destructive. Non-technical team members? Completely locked out.

Checking migration status, clearing caches, listing routes: routine tasks that should take seconds end up blocked behind access restrictions and terminal knowledge. Your team moves slower than it should.

The Solution

Laravel Webartisan gives you a modern, browser-based terminal for running Artisan commands. Tab completion helps you discover commands. Command history lets you repeat actions with arrow keys. Four built-in themes make it feel like a native terminal.

Security is built in at every layer: environment restrictions, Gate-based authorization, command allow/block lists with wildcard patterns, domain restrictions, and a master kill switch. You control exactly who can access it and what they can run.

Key Features

Zero-dependency frontend. No npm builds, no CDN calls. Works out of the box.
Tab completion. Autocomplete command names as you type.
Command history. Navigate with up/down arrows, just like a real terminal.
4 built-in themes. Dark, Light, Monokai, and Dracula.
Gate authorization. Restrict access to specific users or roles.
Command allow/block lists. Wildcard patterns like migrate:* or db:*.

Requirements

PHP 8.2+
Laravel 10.x, 11.x, or 12.x

Installation

composer require emir/laravel-webartisan --dev

View on GitHub

Partnership is at the core of what we do.

Laravel Webartisan

Artisan Commands Shouldn't Require SSH

The Solution

Key Features

Requirements

Installation

Unsure where to start? Let’s figure it out together 👋

Unsure where to start?
Let’s figure it out together 👋