Web Terminal Laravel Package

Product Decisions This Supports

• Internal DevOps/DevRel Portals: Enable self-service access to production/staging environments for engineers, reducing reliance on manual SSH access and improving auditability.
• Customer Support Tools: Offer limited, whitelisted command execution for support teams to debug issues in SaaS applications (e.g., "restart queue worker" or "check disk space").
• Multi-Tenant SaaS Platforms: Provide isolated terminal access per tenant (e.g., managed hosting services) with granular permissions via TerminalPermission enum.
• CI/CD Pipeline Debugging: Embed terminal sessions in Filament dashboards for developers to inspect failed builds or debug deployment issues interactively.
• Roadmap for "Dev Mode": Build a phased rollout of terminal access, starting with read-only commands (e.g., ls, tail -f) and expanding to write operations with approval gates.
• Build vs. Buy: Avoid reinventing secure shell access from scratch; leverage this package to integrate terminal functionality into existing Filament admin panels without heavy custom development.
• Compliance/Auditability: Replace ad-hoc SSH access with logged, permission-gated terminal sessions to meet SOC2/GDPR requirements for command execution tracking.
• Feature Flag for Power Users: Roll out terminal access as a premium feature for advanced users in a SaaS product (e.g., "Dev Terminal" add-on).

When to Consider This Package

• Adopt if:

  • Your team uses Filament + Laravel and needs a secure, auditable way to expose shell access to non-technical or distributed teams.
  • You require multi-tenancy (e.g., managed hosting) or role-based command restrictions (e.g., support teams can’t run rm -rf).
  • You want to embed terminal sessions in a dashboard (e.g., for debugging) without building a custom solution from scratch.
  • Your use case involves interactive commands (e.g., artisan tinker, queue:work) or TUI apps (e.g., htop, vim).
  • You prioritize compliance and need an audit trail for all executed commands (logs, timestamps, user context).

• Look elsewhere if:

  • You need Windows PowerShell support (this package focuses on Unix-like shells).
  • Your stack is not Laravel/Filament/Livewire (e.g., Django, Node.js, or non-web terminal needs).
  • You require highly customized terminal UIs (e.g., game-like interfaces) beyond PTY/ghostty-web rendering.
  • Your security model demands zero-trust beyond whitelisting (e.g., runtime command validation or sandboxing).
  • You need real-time collaboration in terminal sessions (e.g., pair debugging with multiple users).
  • Your PHP version is <8.2 or Laravel version is <11.x (check compatibility table).

How to Pitch It (Stakeholders)

For Executives:

"This package lets us safely embed terminal access into our Filament admin panel, giving engineers and support teams self-service tools to debug issues—without exposing raw SSH. Think of it like a 'Dev Mode' button for our SaaS product:

• Reduces toil: No more waiting for engineers to manually SSH into servers; support teams can run approved commands directly in the UI.
• Improves security: All commands are whitelisted, logged, and isolated by tenant—no more 'oops, I ran rm -rf' incidents.
• Enables compliance: Audit trails for every command executed, which is critical for SOC2/GDPR.
• Low risk: MIT-licensed, actively maintained, and integrates seamlessly with our existing Laravel/Filament stack. We can phase this in—starting with read-only commands for support, then expanding to dev tools—without a heavy custom build."

For Engineering:

"This solves a common pain point of securely exposing shell access in web apps. Here’s why it’s a no-brainer:

• Filament-native: Drops into our admin panel as a resource/page with zero UI work.
• Flexible connections: Supports both local shell (for dev/staging) and SSH (for production).
• PTY support: Full interactive sessions for artisan, queue:work, or even vim—no more clunky workarounds.
• Permissions: Uses Laravel’s enum system for clean can('access_terminal') checks.
• Logs & stats: Built-in audit trails and Filament widgets for monitoring usage. Downsides? Limited to Laravel/Filament, but that’s a non-issue for us. Let’s prototype this for the support team’s 'restart worker' use case first."