Soketi App Manager (for soketi)

Soketi App Manager is a web-based administration UI for soketi, a Pusher-compatible WebSocket server. It gives teams a central interface to create and manage realtime apps, configure webhooks, rotate keys, and view live connection and server metrics instead of using only CLI or config files.

The tool is aimed at engineering teams that want to self-host a production-capable realtime stack (soketi + Redis + an RDBMS) and prefer an open-source UI for operational tasks, role-based access, and faster troubleshooting workflows.

Use Cases

• Teams migrating from Pusher who want protocol compatibility to reuse existing client SDKs and logic.
• Organizations self-hosting realtime services on cloud VMs or on-prem where operational control, data residency, or cost predictability matter.
• Projects running multiple realtime apps/environments that benefit from centralized app CRUD and multi-app dashboards.
• Operations or platform engineers who need a GUI for managing webhooks, credentials, and viewing live connection metrics during incidents.

Strengths

• Pusher protocol compatibility — lowers friction for migration and lets you reuse existing client libraries.
• Centralized app and credential management — create, edit, delete apps and rotate API keys from a single UI.
• Real-time dashboards and metrics — immediate operational visibility into active connections and per-app stats for troubleshooting and capacity checks.
• Webhook configuration in the UI — manage endpoints, headers and filters without editing configuration files.
• Role-based access control — supports multi-user workflows and separates admin and operator responsibilities.
• Open-source and extensible — code is public so you can self-host, audit, or customize the manager to match internal processes.
• Fits common infra stacks — integrates with MySQL/Postgres, Redis and soketi/Node.js, so it can slot into typical deployments.

Limitations

• Operational complexity — self-hosting requires running soketi (Node.js), the App Manager (PHP), an RDBMS and Redis; this increases provisioning and monitoring burden compared with managed services.
• Caching semantics (TTL) — app metadata is cached; changes (credential rotation, config edits) may not be visible immediately unless cache is invalidated or TTL is accounted for.
• Scaling and observability — large-scale, high-concurrency deployments need explicit tuning, autoscaling design and metrics/logging (Prometheus, etc.).
• Smaller ecosystem and maturity — App Manager implementations are community-driven and may require custom glue or contributions versus mature commercial dashboards.

Final Thoughts

Soketi App Manager makes self-hosting a Pusher-compatible realtime stack more practical by providing a focused UI for routine operational tasks. It is a good fit when you need protocol compatibility, control over hosting and security, and you have the ops capacity to run multiple supporting components.

If you evaluate it, plan for operational work: automate deployments for soketi and the App Manager, integrate metrics and logs, test cache TTL behavior for credential rotations, and validate scaling behavior under realistic load. If you lack the operational bandwidth or need strong SLAs without building observability and autoscaling, a managed realtime service may be a better choice.

References

• https://docs.soketi.app/app-management/introduction
• https://docs.soketi.app
• https://github.com/rahulhaque/soketi-app-manager-filament
• https://github.com/soketi/soketi