Soketi server for compatible Pusher clients
The catalog lists a Soketi container for realtime applications using compatible Pusher clients. Review connection, resource, and access-control requirements; provisioning is currently unavailable in the international sandbox.
Soketi template details
Pusher-protocol compatibility and default credentials are configured in the template. Resource limits are governed by your fixed monthly EUR zone package.
Pusher-protocol compatibility
Soketi implements the Pusher protocol for compatible clients. Verify feature and SDK compatibility for your application before switching.
WebSocket-based realtime messaging
Soketi uses WebSockets for realtime events. Latency depends on the client, network, and deployment.
Soketi server template
The marketplace template runs the Soketi image with a 0.25 vCPU and 256 MB RAM minimum. Connection capacity and resource use depend on workload and configuration.
Authentication and network configuration
The template configures a default app key and secret and exposes the service port. Configure channel authorization, TLS, and access controls for your deployment.
Frequently asked questions about Soketi
Answers to common questions about WebSockets, the Soketi template, and Pusher-compatible clients:
Soketi: a WebSocket server using the Pusher protocol
Realtime events can support features such as notifications, chat, and live updates. Soketi is an open-source server that implements the Pusher protocol; compatibility, connection capacity, operating costs, and data handling depend on your application and configuration.
Can Soketi work with applications built for Pusher?
Soketi implements the Pusher protocol and may work with compatible clients. Check the features your application uses and test the client configuration before switching. Performance depends on workload and deployment.
For a server-side event publisher, see the Node.js cloud hosting product. Laravel developers can also configure Buy Laravel hosting with compatible Laravel Echo clients. Integrations require separate configuration.
Soketi template compared with self-managed installation
A self-managed WebSocket server may require reverse-proxy, connection timeout, firewall, and TLS configuration. Requirements vary by software and hosting environment.
The marketplace template defines a public Soketi container with generated credentials. Configure the client, authorization, and TLS for your deployment. Provisioning is currently unavailable in the international sandbox.
Soketi deployment options
Compare protocol support, configuration, resource limits, and service terms.
| Feature | Deplomo Soketi template | Hosted Pusher service | Manual setup on a VPS |
|---|---|---|---|
| Connection capacity | Depends on available resources, workload, and configuration | Limits and pricing depend on the selected plan | Depends on server capacity and operating-system configuration |
| Client compatibility | Implements the Pusher protocol; test compatibility with your client and features | The hosted provider’s API and service terms | Test client behavior, ports, and firewall rules in your environment |
| Deployment and secure transport | Public Soketi container; TLS and domain setup depend on the environment | Connection performance depends on network and workload | Self-managed installation may require proxy and TLS configuration |
| Pricing model | Fixed monthly EUR package pricing | Hosted service prices depend on provider and plan | Deplomo uses fixed monthly EUR packages by zone, with hard limits |
Soketi implements the Pusher protocol for compatible clients. Compare configuration, resources, and service terms for your application; no speed or cost guarantee is implied.
Soketi template requirements
The marketplace lists a Soketi container with generated app credentials. Provisioning is currently unavailable in the international sandbox.
- Marketplace template The marketplace lists a Soketi template; provisioning is currently unavailable in the international sandbox.
- App credentials The template generates an app key and secret. Configure them in your client and protect the secret.
- Provisioning status Service provisioning is currently unavailable in the international sandbox; no deployment time, domain, or TLS setup is promised.
- Configure a compatible client When provisioning is available, configure your client with the service address, port, app key, and secret. Confirm transport security and authorization settings.
Soketi marketplace template overview
The marketplace lists a Soketi server for applications using compatible Pusher clients. Review capacity, security, and package limits for your workload; provisioning is currently unavailable in the international sandbox.
Review the Soketi template and client requirements.
Explore the Soketi marketplace template
Review the template configuration and package limits before deployment.