Free while you build. Priced when you ship.
No credit card to start, and no per-connector fees. When you go to production we size a plan around your message volume and where the mesh runs.
Free
$0
forever
Everything you need to connect your first systems.
- Unlimited projects while you build
- Clients, workers and the REST bridge
- All official SDKs
- Local LLM and on-prem workers
- Community support
Pro
Most teamsTalk to us
usage-based
For products running real traffic in production.
- Higher message and connection limits
- Multiple environments per project
- Usage metrics and message inspection
- Email support with response targets
- Key rotation and team members
Enterprise
Custom
annual
For regulated, on-premise or high-volume deployments.
- Self-hosted or dedicated mesh
- SSO, audit logs and retention controls
- Security review and custom DPA
- Private Slack channel and SLA
- Migration and architecture support
Running the mesh yourself with the single binary is always free for development.
How usage is measured
Two numbers, no seat maths: how many messages the mesh routes for you, and how many connections you keep open.
Messages
Each request and each response routed through the mesh, including REST bridge calls and channel publishes.
Concurrent connections
Clients and workers connected at the same time. Reconnects of the same session are not counted twice.
Not counted
Projects, environments, plugins, actions, SDKs and team members. Add as many as you need.
Questions we get asked
Short answers. The docs go deeper.
What is Gluer?
Gluer is a managed integration layer that connects frontends, backends, third-party services and LLMs through a single real-time message bus. Clients speak WebSockets or plain HTTP, and Gluer routes every message to the worker that can handle it — regardless of language, cloud or network.
How is Gluer different from a message broker like Kafka or RabbitMQ?
Brokers are infrastructure you host and operate, and they only talk to your backend. Gluer is fully managed and reaches all the way to the browser, the mobile app and the CLI: the same message header routes a request from a React page to a Python worker running on a laptop behind NAT, with an HTTP bridge for webhooks.
Do I need to host anything to use Gluer?
No. Gluer runs as a managed mesh at wss://ws.gluer.io. You create a project, get a public key for clients and a private key for workers, and connect. A single-binary CLI is available if you want to run the mesh locally for development or on-premise.
Which languages and frameworks does Gluer support?
Official SDKs cover JavaScript in the browser, Node.js and Dart/Flutter, with Python, Go, Java, .NET and Elixir workers supported through the same protocol. Any language that can open a WebSocket or send an HTTP POST can join the mesh.
Can Gluer connect my application to a local LLM?
Yes. A worker running next to Ollama, llama.cpp or vLLM connects to Gluer with your private key and exposes inference as a normal action. Your frontend calls it like any other endpoint, so prompts and model output never leave your machine or VPC while the browser still gets streamed responses.
How does Gluer handle security?
Projects are isolated by keypair, client keys are public by design and scoped to browser traffic, worker keys are private and never shipped to clients, origins can be allow-listed per project, and every message is scoped to a session. Passwords are hashed with bcrypt, one-time login codes are single-use and short-lived, and traffic is TLS-only.
Is Gluer free to start?
Yes. You can create an account, create a project and connect workers on the free tier without a credit card.